aboutsummaryrefslogtreecommitdiffstats
path: root/slack/slack_thread.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix bots with multiple names only being added once to nicklistTrygve Aaberge2024-02-181-13/+8
| | | | | 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.
* Refactor nick handlingTrygve Aaberge2024-02-181-1/+1
|
* Fix bugs with /slack reply commandTrygve Aaberge2024-02-181-2/+7
|
* Add command /slack replyTrygve Aaberge2024-02-181-1/+1
|
* Add completion of emoji namesTrygve Aaberge2024-02-181-1/+1
|
* Add completion for conversation namesTrygve Aaberge2024-02-181-0/+1
|
* Make conversations.name not asyncTrygve Aaberge2024-02-181-2/+2
| | | | | This means a lot of methods don't have to be async. It's especially useful for the next commit adding conversations completions.
* Support completing @nicks in current bufferTrygve Aaberge2024-02-181-1/+19
| | | | | | | | | | | 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.
* Support sending messagesTrygve Aaberge2024-02-181-0/+8
|
* Reload conversations on reconnectTrygve Aaberge2024-02-181-12/+22
|
* Add unread buffers to hotlist on connectTrygve Aaberge2024-02-181-3/+3
|
* Mark as read when switching away from bufferTrygve Aaberge2024-02-181-0/+15
|
* Correctly tag unread messages from historyTrygve Aaberge2024-02-181-1/+5
| | | | | | 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.
* If a message has a user, use that even though it's a bot_messageTrygve Aaberge2024-02-181-1/+5
| | | | | | | | | Messages from Slackbot apparently have both a user and a bot_id, and sometimes have the subtype bot_message, other times not. However, the bot_id is B01 which gives bot_not_found when trying to look it up. I see that the web client shows it with the user profile, and doesn't show the message as a bot message, so do that here as well to match it and avoid the invalid bot_id.
* Fetch thread replies when receiving thread messageTrygve Aaberge2024-02-181-3/+1
| | | | | | This is done so we can know if we should include a message hash when completing thread hashes, and it also has the benefit of eliminating the loading time when opening thread buffers.
* Support thread buffersTrygve Aaberge2024-02-181-0/+87