| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
When starting senpai, we jump to the last opened buffer. Offset the
horizontal target list to make the buffer visible, as if scrolled to
with CTRL+N.
Fixes: https://todo.sr.ht/~taiite/senpai/100
|
|
|
|
|
| |
This will reduce network usage and possibly increase WHO cache hit ratio
on bouncers supporting a WHO cache.
|
|
|
|
|
|
| |
Even if it is a continuation line.
Fixes: https://todo.sr.ht/~taiite/senpai/98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Preivously, we highlighted the user for any message that contained the
nick, even in the middle of a word.
Now, we only send a highlight if the user was mentioned in a single
word, by detecting word boundaries around the mention of the user.
For example, considering user "foo":
Previously, we would highlight on "foo" and "foolish".
Now, we highlight only on "foo".
This was inspired/copied from soju's handling [1].
[1]: https://git.sr.ht/~emersion/soju/tree/5e56cc30c538eb88c21cce732e2e357e80098164/item/irc.go#L473
Fixes: https://todo.sr.ht/~taiite/senpai/97
|
|
|
|
| |
Fixes: https://todo.sr.ht/~taiite/senpai/17
|
|
|
|
|
|
|
| |
Using man to learn more about senpai is obvious. Using /help is more
specific to senpai.
Mention that rather than the man.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In a previous commit, the color scheme for displaying nicks was changed
to use more colors (30 rather than 14), using extended colors from the
256 colors set.
The issue with this is that most terminal emulators customize the colors
of the first 16 colors to make them more readable (eg, a terminal
emulator with a light theme will make colors darker, and one with a dark
theme will make colors lighter). So the 14 colors used before were
usually not the default color codes from the original xterm/X11 spec,
but specific colors chosen by the terminal emulator to be particularly
readable.
In a way, changing the behavior to use colors from the 256 colors set,
which is usually not overriden, made them much less readable.
Which is why we need a configuration option for this.
I conversatively chose to make the default color scheme the previous
one, with only the base 16 colors.
The 256 colors scheme can be enable by adding to the configuration file:
colors {
nicks extended
}
|
|
|
|
| |
This will help maintainers create their package.
|
| |
|
|
|
|
|
|
|
|
| |
Also, change the color scheme to use more colors. Now 30 instead of 15,
and with the consistent color codes offered by the extended XTerm 256
color scheme.
Fixes: https://todo.sr.ht/~taiite/senpai/90
|
|
|
|
|
|
| |
This enables dynamic discovery of new and deleted networks.
Fixes: https://todo.sr.ht/~taiite/senpai/71
|
|
|
|
| |
Fixes: https://todo.sr.ht/~taiite/senpai/91
|
|
|
|
|
| |
We don't care about them since we display the user away status using
MONITOR.
|
|
|
|
|
| |
This will allow to bring user attention when you are getting
highlighted.
|
| |
|
|
|
|
| |
Fixes: https://todo.sr.ht/~taiite/senpai/87
|
|
|
|
|
|
| |
Thanks steamyalt for the bug report.
Fixes: https://todo.sr.ht/~taiite/senpai/86
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, when running CTRL+N or CTRL+P to go to the next or previous
channel, with the horizontal channel mode, the selected channel could
appear offscreen.
This patch ensures that we scroll just enough to make the newly selected
chan visible.
Thanks to Nomeji for his hard work on this. Adapted slightly to
refactor existing code to use the newly created width computation
routine.
|
|
|
|
| |
Inspired by a patch from gildarts <gildarts@orbital.rocks>
|
|
|
|
| |
You'll need a recent soju version to use this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, when modifying a line in the history (and then possibly
sending it), the history was modified, meaning that when looking up
history lines again, instead of seeing a new line, the actual original
line had been modified.
With this patch, history is always kepy, and modifying a previous line
and sending it will add this line to the history, and restore the
previous history, after flushing the message.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To reproduce:
- Enter a message
- Enter a substring of that message, backsearch it
- Press backspace until the substring is cleared
- senpai crashes
This merely fixes the crash. We could do backsearch better in the future
but that's a whole feature overhaul to be done in its own patch.
Thanks to paren@disroot.org for helping me find the issue by sending a
panic trace :)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
See: https://github.com/ircv3/ircv3-specifications/pull/498
|
|
|
|
|
| |
It should mark the buffer as read if the last message was
before or at the "read" event, not after.
|
|
|
|
|
| |
It's confusing to search for something and have no results show if the
server doesn't support the soju.im/search capability.
|
|
|
|
|
| |
Following a pprof profiling, using fmt.Scanf was slow. time.Parse is
faster and more readable.
|
|
|
|
|
| |
This saves one round trip by letting us send BOUNCER LISTNETWORKS right
away and speeds up startup time.
|
|
|
|
| |
This will slightly speed up startup time.
|
|
|
|
|
|
| |
This heavily reduces CPU load on start, so that we only parse the links
of the current buffer hundreds of messages, rather than all of the
hundreds of messages * count of buffers.
|
| |
|
|
|
|
|
|
|
| |
This patch adds the ability to set a config option for changing the
foreground text color of unread buffers
(This was refactored slightly by delthas.)
|
| |
|
|
|
|
|
|
|
| |
This is inspired by a patch from mooff.
This keeps the same click & drag behavior as for the vertical channel
list.
|
|
|
|
|
|
| |
This is inspired by a patch by mooff.
The horizontal channel list can now be scrolled with the mouse wheel.
|
|
|
|
|
|
|
| |
This patch is inspired and modified from a patch by mooff.
Also this switches the default configuration to *display* the channel &
member list by default.
|
|
|
|
| |
This is a standard shortcut.
|
|
|
|
|
| |
Private messages are now sent to their own buffer, rather than in the
home buffer.
|
|
|
|
|
|
|
|
|
|
| |
Following a quick local profiling & benchmark, matching links with
regexes is by far (>50x) the most time-consuming processing we do,
especially on start.
Switching to a URL regex with any scheme is faster by a factor of ~x8,
probably because there are many less "or" cases between a list of 100+
schemes, instead using a simple character class.
|
|
|
|
|
|
|
|
|
|
| |
Previously, we would render every 64 events (at most).
Now that we have many more events, with history & read, batch events by
period rather than static size.
Waiting up to 200ms before refreshing is a good compromise between
responsiveness and performance.
|
|
|
|
| |
i.e. don't enter an infinite loop when printing disconnection errors :-)
|
|
|
|
|
|
| |
Also refactor ui/ to support overlays, temporary anonmyous buffers.
See: https://github.com/emersion/soju/pull/39
|
|
|
|
|
| |
My DSL line is awful atm, I'd like to know ASAP when I'm disconnected so
that I don't write paragraphs into the void.
|
| |
|