| Commit message (Collapse) | Author | Files | Lines |
|---|
|
- more colors settings:
- server foreground
- channel foreground (active, inactive)
- dumb cosmetic changes because why not (`!` -> `:(`, coloring)
- temporary lines to unclutter main ui from disconnections/reconnections
- display line head only once in case of multiple lines
- cosmetic motd
- handle 396 numeric as "server" head
- improved ACTION display
- imrpoved topic display
bugs:
- ACTION fucks up with multi-line head
- multi-line head needs rework before trying upstream
- what the fuck to with my cosmetic changes
- document new config values
|
|
Previously, we did not clear buffers highlight statuses on MARKREAD if
there was any unread line after it.
This meant that if we received a plain message, than a join message, and
some other device sent us a read marker for the plain message, we would
still highlight the buffer. But we should not: a join message should not
highlight the buffer.
This is a recurrent use case because some clients do not display join
mesasges and therefore do not send read markers for it.
This updates the logic to actually store the notify level (in the line)
and uses it to reset the highlight status when only NotifyNone messages
(or no messages) are left.
|
|
Using man to learn more about senpai is obvious. Using /help is more
specific to senpai.
Mention that rather than the man.
|
|
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
|
|
Private messages are now sent to their own buffer, rather than in the
home buffer.
|
|
This patch also disable the highlight on reconnect. This might be an
issue (the user would want to know when senpai is online again?), but
with multiple connections, it's bothersome to have to unread all of
them on start (it wasn't a problem with only one connection since it was
read instantly).
Now, lastbuffer.txt also contains the network ID, otherwise the user
might end up on another buffer with the same name.
This patch does not extend /r to support multiple networks (it will send
the message to the latest query, whatever the current displayed network
is).
|
|
|
|
Saves space
also removed non-edition related method IsCommand out of editor.go
|
|
Namely, we want the unread light to show up only on actual messages, not
commands etc.
This opens the way for not showing an unread light when printing topic
on join.
|
|
So that the colors go well with the terminal background.
|
|
Refactor:
- Split out reads/writes from irc.Session to irc.ChanInOut,
- Message handling is now manual, messages must be passed to
irc.Session.HandleMessage for its state to change,
- Remove data-race-prone App.addLineNow (called from both the main
eventLoop and irc loops) and add App.addStatusLine (to be called from
the main event loop) and App.queueStatusLine (to be called from other
goroutines). These two functions now write to both the current buffer
and the home buffer,
- add a irc.Typings.List function that locks the list of typings before
accessing it.
Changes as I went through the whole code...
- CAP handling is fixed (especially CAP DEL and CAP ACK),
- irc.Session now handles PREFIX,
- unhandled messages are now shown, except for some rare cases where
it's completely useless to show them.
|
|
|
|
|
|
- Centralize message formatting
- Make line formatting more flexible
- Provide more information in irc events
- Refactor command handling
- Add a /help command
- Make /me reply to last query if from home
- Enforce argument for /me
- Make BufferList and Editor public
- Batch processing of IRC events
|
