| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
| |
When installing on OpenBSD, you need to specify the Python 3 version (not Python 2)
|
| |
|
|
|
| |
This can be used when you want to remove a team, so you know which token
to remove.
|
| |
|
|
|
|
|
|
|
| |
When new replies come in over websocket, we don't update the
message_json of the parent message with the new replies, we just append
the new message to the submessages list. Therefore, the
number_of_replies function has to check both of these and take the max.
Fixes #722
|
| | |
|
| |
|
|
|
|
| |
It tooked me a while to figure out why weechat says that websocket module was not found in wee-slack plugin.
pip list sayed websocket-client was installed.
after installing pip3 and websocket-client with pip3, everything worked fine.
The current ubuntu 19.04 `python-websocket` package has always installed the python2.7 version.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is for channels which initially were public, but then are changed
to private. They look the same as groups (channels initially created as
private) in the official clients, but can only be used with the
conversations api. They are listed in the channels list of rtm.start
with is_private set to true.
There are some remaining issues, which are documented in the readme.
I'm not sure if we can support read sync and showing unread on load
without changes from Slack to the API.
Showing thread messages in the channel is possible to fix, but we would
have to send requests to load the thread history for all the messages in
the history that has replies.
Fixes most of #644
|
| |
|
|
| |
Fixes #620
|
| | |
|
| |
|
|
| |
Fixes parts of #714
|
| |
|
|
|
|
|
|
| |
This was broken in commit 6f9339b.
I haven't verified that is_member is set to the correct value when a
user group is created, because I don't have access to a slack team where
I can create user groups right know.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Also shows if you are a member or not in the command /slack usergrous.
Fixes #272, fixes #367, fixes #542
|
| |
|
|
|
| |
This allows you to complete nicks without a leading @ in buffers we
don't show the nicklist, i.e. the team buffer and thread buffers.
|
| | |
|
| |
|
|
| |
Fixes #698
|
| |
|
|
|
|
|
|
| |
If we don't linkify users, only usernames (which are not shown anymore)
are accepted by the chat.command endpoint, not display names. It does
accept user links, so we can use that. However, it doesn't seem to
accept channel links (at least the invite command, which is what I
tested), so we only linkify users.
|
| |
|
|
| |
Fixes #369, fixes #374
|
| |
|
|
| |
We should always use w, so we go through the WeechatWrapper.
|
| |
|
|
| |
So it doesn't try to connect to the websocket when running the tests.
|
| |
|
|
|
|
| |
I don't know all the possible prefixes, and I don't think it's a problem
to just match # and @. The prefixes I've seen for channels are #C, #D
and #G, and for users @U and @W.
|
| |
|
|
|
| |
Instead of splitting the message at spaces and checking and replacing
each word, use re.sub for the whole message.
|
| | |
|
| | |
|
| |
|
|
|
| |
Instead of finding each match and calling replace on the text with that
match, use re.sub to replace all the matches.
|
| |
|
|
|
|
|
|
| |
@group isn't mentioned in the documentation[0], and is changed to
@channel if you try to complete it in the web client, so it probably
shouldn't be used anymore.
[0]: https://get.slack.help/hc/en-us/articles/202009646-Notify-a-channel-or-workspace
|
| |
|
|
|
|
|
|
|
| |
This is for the notifications @channel, @everyone, @group and @here.
@group isn't mentioned in the documentation[0], but it is still rendered
as a highlight in the web client, so I included it.
[0]: https://get.slack.help/hc/en-us/articles/202009646-Notify-a-channel-or-workspace
|
| | |
|
| |
|
|
| |
Fixes #587
|
| |
|
|
| |
Subteams/usergroups should never be used without the @.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This includes the prefix that shows the channel type.
|
| | |
|
| |
|
|
| |
Fixes #703
|
| |
|
|
| |
Fixes #100
|
| |
|
|
|
|
|
| |
The username can't be changed by the users themselves now and is auto
generated for new users, so we shouldn't use it. Only use username as a
last resort if neither display name nor full name is set (I'm not sure
this ever happens, it looks like the full name field is mandatory).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attachment fields are not guaranteed to have a title at all.
This fixes in particular slackbot app approval messages, with an
attachment like so:
{
"callback_id": "whitelist_A11BCGM0E_181389840855",
"fields": [
{
"short": true,
"value": ":white_check_mark: *<@U4RPXA42F|davo> approved this app for the team.*"
}
],
"fallback": "Approve or deny the application",
"id": 4,
"color": "#2ab27b"
}
|
| | |
|
| |
|
| |
Also hide any unset fields.
|
| |
|
|
|
| |
This prevents printing an error when running /away without -all on
buffers other than slack buffers.
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #697
|
| | |
|
| | |
|
| | |
|
