| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Fixes #597
|
| | |
|
| |
|
|
|
| |
Instead of duplicating much of the documentation for commands and
options, refer to the /set and /help commands in weechat.
|
| | |
|
| |
|
|
|
| |
This includes these commands in the help command. It also allows these
commands to be used with the /slack prefix.
|
| |
|
|
|
| |
Don't send in the command name as part of args. This removes the need
for removing the name from args.
|
| |
|
|
|
|
|
|
|
| |
We should use hook_command instead of hook_command_run when we add new
custom commands because this will include completion and help for the
command.
When we use this, the command name won't be included in the arguments,
which is why the usage of args in the functions has changed.
|
| | |
|
| |
|
|
|
|
| |
linkarchive now supports being run without arguments, and if so it will
output a link to either the team or the channel, depending on where it's
run. openweb has been removed.
|
| |
|
|
|
|
| |
When the command starts with command_, it will be listed in the help and
callable with /slack. This is just a callback function, so it should not
be callable directly by the user.
|
| |
|
|
|
| |
This is a command meant for debugging and shouldn't be normally
available and listed in the help.
|
| |
|
|
|
| |
/leave is by default aliased to /part. We don't have to specify this in
wee-slack.
|
| |
|
|
| |
Fixes #363
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
When a user is mentioned in a topic, it's only resolved in the
15:47:34 <--> @someone set the channel topic: blah blah @mention blah
message. The buffer title, however, reads:
blah blah <@JHDJFHKDW> blah
|
| |
|
|
|
|
|
|
|
|
| |
When a "channel_joined" event is received (e.g. when joining channels
from the web client, or when someone else makes you join the channel),
update_from_message_json sets self.topic to the dict, but render_topic
expects it to be a string. This is an inconsistency introduced by
e64293b41573b5caad2ebf343d9a4397cef22a67. Let's keep the dict.
Actually, using update_from_message_json at all seems like a bad idea...
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This won't stop formatting within backticks, but will avoid applying
bold formatting to a message like this:
* Run this find command: `find . -name '*.exe'`
Ref: #566
|
| |
|
|
|
|
|
| |
This allows copy-pasting messages preserving their formatting,
and will help avoid characters going missing within backticks.
Ref: #566
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
