| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Without spaces, WeeChat will consider all the nicks as one word, which
means that rather than wrapping between nicks, it will fill the whole
line and wrap in the middle of nicks. Additionally, if you have disabled
weechat.look.align_multiline_words it will start from the beginning of
the line when wrapping, rather than after the prefix, which doesn't look
nice.
|
|
|
|
|
| |
Remove a space before a colon and add a comma after a sentence starting
with if.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The url_private link for Slack posts just downloads a json of the post,
which isn't very useful to click on. The permalink goes to the web view
for a post, which is what we want. The web client adds origin_team and
origin_channel, which makes the post page show info about where the post
is shared, so add that here as well.
We still want to use url_private for images etc., not permalink there as
well, because that links to the Slack client with the image shown in the
sidebar, which is much more inconvenient than just getting the image
directly.
|
|
|
|
|
|
|
|
| |
If a link preview was added by an app, like GitHub, instead of directly
by Slack, it was not detected by wee-slack as a link preview, so it
would be shown even if link_previews was set to false.
Fixes #834
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
One user experiences receiving a "HTTP/1.1 200 Connection established"
header block before a "HTTP/2 200" header block with the headers. I'm
not sure why specifically this happens, but I know a similar response
will happen if redirects are followed.
This wasn't supported by the http_check_ratelimited function which
splits the header from the body. It now splits out all the header blocks
from the body and uses the status and headers from the last one.
|
|
|
|
| |
Fixes #871
|
|
|
|
|
| |
This is only required for WeeChat < 1.5, and we require >= 2.2, so
there's no point in keeping this.
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
When slack return a button message type and a url field is present we
should output the URL.
Fix: #811 and #810
|
|\
| |
| |
| | |
Support new session tokens (xoxc tokens) and replace the usage of
rtm.start (which will soon stop working) with other API methods.
|
| | |
|
| |
| |
| |
| |
| | |
Limit should be used now, so it seems like count has been renamed to
limit.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
On one of my Slack teams, none of the MPIMs are included in
conversations.list if types include public_channel for some reason.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
According to one comment it was necessary for them to include this
cookie as well.
|
| | |
|
| |
| |
| |
| | |
The individual teams in the enterprise grid is still listed.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
This is a necessary step for #844
|
| |
| |
| |
| |
| | |
I don't think these are necessary. I've not experienced any errors
after removing them.
|
|/
|
|
|
|
|
|
|
|
|
| |
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
|