Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Make conversations.name not async | Trygve Aaberge | 2024-02-18 | 6 | -53/+78 |
| | | | | | 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 buffer | Trygve Aaberge | 2024-02-18 | 4 | -6/+80 |
| | | | | | | | | | | | 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 bold/italic attributes when sending messages | Trygve Aaberge | 2024-02-18 | 1 | -1/+5 |
| | |||||
* | Support mentioning users | Trygve Aaberge | 2024-02-18 | 1 | -3/+24 |
| | | | | | | | 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. | ||||
* | Support group broadcast refs | Trygve Aaberge | 2024-02-18 | 1 | -2/+3 |
| | | | | This is an alias for @channel. | ||||
* | Support open/close/joined/left conversation events | Trygve Aaberge | 2024-02-18 | 3 | -2/+72 |
| | |||||
* | Close IM/MPIM and remove from open_conversations on buffer close | Trygve Aaberge | 2024-02-18 | 2 | -0/+19 |
| | |||||
* | Open closed IM/MPIM buffers on new messages | Trygve Aaberge | 2024-02-18 | 1 | -5/+11 |
| | |||||
* | Show user status in DM buffer title | Trygve Aaberge | 2024-02-18 | 7 | -33/+78 |
| | |||||
* | Check if closed IMs/MPIMs have unread messages on start | Trygve Aaberge | 2024-02-18 | 1 | -3/+15 |
| | | | | | Sometimes an IM/MPIM can have unread messages even when is_open is false, so we have to check the history if there are any unread messages. | ||||
* | Show conversation topic in buffer title | Trygve Aaberge | 2024-02-18 | 5 | -3/+35 |
| | |||||
* | Handle when some items are missing from the response | Trygve Aaberge | 2024-02-18 | 2 | -6/+21 |
| | |||||
* | Log connected/disconnected from workspace | Trygve Aaberge | 2024-02-18 | 1 | -0/+3 |
| | | | | | We should create a server buffer for each workspace, but print to the core buffer for now. | ||||
* | Log unknown websocket messages to debug buffer instead of core | Trygve Aaberge | 2024-02-18 | 1 | -5/+14 |
| | | | | | This just logs that a message is unknown/unhandled. The contents of the message will be printed on the line above. | ||||
* | Fetch all mentioned users at once in fill_history | Trygve Aaberge | 2024-02-18 | 2 | -8/+23 |
| | |||||
* | Don't crash when message for hash is missing | Trygve Aaberge | 2024-02-18 | 1 | -6/+7 |
| | | | | | We can have a hash for a message we don't have if e.g. a broadcast reply is sent, and the parent is older than the history we have fetched. | ||||
* | Print error when loosing connection, for debugging | Trygve Aaberge | 2024-02-18 | 1 | -2/+2 |
| | |||||
* | Handle unknown user/bot when adding to nicklist | Trygve Aaberge | 2024-02-18 | 1 | -12/+24 |
| | |||||
* | Handle errors when looking up chat items | Trygve Aaberge | 2024-02-18 | 2 | -16/+69 |
| | |||||
* | Fix bug with setting bool config values | Trygve Aaberge | 2024-02-18 | 2 | -3/+6 |
| | |||||
* | Use one debug buffer for all debug logging | Trygve Aaberge | 2024-02-18 | 5 | -56/+79 |
| | | | | | I will implement filtering like the /server raw buffer, instead of having multiple debug buffers. | ||||
* | Add tests for attachments and fix rendering bugs | Trygve Aaberge | 2024-02-18 | 5 | -37/+755 |
| | |||||
* | Apply code block styles first | Trygve Aaberge | 2024-02-18 | 2 | -5/+61 |
| | | | | | | | It looks better to have the `` characters around the other styles when there's styling inside code blocks. It makes it look a bit worse when theres code blocks inside styled text though. It should really remember the order the styles are opened to close them in the correct order. | ||||
* | Add render blocks tests from old version | Trygve Aaberge | 2024-02-18 | 3 | -6/+393 |
| | |||||
* | Catch errors when rendering message | Trygve Aaberge | 2024-02-18 | 1 | -20/+27 |
| | |||||
* | Support editing and deleting messages | Trygve Aaberge | 2024-02-18 | 3 | -20/+119 |
| | |||||
* | Support adding and removing reactions | Trygve Aaberge | 2024-02-18 | 5 | -4/+89 |
| | |||||
* | Only use letters for message hashes | Trygve Aaberge | 2024-02-18 | 1 | -1/+3 |
| | | | | This way it doesn't collide with message indices. | ||||
* | Upgrade dependencies | Trygve Aaberge | 2024-02-18 | 1 | -12/+12 |
| | |||||
* | Support sending messages | Trygve Aaberge | 2024-02-18 | 7 | -15/+66 |
| | |||||
* | Apply highlights in chat even when notify is none | Trygve Aaberge | 2024-02-18 | 3 | -1/+11 |
| | | | | | | | 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. | ||||
* | Support muted conversations config | Trygve Aaberge | 2024-02-18 | 7 | -6/+115 |
| | |||||
* | Add some basic tests for SlackMessage._unfurl_refs | Trygve Aaberge | 2024-02-18 | 2 | -1/+195 |
| | |||||
* | Add some repr methods for useful debug printing | Trygve Aaberge | 2024-02-18 | 3 | -1/+10 |
| | |||||
* | Remove color suffix from color option | Trygve Aaberge | 2024-02-18 | 2 | -10/+10 |
| | | | | It's redundant to have this when the options are in the color section. | ||||
* | Support highlight notifications without rendering history | Trygve Aaberge | 2024-02-18 | 3 | -329/+383 |
| | |||||
* | Don't show disconnected status when connecting | Trygve Aaberge | 2024-02-18 | 1 | -2/+5 |
| | |||||
* | Update message when subscribed/unsubscribed | Trygve Aaberge | 2024-02-18 | 3 | -13/+46 |
| | | | | | | Pyright doesn't allow me to set subscribed/last_read in _message_json since some of the _message_json types don't have them, so had to use separate attributes. | ||||
* | Reload conversations on reconnect | Trygve Aaberge | 2024-02-18 | 5 | -30/+125 |
| | |||||
* | Reduce priority of input_text_display_with_cursor modifier | Trygve Aaberge | 2024-02-18 | 1 | -1/+1 |
| | | | | | | | | | This may conflict with go.py if it has an equal or higher priority than that, which causes go.py to not show any buffers. So set it to a low priority so it doesn't conflict with anything else. Since this only prepends to the input string and doesn't read the string, I think it could have the lowest priority, but leave some room for lower priorities just in case another hook needs it. | ||||
* | Raise error if both error and response_code is missing | Trygve Aaberge | 2024-02-18 | 1 | -0/+9 |
| | | | | | I experienced a KeyError on response_code and not sure when that could happen, so log the output to check it if it happens again. | ||||
* | Add unread buffers to hotlist on connect | Trygve Aaberge | 2024-02-18 | 5 | -8/+29 |
| | |||||
* | Use notify_private tag in private buffers | Trygve Aaberge | 2024-02-18 | 2 | -7/+36 |
| | |||||
* | Mark as read when switching away from buffer | Trygve Aaberge | 2024-02-18 | 9 | -5/+117 |
| | |||||
* | Update message_json dict rather than replacing it | Trygve Aaberge | 2024-02-18 | 1 | -1/+3 |
| | | | | | In the message_replied event, the message json doesn't include all properties, so `subscribed` and others were removed when we replaced it. | ||||
* | Mark buffer as read when conversation/thread is marked | Trygve Aaberge | 2024-02-18 | 5 | -0/+102 |
| | |||||
* | Set unread marker after last read message | Trygve Aaberge | 2024-02-18 | 1 | -0/+2 |
| | |||||
* | Correctly tag unread messages from history | Trygve Aaberge | 2024-02-18 | 4 | -7/+28 |
| | | | | | | 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. | ||||
* | Split users.info into multiple requests when necessary | Trygve Aaberge | 2024-02-18 | 2 | -2/+56 |
| | | | | | | If you try to request several thousand users in one request (not sure exactly what the limit is), it just returns HTTP 500, so split it into multiple requests with a max of 1000 users per request. | ||||
* | Get all reaction users in one request | Trygve Aaberge | 2024-02-18 | 2 | -2/+15 |
| |