| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So that 1/ redundant events are removed even if people change nick in
the mean time and 2/ events that are actually not redundant are not
removed, e.g.
+val val->jw +dan dan->val -val
should be reduced to
+val val->jw
instead of
val->jw +dan dan->val
|
|
|
|
| |
Used back when senpai showed a random message at startup
|
| |
|
| |
|
|
|
|
|
|
| |
Initial history request: 200 -> 500
Infinite scroll request: 100 -> 200
Reconnect request: 200 -> 1000
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some servers might adjust their sasl cap at runtime, e.g.
CAP NEW sasl=PLAIN,EXTERNAL
[…]
CAP NEW sasl=PLAIN
In this case, we don't really want to `CAP REQ sasl` again, because
this will make us re-authenticate a second time.
Avoid requesting caps which have already been ACKed.
|
|
|
|
|
| |
Should solve duplicates on servers that don't store message stamps with
the full millisecond precision offered by the time tag (e.g. soju)
|
| |
|
|
|
|
| |
See https://github.com/ircv3/ircv3-specifications/pull/476
|
| |
|
| |
|
|
|
|
|
| |
3 is yellow, not green. The person who wrote this should really fix
their color scheme.
|
|
|
|
| |
This option no longer exists
|
|
|
|
|
| |
We wait until after AUTHENTICATE to send CAP END like a good client,
but it needs to be sent when SASL isn't used, too.
|
|
|
|
|
| |
Also, fix an issue where mode strings only displayed the first
parameter.
|
|
|
|
|
|
|
|
|
|
| |
- Refactor formatting lines into a function
- Store event times in the event
- Refactor merging lines into a function
- Always merge lines from the history, now that we will add mergeable
lines with CHATHISTORY
Successfully tested locally.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch replaces the YAML configuration format with scfg
(https://git.sr.ht/~emersion/scfg).
Additionally, a few things about configuration are cleaned up:
* abbreviated names are expanded (addr -> address, nick -> nickname)
* negative bools switched to positive (no-tls -> tls)
* independent column widths are grouped under the "pane-width"
directive
* implementation of default configuration values is improved
* password-cmd is executed directly (with scfg field parsing)
instead of with "sh -c".
* on-highlight is now a file, $XDG_CONFIG_HOME/senpai/highlight by
default, which can be changed with the on-highlight-path directive
|
| |
|
| |
|
| |
|
|
|
|
| |
See ticket #79 for more information
|
|
|
|
|
| |
This is namely useful when the terminal is closing: these events are
sent, and we should close when that happens (instead of panicking).
|
| |
|
|
|
|
| |
This lets open a buffer to a user without sending a message.
|
| |
|
|
|
|
|
| |
If there are multiple channels with the same name in several networks,
we should part from the one from the correct network.
|
| |
|
| |
|
|
|
|
| |
It simplifies the code and make registration use one less roundtrip
|
| |
|
|
|
|
| |
Otherwise it breaks infinite scrolling.
|
| |
|
|
|
|
|
| |
This reverts commit 96340f8c4d91f59f6e39767891f9bb52d7fad329 because of
a bug in timeline rendering.
|
| |
|
|
|
|
|
| |
I prefer this over printing the IRC formatted string, since the topic
should be printed in gray.
|
|
|
|
| |
We use os.WriteFile which is >=go1.16
|
| |
|
|
|
|
|
|
| |
This makes multi-line links properly clickable.
See: https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda
|
| |
|
| |
|
|
|
|
|
| |
The topic is the first line we put in a buffer, so we have to place the
first batch of history *before* the topic, instead of after.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Channels which have never received any message return no messages on the
initial chathistory, thus returning an empty bound with first == last ==
time.Time{}.
However this empty bound was stored in the channel bounds, and was used
as starting point for fetching history if Page Up was pressed. This in
turn caused senpai to send a CHATHISTORY BEFORE 01-01-0001 message,
which is invalid.
This fixes the issue by not storing an empty bound if the CHATHISTORY
request does not return any message.
|
|
|
|
| |
Seems like I really have too many channels... :)
|
|
|
|
|
| |
- Normalize usage display
- Sort commands alphabetically
|
| |
|