aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Log connected/disconnected from workspaceTrygve Aaberge2024-02-181-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 coreTrygve Aaberge2024-02-181-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_historyTrygve Aaberge2024-02-182-8/+23
|
* Don't crash when message for hash is missingTrygve Aaberge2024-02-181-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 debuggingTrygve Aaberge2024-02-181-2/+2
|
* Handle unknown user/bot when adding to nicklistTrygve Aaberge2024-02-181-12/+24
|
* Handle errors when looking up chat itemsTrygve Aaberge2024-02-182-16/+69
|
* Fix bug with setting bool config valuesTrygve Aaberge2024-02-182-3/+6
|
* Use one debug buffer for all debug loggingTrygve Aaberge2024-02-185-56/+79
| | | | | I will implement filtering like the /server raw buffer, instead of having multiple debug buffers.
* Add tests for attachments and fix rendering bugsTrygve Aaberge2024-02-185-37/+755
|
* Apply code block styles firstTrygve Aaberge2024-02-182-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 versionTrygve Aaberge2024-02-183-6/+393
|
* Catch errors when rendering messageTrygve Aaberge2024-02-181-20/+27
|
* Support editing and deleting messagesTrygve Aaberge2024-02-183-20/+119
|
* Support adding and removing reactionsTrygve Aaberge2024-02-185-4/+89
|
* Only use letters for message hashesTrygve Aaberge2024-02-181-1/+3
| | | | This way it doesn't collide with message indices.
* Upgrade dependenciesTrygve Aaberge2024-02-181-12/+12
|
* Support sending messagesTrygve Aaberge2024-02-187-15/+66
|
* Apply highlights in chat even when notify is noneTrygve Aaberge2024-02-183-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 configTrygve Aaberge2024-02-187-6/+115
|
* Add some basic tests for SlackMessage._unfurl_refsTrygve Aaberge2024-02-182-1/+195
|
* Add some repr methods for useful debug printingTrygve Aaberge2024-02-183-1/+10
|
* Remove color suffix from color optionTrygve Aaberge2024-02-182-10/+10
| | | | It's redundant to have this when the options are in the color section.
* Support highlight notifications without rendering historyTrygve Aaberge2024-02-183-329/+383
|
* Don't show disconnected status when connectingTrygve Aaberge2024-02-181-2/+5
|
* Update message when subscribed/unsubscribedTrygve Aaberge2024-02-183-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 reconnectTrygve Aaberge2024-02-185-30/+125
|
* Reduce priority of input_text_display_with_cursor modifierTrygve Aaberge2024-02-181-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 missingTrygve Aaberge2024-02-181-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 connectTrygve Aaberge2024-02-185-8/+29
|
* Use notify_private tag in private buffersTrygve Aaberge2024-02-182-7/+36
|
* Mark as read when switching away from bufferTrygve Aaberge2024-02-189-5/+117
|
* Update message_json dict rather than replacing itTrygve Aaberge2024-02-181-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 markedTrygve Aaberge2024-02-185-0/+102
|
* Set unread marker after last read messageTrygve Aaberge2024-02-181-0/+2
|
* Correctly tag unread messages from historyTrygve Aaberge2024-02-184-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 necessaryTrygve Aaberge2024-02-182-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 requestTrygve Aaberge2024-02-182-2/+15
|
* Support overriding display_reaction_nicks per bufferTrygve Aaberge2024-02-183-2/+10
|
* Prefix private conversations with &Trygve Aaberge2024-02-181-2/+4
|
* Open conversations in sorted order by nameTrygve Aaberge2024-02-182-6/+31
|
* Add an option for what to replace space in nicks withTrygve Aaberge2024-02-182-2/+11
|
* Unfurl refs in text blocksTrygve Aaberge2024-02-181-8/+18
|
* Check that script loads in WeeChat in CITrygve Aaberge2024-02-182-14/+36
|
* Build in CI and upload as artifactTrygve Aaberge2024-02-182-1/+10
|
* Update CI to use poetry and run the relevant checksTrygve Aaberge2024-02-181-14/+6
|
* Include cookie when making the websocket connectionTrygve Aaberge2024-02-181-0/+1
| | | | Slack began to require this for xoxc tokens today.
* Don't add to nicklist for imsTrygve Aaberge2024-02-181-2/+4
|
* If a message has a user, use that even though it's a bot_messageTrygve Aaberge2024-02-183-19/+19
| | | | | | | | | 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.
* Highlight messages with mentionsTrygve Aaberge2024-02-182-18/+82
|
generated by cgit (git 2.34.1) at 2024-11-15 02:32:49 +0000