aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Include footer in attachmentsTrygve Aaberge2020-04-052-0/+49
|
* Don't add fallback if link exists in text_beforeTrygve Aaberge2020-04-052-3/+34
| | | | | | | | We should only use the fallback if we don't get any information out of the attachment. For links that exists in text_before, we have gotten the information from the attachment, but choose not to display it so we don't end up with duplicate links. Therefore, we shouldn't use the fallback in this case.
* Match attachment links against escaped text as wellTrygve Aaberge2020-04-052-3/+19
| | | | | The urls in the attachment fields can apparently come both escaped and unescaped.
* Don't print image_url if it's equal to from_urlTrygve Aaberge2020-04-052-1/+18
|
* Ignore ref fallback if it's equal to the refTrygve Aaberge2020-04-052-1/+6
| | | | | Prevents showing "http://some.url (http://some.url)" if the url has a fallback which is equal to the url.
* Add tests for unfurl_auto_link_display with mailtoTrygve Aaberge2020-04-051-0/+15
|
* Merge pull request #758 from aereaux/subscribe_threadsTrygve Aaberge2020-04-051-68/+172
|\ | | | | Allow subscribing to threads
| * Remove message_replied handlerTrygve Aaberge2020-04-051-16/+1
| | | | | | | | | | Now that we notify for subscribed threads in the thread_message handler, we don't need this anymore.
| * Use slack_api_translator from the team everywhereTrygve Aaberge2020-04-051-26/+26
| |
| * Stop calling thread.mark if not supportedTrygve Aaberge2020-04-051-5/+11
| | | | | | | | | | | | | | | | | | The subscriptions.thread.mark method is only supported for the tokens the web client use, not by oauth or legacy tokens, so if we get an error that it's not supported for the current token type, remove it from slack_api_translator so we don't keep calling it. slack_api_translator is moved to a team attribute because different teams may use different token types.
| * Fix arguments for print_errorTrygve Aaberge2020-04-051-3/+3
| |
| * Remove thread_messages_in_channel mark_read-ing.Aidan Epstein2020-03-301-6/+0
| | | | | | | | | | This doesn't work because thread_channels only includes threads that have buffers open.
| * Fix a couple bugs in mark_read.Aidan Epstein2020-03-301-4/+7
| |
| * Mark all threads as read when thread_messages_in_channel is set.Aidan Epstein2020-03-271-2/+7
| |
| * Process thread_marked events, to mark threads as read when the API tells us to.Aidan Epstein2020-03-271-0/+12
| |
| * Store thread last_reads in parent_message, so that they survive buffer closes.Aidan Epstein2020-03-271-2/+10
| |
| * 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).
* | Release v2.5.0v2.5.0Trygve Aaberge2020-03-252-1/+34
| |
* | Add table of contents to the readmeTrygve Aaberge2020-03-241-0/+26
| | | | | | | | This was generated with https://github.com/ekalinin/github-markdown-toc
* | Add FAQs for buffer order and notificationsTrygve Aaberge2020-03-241-0/+23
|/
* 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.
generated by cgit (git 2.34.1) at 2024-11-16 02:30:45 +0000