| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
history_pending had a problem with being stuck as True if a crash
occurred. Additionally, only is_loading is shown in the input bar item,
so if only history_pending is True for some reason (which shouldn't
happen), it's not shown. I don't think I need a separate variable, so
instead of fixing history_pending, just use is_loading which doesn't
have these problems.
|
| |
|
|
|
|
|
| |
Otherwise a hash that's all digits can't be used without the $ prefix.
Message hashes are always at least three characters, so even though this
prevents using indexes that collides with a hash, I don't think it's a
problem as such large indexes doesn't seem practical anyways.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
When joining a channel you seem to get the last messages for it over the
WebSocket. When joining a channel you've parted and you still have the
buffer for open, those messages will already be in the buffer, so we
have to make sure their not printed multiple times.
I've also been told that messages can appear multiple times in the
reconnect brach, which this should fix too.
|
| | |
|
| | |
|
| |
|
|
|
| |
We don't want to call the API to close im/mpim conversations when the
script is unloading.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously each message was rerendered individually. This meant that for
each message, we start at the bottom of the buffer and go through all
the lines upwards until we find the message. So the lines were looped
through a lot of times which was slow. Now we instead go through all the
lines once, look up the message for each line and updates it.
This is only for >= 4.0.0 since earlier versions may have multiple lines
for each message (when the message has multiple lines). That would
complicate this way of updating the messages, and I don't think it's
worth implementing it when it's only for an old version.
|
| |
|
|
|
|
| |
This enforces us to check that buffer_pointer is set, so we don't
accidentally operate on the core buffer, which is what is done when
buffer_pointer is an empty string.
|
| |
|
|
|
| |
If a bot uses multiple nicks, we have to add all of them to the
nicklist, so none of the nicks are shown as offline.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This means a lot of methods don't have to be async. It's especially
useful for the next commit adding conversations completions.
|
| |
|
|
|
|
|
|
|
|
|
| |
Adds all known nicks in the current buffer with an @ prefix to the
nicks completion.
Disables the API search based nick completion for now until it's working
properly. It currently doesn't have any context of which
conversation/thread you are in, so you often get other nicks than the
one you want to complete first. Additionally, it doesn't work with OAuth
tokens.
|
| | |
|
| |
|
|
|
|
|
| |
This currently has the limitation that the user has to be known to
wee-slack for the mention to work. That is, there needs to be some
interaction with it (message or reaction from or mention) or it has to
be in the loaded members in any of the loaded conversations.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
When notify is none, the buffer should not appear in the hotlist even
for a highlight. However, when switching to the buffer, we want the line
to be highlighted. To achieve this use a tag added to highlight_tags on
the buffer.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Now notify tags are set based on last_read so both read and unread
messages gets the correct tags irregardless if they come from history or
websocket.
|
| | |
|
| | |
|
| |
|
