aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Improve handling of thread/subscription errors.Aidan Epstein2020-03-261-5/+15
|
* Fix python 2 incompatibility.Aidan Epstein2020-03-261-2/+4
|
* Add error reporting for subscriptions.Aidan Epstein2020-03-251-0/+1
|
* Refactor command_(un)subscribe.Aidan Epstein2020-03-251-26/+16
|
* Add new notify_thread case for subscriptions.Aidan Epstein2020-03-251-0/+2
|
* Fix typo in subprocess_thread_message, and reorder messages.Aidan Epstein2020-03-251-2/+2
|
* Check history_message in SlackThreadChannel's buffer_prnt.Aidan Epstein2020-03-251-4/+4
|
* Refactor mark_read into SlackChannelCommon.Aidan Epstein2020-03-251-28/+15
|
* Only say subscribed if subscribed, instead of True/FalseAidan Epstein2020-03-251-2/+2
|
* Use actual last_read times in threads, instead of that of the parent channel.Aidan Epstein2020-03-211-5/+17
|
* Fix messages not updating when subscription status changes.Aidan Epstein2020-03-211-2/+8
|
* Add slack subscribe and unsubscribe commands.Aidan Epstein2020-03-211-4/+38
|
* Update thread last_read mark.Aidan Epstein2020-03-211-6/+13
|
* Beginning of work on subscribing to threads.Aidan Epstein2020-03-211-2/+42
| | | | | It currently seems to work on threads that are automatically subscribed (such as by saying something in them).
* Update docs for how to connect to a teamTrygve Aaberge2020-03-211-11/+16
|
* Create a helper function for printing part of a tokenTrygve Aaberge2020-03-211-16/+18
| | | | | | | This also changes the text to include the end of the token, because tokens for the same team often start with the same, so the warnings I added in the two previous commits would show the same text for the two tokens.
* Print warning when trying to add two tokens for the same team and userTrygve Aaberge2020-03-211-3/+14
|
* Print error when trying to add the same team for two different usersTrygve Aaberge2020-03-211-12/+22
| | | | | | This is not currently supported because the two teams would have conflicting buffer names. Before this patch, it would print out a bunch of error messages about conflicting buffer names.
* Use existing team_hash when creating SlackTeamTrygve Aaberge2020-03-211-2/+3
| | | | | | | | | The team_hash is generated in handle_rtmstart, and it was generated again when instantiating SlackTeam. However, the parameters the two used were different, so they ended up with different hashes, and the check for existing teams in rtmstart would always be false. Fixes #734
* Allow using /slack register with an existing tokenTrygve Aaberge2020-03-212-10/+26
|
* Set highlight_words for new channels and thread channelsTrygve Aaberge2020-03-201-1/+12
| | | | Fixes #736
* Fix broken tests with Python 2 after commit aa63263Trygve Aaberge2020-03-191-0/+1
| | | | | We only use unicode strings on Python 2, so set str = unicode, so we can use the str type in the rest of the code.
* Show the parent message as the first message in a threadTrygve Aaberge2020-03-191-1/+1
| | | | | | | The message is also shown in the title bar, but that is usually limited to one line, so it may not show the whole message. Fixes #705
* Preserve thread channels across reconnections and /rehistoryTrygve Aaberge2020-03-191-21/+37
| | | | | | | | | | | | | | Previously, the references to the thread channels and the hashes of the messages would be lost when the channel reloaded its history. That meant that when new messages arrived in the thread, they would not be printed in the thread channel. This moves the references to the thread channels from each parent message to the channel, and changes the values in hashed_messages to be just the timestamp instead of the message, so we don't have to clear it when we reload the history. Relates to #714
* Fix error when trying to compare SlackTS with NoneTrygve Aaberge2020-03-191-1/+1
|
* Don't remove logger_backlog tag when no_log is setTrygve Aaberge2020-03-191-1/+1
| | | | | When log[0-9] tags were removed for no_log lines in commit 3f4e64c, the logger_backlog tag was inadvertently also removed.
* Reply to parent message if trying to reply to thread messageTrygve Aaberge2020-03-182-1/+29
| | | | | | | | | | | | | | | Opening a thread on a thread message is not possible, so the logical thing to do if a user tries to reply to a thread message is to put the message in the same thread as the message that is replied to. Slack currently has a bug which causes thread messages to be converted to normal messages if you try to reply to them (that is, send a message with thread_ts set to the ts of the thread message), but the message you reply with will end up in the original thread. I filed an issue and they confirmed that it is a bug, and that you should not send messages with thread_ts set to the ts of a thread message. Fixes #751
* Send parent channel as reference to conversations.repliesTrygve Aaberge2020-03-151-1/+2
| | | | | | | This was inadvertently changed to send the thread channel as reference in commit 6238505. Fixes #757
* Improve help text for /reply and update Commands.mdTrygve Aaberge2020-03-032-7/+17
|
* Make /slack help output equal to weechats /help outputTrygve Aaberge2020-03-031-10/+19
|
* Strip whitespace from help descriptions for commandsTrygve Aaberge2020-03-021-1/+1
| | | | | | | | | command_reply now has a blank line after the first line, which means we sent in a description with a blank first. Weechat automatically adds a blank line before the description, so it showed two blank lines for /help reply. We want the blank line in the docstring for /slack help reply, so strip it in the description instead of removing it from the docstring.
* Handle reply for broadcast messages sent from wee-slackTrygve Aaberge2020-03-021-1/+4
|
* Add ability to broadcast a thread message to the rest of the channel. (#753)Trygve Aaberge2020-03-021-12/+35
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add ability to broadcast a thread message to the rest of the channel. This adds an optional -broadcast parameter to /reply and a /slack broadcast command. Also update completions for /reply. * Change reply argument from -broadcast to -alsochannel, remove command_broadcast, and change reply to work without the id when in a thread buffer. * Clarify documentation of /reply command, and refactor msg logic. * Fix /help reply display.
| * Fix /help reply display.Aidan Epstein2020-03-011-0/+2
| |
| * Clarify documentation of /reply command, and refactor msg logic.Aidan Epstein2020-03-011-12/+16
| |
| * Change reply argument from -broadcast to -alsochannel, removeAidan Epstein2020-03-011-25/+21
| | | | | | | | | | command_broadcast, and change reply to work without the id when in a thread buffer.
| * Add ability to broadcast a thread message to the rest of the channel.Aidan Epstein2020-02-291-5/+26
| | | | | | | | | | | | | | This adds an optional -broadcast parameter to /reply and a /slack broadcast command. Also update completions for /reply.
* | Differentiate between manual and auto away in away bar itemTrygve Aaberge2020-03-021-1/+6
| |
* | Handle manual presence change properlyTrygve Aaberge2020-03-021-2/+5
| | | | | | | | | | | | | | | | The manual_presence_change event is just for your own user and doesn't include any user ids. This adds a field on the team with your manual presence so we can show if the user is automatically away or manually away.
* | Ensure we are subscribed to our own presenceTrygve Aaberge2020-03-021-1/+3
| | | | | | | | | | | | Slack doesn't send the presence_change event for our own user when it updates the auto presence unless we subscribe to it. The manual_presence_change however is sent either way.
* | Set presence to active when switching buffer or calling /slack backTrygve Aaberge2020-03-021-6/+12
| |
* | Show away in away bar item when presence is awayTrygve Aaberge2020-03-021-0/+18
|/ | | | | | | | | | This shows it in the standard away bar item, and also adds a specific one for wee-slack. The reason for including the specific one is that if multiple scripts in the same plugin define the same bar item, only one of them will work[0]. So people that have another python script which also defines the away bar item can use the slack_away bar item instead. [0]: https://github.com/weechat/weechat/issues/1348
* Set re.UNICODE correctly in linkify_textTrygve Aaberge2020-02-281-1/+1
| | | | | | | This caused nicks with unicode characters to not be linkified on Python 2. The error was introduced in commit f5cfdab. Fixes #747
* Don't send history_message to SlackThreadChannel.buffer_prntTrygve Aaberge2020-02-271-1/+1
| | | | | | | It isn't currently being used. This fixes an error I introduced when I removed **kwargs from this method in commit 6238505.
* Update docs/Options.md after commit f084200Trygve Aaberge2020-02-231-1/+1
|
* Improve documentation for removing a teamTrygve Aaberge2020-02-231-0/+5
|
* Print error if trying to use /thread in team bufferTrygve Aaberge2020-02-231-0/+4
| | | | Fixes #737
* (Un)merge team buffers when irc.look.server_buffer is changedTrygve Aaberge2020-02-231-2/+15
| | | | Fixes #712
* Don't switch to the debug buffer when config is changedTrygve Aaberge2020-02-231-3/+1
|
* Move inviter text to before blocks and unfurl_refsTrygve Aaberge2020-02-231-6/+5
| | | | | Blocks should come after the inviter text, and by moving it before unfurl_refs we don't have to call that twice.
generated by cgit (git 2.34.1) at 2024-11-10 09:42:02 +0000