aboutsummaryrefslogtreecommitdiffstats
path: root/wee_slack.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove compatibility for irc_nick_color_nameTrygve Aaberge2022-10-081-2/+1
| | | | | This is only required for WeeChat < 1.5, and we require >= 2.2, so there's no point in keeping this.
* Update WeeChat version check to require >= 2.2Trygve Aaberge2022-10-081-2/+2
| | | | | | | After moving the token in Slack API requests from a query string param to an Authorization header in commit 2185a58 we require WeeChat >= 2.2 because that was the version which added support for setting HTTP headers.
* Open open IMs and MPIMs on startTrygve Aaberge2022-10-041-0/+2
| | | | | | | | | | | | | We used the response from rtm.start to find which IMs and MPIMs to open, but after moving away from that we didn't have the information from the response from conversations.list, so commit 962bbc5 changed to only open unread ones. However, it turns out that conversations.info has the information, and we are already requesting that for each IM/MPIM to check if it's unread, so we can use that to open the correct ones. Fixes #875
* Fix old type MPIMs not being marked as unread on startTrygve Aaberge2022-10-041-1/+1
| | | | | | | | Old type MPIMs (has `is_group: true`) has `is_open`, but not `unread_count_display` in the response from `conversations.list`, so they were not marked as unread on start if background_load_all_history was set to false because we have to request the history, but `check_should_open` created the buffer, so it wasn't requested here.
* Fall back to bot_id as nick if no other info is availableTrygve Aaberge2022-10-021-1/+1
| | | | | | | | | | Apparently there are some bots which are not listed in users.list and which sends messages where the only info about the sender is a bot_id. To fix this properly we will have to look up the bot with bots.info when we encounter an unknown bot_id, but for now just fall back to using the id directly like we do with unknown users to make it possible to use triggers and filters.
* Update script author to myselfTrygve Aaberge2022-10-021-2/+2
| | | | | I've been the maintainer of this script for several years now, and Ryan isn't involved anymore, so it makes sense to update the script author.
* Update usage of deprecated WeeChat API methodsTrygve Aaberge2022-10-021-16/+24
| | | | | The script will use the new methods if the WeeChat version is new enough, and the old deprecated methods if it's too old for the new ones.
* Release v2.9.0v2.9.0Trygve Aaberge2022-09-191-1/+1
|
* Fix compatibility with Python 2Trygve Aaberge2022-09-191-9/+7
|
* Reformat code after last commitTrygve Aaberge2022-09-191-1/+1
|
* feat(display): Add URL when slack block contain URL (#863)Romain THERRAT2022-09-191-0/+2
| | | | | | When slack return a button message type and a url field is present we should output the URL. Fix: #811 and #810
* Fix limit parameter in history requestTrygve Aaberge2022-09-181-1/+1
| | | | | Limit should be used now, so it seems like count has been renamed to limit.
* Check if channel is mpim before shared on loadTrygve Aaberge2022-09-181-2/+2
| | | | | | On one of my teams, all the MPIMs have is_shared set to true and the name is not set correctly if they are created as SlackSharedChannel instead of SlackMPDMChannel.
* Load list of MPIMs separately on startTrygve Aaberge2022-09-181-14/+26
| | | | | On one of my Slack teams, none of the MPIMs are included in conversations.list if types include public_channel for some reason.
* Fix /query not working for new MPIMsTrygve Aaberge2022-09-181-18/+34
|
* Support retrying requests when ratelimitedTrygve Aaberge2022-09-181-48/+87
|
* Gracefully handle user_is_restricted error on initial loadTrygve Aaberge2022-09-181-1/+10
| | | | | | If you are a guest on a team, requesting the user groups may fail with this error. Instead of failing the whole startup, report an error and continue.
* Support including the d-s cookieTrygve Aaberge2022-09-181-1/+5
| | | | | According to one comment it was necessary for them to include this cookie as well.
* Support specifying both url encoded and raw (not url encoded) cookiesTrygve Aaberge2022-09-181-3/+15
|
* Don't open all DMs and MPDMs on startTrygve Aaberge2022-09-181-11/+32
| | | | | | | | Instead open only unread DMs and MPDMs. Unfortunately it doesn't seem to be possible to know which DMs or MPDMs are open from the last run or in the official client (without using internal APIs). We could explore alternatives like opening the ones with recent messages, or storing which are open, but this will have to do for now.
* Handle conversations.info for all typesTrygve Aaberge2022-09-181-18/+11
| | | | | | This sets last_read on the channel, though we have no guarantee that we get the result from info before history, and if we get history first, the read messages will still be marked as unread.
* Use SlackRequest options in file downloadTrygve Aaberge2022-09-181-1/+2
|
* Show which requests fail at startupTrygve Aaberge2022-09-181-6/+7
|
* Check if members is not empty in SlackMPDMChannelTrygve Aaberge2022-09-171-1/+1
| | | | | | If you use an xoxc token, the conversations.list endpoint returns an empty list for members of mpdms that have is_group set to true, which made this fail.
* Support specifying an auth cookie in slack_api_tokenTrygve Aaberge2022-09-171-1/+13
| | | | | | | | | | | | This is necessary for xoxc tokens. The cookie is specified after the token with a colon separating them, i.e. "token1,token2:cookiefor2,token3". This makes slack_api_token even more inconvenient, but it will have to do until we rewrite the config to have a section for each team, like the irc config has. Fixes #844
* Support specifying cookies in SlackRequestTrygve Aaberge2022-09-171-9/+28
| | | | This is a necessary step for #844
* Remove empty hook_process_hashtable callsTrygve Aaberge2022-09-171-3/+0
| | | | | I don't think these are necessary. I've not experienced any errors after removing them.
* Support starting wee-slack without using rtm.startTrygve Aaberge2022-09-171-21/+256
| | | | | | | | | | | rtm.start is deprecated and will stop working on September 20, 2022. This patch replaces it with several other API endpoints to get the info we need. The handle_rtmstart method is kept for the test setup to work, but this setup should also be replaced with the new API endpoints. This is a necessary step for #699 and #844
* Don't crash on missing mode on files in messagesTrygve Aaberge2022-09-171-1/+1
|
* Use correct parameter name for info requestTrygve Aaberge2022-09-171-1/+1
|
* Fix tests and formatting after last commitTrygve Aaberge2022-09-171-3/+3
|
* Check closed IM channels for unread messages (#859)Daniel Nelson2022-09-171-0/+17
| | | | | On connection check closed IM channels for unread messages and if any are found open a buffer. This ensures that new direct messages are not missed.
* Fix message changes not being processedTrygve Aaberge2022-01-311-1/+2
| | | | | | | | | | | | | The Slack API has changed message_changed events from having a unique ts to having the ts of the message that's changed, which means that the condition in the start of process_message to not process duplicate messages (see commit 68966be for info about that) made it skip the message_changed events. To fix this, only do this duplication check for messages without a subtype (i.e. new normal messages). This condition is becoming a bit convoluted, so it might be better to do this duplication check another way, but this will have to do for now to get the issue fixed.
* Fix formatting after black upgradeTrygve Aaberge2022-01-301-9/+5
|
* Fix alignment of multiline messages with non-ASCII prefix. (#854)bemoody2021-11-161-1/+2
| | | | | | | | | | | | On Python 2, weechat.string_remove_color doesn't work for Unicode strings containing non-ASCII characters. The string must be converted to bytes using encode_to_utf8. Furthermore, the length of a non-ASCII string (either in bytes or codepoints) isn't the same as the width of the string on screen. To accurately calculate the width, when the string might contain combining or double-width characters, use weechat.strlen_screen. Co-authored-by: Benjamin Moody <benjaminmoody@gmail.com>
* Validate token not empty, before initiate connection (#853)Inom2021-11-161-1/+5
| | | | | | | | | | I continuously received this error: ``` AttributeError: 'NoneType' object has no attribute 'token' ``` Because tokens list was `['', '']`. And wee-chat tried initiate connections without tokens. This small change fix this error.
* Don't unhide buffers when reprinting messages (#839)Kevin Pulo2021-06-231-0/+1
|
* Remove Python >= 3.6 only syntaxTrygve Aaberge2021-06-231-1/+1
| | | | This comma broke compatibility with Python 2.7, so remove it.
* Fix alignment of multiline messagesTrygve Aaberge2021-05-261-2/+5
| | | | | | When `weechat.look.prefix_align` is set to `none`, lines after the first in a message would not align with the first. Use the same number of spaces as the prefix for those lines, so they align with the first.
* Release v2.8.0v2.8.0Trygve Aaberge2021-05-111-1/+1
|
* Add compatibility with WeeChat >= 3.2 (XDG directories)Sébastien Helleu2021-05-111-3/+8
|
* Support MPIMs in channel list of rtm.startTrygve Aaberge2021-05-111-14/+36
| | | | | | | | | | | For some reason, some MPIMs are listed in the channel list of the response from rtm.start, with is_mpim set to true, instead of in the mpims list. These incorrectly appeared as private channels instead of MPIMs in wee-slack. These entries do not contain a members list, so we have to call conversations.members and set the name after receiving the response from that.
* Add indicator for broadcast thread messages (#838)Bill Doyle2021-05-111-1/+13
|
* Support mpim_aware RTM APITrygve Aaberge2021-05-081-13/+24
| | | | | | | | | | | | Apparently, the API now sends an mpim_joined event when an MPIM is created instead of a group_joined event, even if we don't set mpim_aware to true. Instead of just handling mpim_joined in addition to group_joined (which could cause issues if both are called for MPIMs, though I haven't experienced that), it's better to properly support mpim_aware. Fixes #825, fixes #833
* Include channel name in file names for downloaded filesTrygve Aaberge2021-04-301-4/+6
| | | | Fixes #836
* Ignore failing flake rules instead of selecting only a fewTrygve Aaberge2021-04-131-1/+5
| | | | E203 should be ignored when using black according to their docs.
* Fix some flake8 errorsTrygve Aaberge2021-04-131-2/+2
|
* Some code cleanup from lgtm.com checksTrygve Aaberge2021-04-121-17/+18
|
* Call conversations.members for all channelsTrygve Aaberge2021-03-211-1/+4
| | | | | | | | | It turns out that some channels in rtm.start include a member list with a few users, but not all. Therefore, I don't know how we can know if the list is complete or not, so we have to call conversations.members for all channels. Fixes #829
* Call conversations.members for all channel typesTrygve Aaberge2021-03-211-22/+9
| | | | | | | | | | I'm not sure when members for a channel is included in rtm.start, but it seems like shared and private channels doesn't include the field at all, while some other channels have started to only include the user. Therefore, call conversations.members if a channel doesn't have any members or if the only member is the user. Hopefully this fixes #829
generated by cgit (git 2.34.1) at 2024-11-11 00:39:00 +0000