aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Use enterprise id in edgeapi path if it existsTrygve Aaberge2024-03-292-1/+3
| | | | | | | It seems like for enterprise workspaces you have to use the enterprise id (if the token is a workspace level token, `enterprise_id/workspace_id` can also be used, but isn't necessary), while for non-enterprise workspaces the workspace id should be used.
* Don't unnecessarily resolve nick an extra time for normal messagesTrygve Aaberge2024-03-291-2/+1
|
* Look for message hash before index in ts_from_hash_or_indexTrygve Aaberge2024-02-271-1/+4
| | | | | | | 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.
* Print error message from reply command if id/index isn't foundTrygve Aaberge2024-02-271-0/+3
|
* Add buffer localvar slack_mutedTrygve Aaberge2024-02-221-0/+1
| | | | This is 1 if the conversation is muted and 0 if it's not.
* Support date in rich text elementsTrygve Aaberge2024-02-212-0/+9
|
* Configure which files pyright runs on in pyproject.tomlTrygve Aaberge2024-02-212-1/+2
| | | | | | | | | | Move the configuration of which files pyright should run on from the CI command to pyproject.toml. Pyright is only configured to run on the main files for v3. So don't run it on the files for the old version of wee-slack, and don't run it on the util scripts. Ideally we would run it on the util scripts, but they give a lot of errors now, so we'd have to fix that first.
* Configure ruff files in pyproject.toml and run on most filesTrygve Aaberge2024-02-213-2/+3
| | | | | | | | | | | Move the configuration of which files ruff check should run on from the CI command to pyproject.toml and change it to run on most files. Exclude these files: - typings/weechat.pyi because it's copied from the WeeChat repo and I don't want errors from that. - wee_slack.py and _pytest because it's the old version, so there's no point spending time fixing lint errors there.
* Specify minimum python version for tools in pyproject.tomlTrygve Aaberge2024-02-214-6/+10
|
* Upgrade to the latest version of ruffTrygve Aaberge2024-02-212-24/+25
|
* Format built file after building if ruff is availableTrygve Aaberge2024-02-202-0/+13
|
* Upgrade all dependenciesTrygve Aaberge2024-02-206-38/+35
|
* Create nightly releases from masterTrygve Aaberge2024-02-201-0/+8
| | | | | This will update the nightly release with the latest build every time master is pushed to.
* Replace a str.format with an f-stringTrygve Aaberge2024-02-201-1/+1
|
* Add support for focus events (mouse/cursor mode)Trygve Aaberge2024-02-204-17/+114
|
* Add command `/slack linkarchive`Trygve Aaberge2024-02-202-0/+61
|
* Make api accessible from SlackBufferTrygve Aaberge2024-02-205-22/+22
|
* Move completion code to a separate fileTrygve Aaberge2024-02-206-360/+384
|
* Only reset foreground color in with_color functionTrygve Aaberge2024-02-196-24/+24
| | | | | | | The with_color helper is usually used to set only the foreground color (currently all usages), so by only reseting the foreground we keep any existing background color. This fixes the default background on the current buffer in the buflist for muted conversations.
* Add command `/slack mute`Trygve Aaberge2024-02-192-1/+39
|
* Refactor command functions to be asyncTrygve Aaberge2024-02-191-39/+26
|
* Support async command functionsTrygve Aaberge2024-02-191-6/+15
|
* Move set user profile functionsTrygve Aaberge2024-02-191-14/+14
|
* Don't require any arguments for `/slack join`Trygve Aaberge2024-02-181-1/+1
| | | | It will use the current buffer if no arguments are given.
* Fetch max 500 users in each requestTrygve Aaberge2024-02-181-1/+1
| | | | | Some users have gotten HTTP 500 from the API when trying to request 1000 users in one request.
* Don't print the same message multiple timesTrygve Aaberge2024-02-183-14/+32
| | | | | | | | | | 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.
* Add command `/slack part`Trygve Aaberge2024-02-184-12/+66
|
* Add an option to leave the channel when a buffer is closedTrygve Aaberge2024-02-184-1/+22
|
* Don't call conversations.leave when closed from serverTrygve Aaberge2024-02-183-12/+27
|
* Add command `/slack join`Trygve Aaberge2024-02-183-0/+79
| | | | | For now this only supports known channels, which currently typically means they have to be referenced in a channel with history loaded.
* Include all workspace nicks in nick completionTrygve Aaberge2024-02-181-5/+23
|
* Add command `/slack query` to open DM/MPDM channelsTrygve Aaberge2024-02-183-9/+96
| | | | | | For now this only supports known nicks, i.e. mostly nicks that have posted a message, is mentioned in a message or appears in the nicklist in any of the conversations that's loaded.
* Don't run buffer close callback when script is unloadingTrygve Aaberge2024-02-184-0/+6
| | | | | We don't want to call the API to close im/mpim conversations when the script is unloading.
* Unset _connect_task after cancelling itTrygve Aaberge2024-02-181-0/+1
| | | | | | | If _connect_task remains set, the connect command won't allow you to connect again because it thinks it's still connecting. This caused a problem where if you disconnect while connecting (or after connecting has crashed), it wasn't possible to connect again afterwards.
* Correctly show reactions with more than 50 users in v3.0.0Trygve Aaberge2024-02-185-10/+150
| | | | | | | | | | | If a reaction has more than 50 users, the list of users will be cropped to just 50 users. This made the counts wrong since we used the number of users rather than the count property. Fix it by using the count property instead and adding "and others" to the list of users if show_reaction_nicks is enabled (the same as the Slack client shows when you hover over the reaction). This is the same fix as in commit 6b388cd9, but for version 3.0.0.
* Support files in Slack Connect channelsTrygve Aaberge2024-02-185-84/+131
| | | | | | | | | Files uploaded in Slack Connect channels doesn't contain any information, so we have to make a request to files.info in order to get the information to render it. See https://api.slack.com/apis/channels-between-orgs#check_file_info for more info.
* Improve performance of rerender_history for WeeChat >= 4.0.0Trygve Aaberge2024-02-181-7/+32
| | | | | | | | | | | | | 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.
* Post users.profile.set as a JSON bodyTrygve Aaberge2024-02-185-85/+109
| | | | | It's better to post nested objects as JSON rather than url encoding them, and this fixes some type errors.
* Rename clean option in status to clearTrygve Aaberge2024-02-181-2/+2
|
* Set user statusPierguido Lambri2024-02-183-2/+60
| | | | | | | It's now possible to set and clear the uses status. For now it's not possible to set the status emoji or the status expiration. Signed-off-by: Pierguido Lambri <plambri@redhat.com>
* Set user user presence (#919)Pier2024-02-182-0/+22
| | | | | | | | | | | The user can now set the presence with: /slack presence away Or: /slack presence active Signed-off-by: Pierguido Lambri <plambri@redhat.com>
* Set buffer_pointer to None when buffer doesn't existTrygve Aaberge2024-02-184-28/+39
| | | | | | 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.
* Fix bots with multiple names only being added once to nicklistTrygve Aaberge2024-02-186-84/+42
| | | | | 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.
* Don't include external nick suffix when completingTrygve Aaberge2024-02-181-4/+4
| | | | | Mostly because it's a bit simpler not having to handle this suffix when linkifying text.
* Refactor nick handlingTrygve Aaberge2024-02-186-76/+76
|
* Handle messages without a user fieldTrygve Aaberge2024-02-185-47/+95
| | | | | | This can happen in channels shared between workspaces if one of the workspaces are removed. Then messages from users in that workspace will not have a user field anymore, but instead a user_profile field.
* Underline URL texts by defaultTrygve Aaberge2024-02-181-2/+2
|
* Unescape from_url in attachmentsTrygve Aaberge2024-02-181-1/+1
| | | | | | | | | | | | | | It looks like from_url should be unescaped, but title_link and image_url should not. Slack seems a bit inconsistent here though, as an image in an attachment will use the unescaped title_link, but the link in the title itself will use the original (possibly escaped) one. And the title for the image link will use the original (possibly escaped) title, while the title in the attachment will unescape it. I suppose you're not supposed to HTML escape (or Slacks version of it) URLs in title_link and image_url (which makes sense), but Slack does escape from_url if you send a message with a link to a thread message, so we have to handle that.
* Unescape file titlesTrygve Aaberge2024-02-182-30/+35
| | | | | Also mark a lot of fields as NotRequired as tombstone files doesn't have these fields.
* Support handling files that are not foundTrygve Aaberge2024-02-181-0/+5
|