| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a `show_presence_presence` config option that defaults to
true. When true, the `+` appears before present users in the buffer
list, as they did before this commit. But when false, the `+` mark is
omitted and presence is no longer shown.
This helps users who want their terminal programs to flag activity but
don't consider presence changes to be activity worth flagging.
|
|
|
|
|
| |
This is for users with a team that has restricted which apps that can be
installed in Slack.
|
| |
|
| |
|
|
|
|
|
| |
This option allows a user to set a custom color to the (edited)
suffix on messages that have been edited.
The default color is set to '095', as it was the former choice.
|
|
|
|
| |
* fixes #618
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If `short_buffer_names` is set, the buffer names doesn't contain slack,
so the bindings that was set didn't work. In order to make the bindings
work for these users by default, bind to all python buffers instead,
because we are not able to differantiate these buffers from other python
buffers.
wee-slack won't overwrite existing bindings so this won't break anyones
setup. Users with these bindings already set will just have to set the
bindings themselves. None of the registered weechat script uses these
bindings, so this is most likely much fewer users than those that have
`short_buffer_names` set.
|
|
|
|
| |
Fixes a bug introduced two commits ago, in commit fd4ddd9.
|
|
|
|
| |
Fixes #533
|
|
|
|
| |
Prints user friendly error messages if given invalid arguments.
|
|
|
|
|
|
| |
thread_command_callback is only bound to /thread and /reply, so it will
never be called with anything else, and there is no point in printing an
error message.
|
|
|
|
|
|
|
|
|
|
|
| |
The buffer given in the arguments refers to the buffer where the command
was run, while w.current_buffer refers to the buffer active in weechat.
Normally these are the same, but relay clients may have a different
buffer active than the one in weechat. Therefore, using w.current_buffer
could cause commands sent from those clients to operate on the wrong
buffer.
Fixes #547 and #615
|
|
|
|
|
|
|
|
|
| |
This rewrites modify_buffer_line and modify_print_time (now
modify_last_print_time to be more clear) to be much more readable.
modify_buffer_line had a bug where it moved past the first line, causing
the line_pointer to be lost so the first line couldn't be updated. This
is now fixed.
|
|
|
|
| |
Simplifies the usage so we don't have to look it up each time.
|
|
|
| |
Fixes #541
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Fix for #570, also incorporates #545
* Fixes from the review
* review fix #2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix typing and completion errors in core buffer
Typing more than 8 characters or hitting tab after a non-space character
in the core buffer causes errors because the buffer is a SlackTeam
object instead of a SlackChannel.
* Add `type` attribute to SlackTeam
* Add `members` property to SlackTeam and fix `type` value
* Return dict_keys for SlackTeam.members
|
|
|
|
| |
edition
|
|
|
|
| |
Closes #640
|
| |
|
|
|
|
| |
Similar to how Slack grays out muted channels in their own UI.
|
|
|
|
|
|
|
|
|
| |
Renames the config options for colors to start with color instead of end
with it, so they are grouped together.
If thread_suffix_color is set, the config will be migrated to the new
name. I didn't bother to migrate reaction_suffix_color since that added
just half an hour ago.
|
| |
|
| |
|
|
|
| |
Closes #546
|
| |
|
|
|
|
|
|
|
| |
If there's more work, schedule ourselves more often, if there's less,
back off a bit to lessen the CPU load.
Fixes: #523
|
|\
| |
| | |
Hide activity from muted channels
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The tag slack_muted_channel is set on all messages in channels which are
muted, and all messages in threads which belong to muted channels.
If you use a plugin for push notifications and don't want notifications
from muted channels, you can set it to ignore messages with this tag.
This would give you the same behavior as with the official client. Note
that this just applies to messages shown in the hotlist, i.e. highlights
(depending on your config) and thread messages, as messages hidden from
the hotlist are probably already ignored by the notification plugin.
|
| |
| |
| |
| |
| | |
Prints either "Muted channel #x" or "Unmuted channel #x" to the team
buffer.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows you to control which activity from muted channels you will
be notified for.
The default is set to personal_highlights, as I find that the most
useful. The official client doesn't send a notification for any
activity, but it shows highlights in the sidebar, so all_highlights is
probably the closest to that. However, since there isn't any difference
between highlights from muted and non-muted channels in wee-slack, I
think getting channel highlights from muted channels is a bit much.
|
| |
| |
| |
| |
| | |
If highlight_words is set to nothing, we should still call
set_highlights to remove any previous words.
|
| |
| |
| |
| |
| | |
Show channel names instead of id's, and show them in a more readable
format.
|
| |
| |
| |
| | |
Previously, it was set to the set of an empty string.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This sets the correct tags for messages in muted channels and prevents
muted channel from being added to the hotlist on start and when a
message arrives.
Threads from a muted channel are not muted. If you are part of a thread,
you probably want to be notified for messages in it, even though the
parent channel is muted. The official client shows messages in threads
from muted channels in "New threads" with a highlight in the sidebar.
Fixes #456
|
| |
| |
| |
| |
| | |
For muted channels, we need the tags for muted in addition to the tags
we normally want.
|
|/
|
|
|
| |
Don't mute topic messages, set the irc_topic and slack_topic tags and
let people filter them as wanted.
|
|\
| |
| | |
Subscribe threads
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
DMs with multiple persons should highlight just like DMs with one
person, instead of notifying without highlight like a channel.
This seems to have been the intention all along, but it didn't work
because the channel type was checked for mpdm, not mpim which is what
the type is set to (even though the class is called SlackMPDMChannel.
|
| |
|
|
|
|
|
|
| |
The join/leave prefix ends with a tab (which is used to separate nick
and message), but we also add a tab in buffer_prnt, so the join/leave
messages ended up with a tab in front of them.
|
|
|
|
| |
Fixes #538
|