aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove /leave commandTrygve Aaberge2019-01-261-2/+0
| | | | | /leave is by default aliased to /part. We don't have to specify this in wee-slack.
* Add /slack help commandTrygve Aaberge2019-01-261-4/+26
| | | | Fixes #363
* Simplify setting topic from topic or purposeTrygve Aaberge2019-01-261-3/+1
|
* Resolve references in topicTomas Janousek2019-01-261-1/+2
| | | | | | | | | | 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
* Fix 'wrong arguments for function "buffer_set"'Tomas Janousek2019-01-261-6/+5
| | | | | | | | | | 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...
* Include threads when marking latest message as read (#653)Eric Wang2019-01-261-1/+1
|
* Add tests for preserving formatting in code blocksDavid Vo2019-01-251-0/+13
|
* Add tests for no formatting casesDavid Vo2019-01-251-0/+14
|
* Avoid formatting matching into code spans/blocksDavid Vo2019-01-251-2/+2
| | | | | | | | | 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
* Preserve formatting charactersDavid Vo2019-01-251-2/+2
| | | | | | | This allows copy-pasting messages preserving their formatting, and will help avoid characters going missing within backticks. Ref: #566
* Fix bold/italics matching across newlinesDavid Vo2019-01-251-2/+2
|
* Add show_buflist_presence config option (#558)David Golden2019-01-251-4/+6
| | | | | | | | | | 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.
* Add instructions on how to request slack app installationTrygve Aaberge2018-11-161-2/+2
| | | | | This is for users with a team that has restricted which apps that can be installed in Slack.
* Release v2.2.0v2.2.0Trygve Aaberge2018-11-122-1/+3
|
* Add a changelogTrygve Aaberge2018-11-121-0/+29
|
* Add an option to set color of (edited) suffix (#660)er-12018-11-121-1/+5
| | | | | 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.
* Add apostrophe to the regex with a corresponding testPásztor János2018-11-122-1/+9
| | | | * fixes #618
* Clarify usage of mouse and cursor modeTrygve Aaberge2018-11-111-1/+3
|
* Bind cursor/mouse commands to all python buffersTrygve Aaberge2018-11-112-13/+16
| | | | | | | | | | | | | | 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.
* Allow more than one word in /reply messageTrygve Aaberge2018-11-071-3/+2
| | | | Fixes a bug introduced two commits ago, in commit fd4ddd9.
* Support using /thread for already opened threadsTrygve Aaberge2018-11-051-2/+3
| | | | Fixes #533
* Add error handling to /thread and /replyTrygve Aaberge2018-11-051-26/+42
| | | | Prints user friendly error messages if given invalid arguments.
* Remove unnecessary print and returnsTrygve Aaberge2018-11-051-3/+1
| | | | | | 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.
* Use buffer from arguments instead of w.current_bufferTrygve Aaberge2018-11-041-10/+4
| | | | | | | | | | | 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
* Fix bug preventing first line in buffer to be changedTrygve Aaberge2018-11-041-69/+51
| | | | | | | | | 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.
* Store hdata structure in a classTrygve Aaberge2018-11-042-24/+29
| | | | Simplifies the usage so we don't have to look it up each time.
* Add linkarchive slack command to create a link to a given message (#650)Immae2018-11-042-3/+31
| | | Fixes #541
* Add open thread command with cursorIsmaël Bouya2018-11-042-2/+12
|
* Fix status callIsmaël Bouya2018-11-031-1/+1
|
* Match nicks with parenthesis and/or unicode (#649)pasja2018-11-032-1/+38
| | | | | | | | * Fix for #570, also incorporates #545 * Fixes from the review * review fix #2
* Fix typing and completion errors in core buffer (#638)Eric Wang2018-10-311-0/+5
| | | | | | | | | | | | | | * 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
* Allow selection of a message using mouse or cursor in /reply / reaction / ↵Ismaël Bouya2018-10-292-55/+145
| | | | edition
* Fix loading history with deleted attachmentJosip Janzic2018-10-221-2/+10
| | | | Closes #640
* Add config for color for muted channels in buflistTrygve Aaberge2018-10-211-1/+5
|
* Gray out muted channels in buflistEric Wang2018-10-211-1/+2
| | | | Similar to how Slack grays out muted channels in their own UI.
* Group color configs togetherTrygve Aaberge2018-10-211-14/+20
| | | | | | | | | 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.
* reactions: Add a config parameter to change color of suffixed reacsPaul B2018-10-211-2/+8
|
* Allow reactions and edition of messages in threadsIsmaël Bouya2018-10-211-50/+70
|
* Add option to show thread messages in parent channel (#616)Josip Janzic2018-10-211-32/+40
| | | Closes #546
* Fix test_everything.py failing by handling events in orderEric Wang2018-10-201-1/+1
|
* Use an adaptive eventrouter timerTollef Fog Heen2018-09-301-1/+12
| | | | | | | If there's more work, schedule ourselves more often, if there's less, back off a bit to lessen the CPU load. Fixes: #523
* Merge pull request #457 from trygveaa/hide-activity-from-muted-channelsTrygve Aaberge2018-09-132-41/+84
|\ | | | | Hide activity from muted channels
| * Set tag slack_muted_channel on muted channel messagesTrygve Aaberge2018-09-041-7/+13
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * Print result from /slack mute commandTrygve Aaberge2018-09-041-8/+9
| | | | | | | | | | Prints either "Muted channel #x" or "Unmuted channel #x" to the team buffer.
| * Add a 'muted_channels_activity' config optionTrygve Aaberge2018-09-041-4/+21
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * Always call set_highlights in set_highlight_wordsTrygve Aaberge2018-09-041-4/+3
| | | | | | | | | | If highlight_words is set to nothing, we should still call set_highlights to remove any previous words.
| * Implement showmuted command properlyTrygve Aaberge2018-09-042-2/+10
| | | | | | | | | | Show channel names instead of id's, and show them in a more readable format.
| * Set muted channels to empty set if no muted channelsTrygve Aaberge2018-09-021-1/+1
| | | | | | | | Previously, it was set to the set of an empty string.
| * Add mute command to readmeTrygve Aaberge2018-09-021-0/+5
| |
| * Hide activity from muted channelsTrygve Aaberge2018-09-021-8/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
generated by cgit (git 2.34.1) at 2024-11-14 23:49:01 +0000