| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Just handle <>& for now.
Fixes: #186
|
|
|
|
|
|
|
| |
Make sure we have something that's a well-formed nick before we go
ahead and do silly things.
Fixes: #237
|
|
|
|
|
|
|
| |
Make it clearer where the messages are coming from when printing to
main buffer.
Fixes: #240
|
|
|
|
|
|
|
| |
If we get a ValueError when loading the json, continue, instead of
making the user unhappy.
Closes: #248
|
|\
| |
| | |
Support passing additional tags to enable notification_center.py
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
More updates to get highlights working
add that gitignore
Hopefully handles all situations where a message would have highlights
Removed additional settings; was not needed
Resolve code review items
- fix an erroneously removed condition for unsetting a config option
- remove notify_highlight tag; is redundant
- thanks @tfheen!
Removes project-local .gitignore
Undo an uncomment
Reverting back to including the previously commented line
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we're in a non-slack buffer, just ignore /part, /topic, /me, etc.
This is somewhat based off #212, so thanks to @bendem for pointing
this out.
Fixes: #137
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Open new queries
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit 46384b6782f0b73318f764bf02f24cdbcdd059c9 introduced storing the
reaction users as a set in the message_json representation. However sets
are not JSON serializable. Instead uses a list and checks for membership
prior to manipulation.
Fixes the traceback:
Traceback (most recent call last):
File "wee_slack.py", line 2105, in cache_write_cb
cache_file.write("{}\n".format(json.dumps(message.message_json)))
File "/usr/lib/python2.7/json/__init__.py", line 244, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python2.7/json/encoder.py", line 207, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python2.7/json/encoder.py", line 270, in iterencode
return _iterencode(o, 0)
File "/usr/lib/python2.7/json/encoder.py", line 184, in default
raise TypeError(repr(o) + " is not JSON serializable")
TypeError: set([u'Uxxxxxxxx']) is not JSON serializable
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Prevents the traceback:
Traceback (most recent call last):
File "wee_slack.py", line 1361, in slack_websocket_cb
proc[function_name](message_json)
File "wee_slack.py", line 1417, in process_presence_change
server.users.find(identifier).set_active()
File "wee_slack.py", line 860, in set_active
w.nicklist_nick_set(self.server.buffer, self.nicklist_pointer,
"visible", "1")
AttributeError: 'User' object has no attribute 'nicklist_pointer'
|
|\ \ \
| | | |
| | | | |
Added process_group_join, process_group_leave and process_group_topic
|
| | |/
| |/|
| | |
| | | |
that pass to their channel equivalents
|
|\ \ \
| | | |
| | | | |
Fix error when sending messages to server query
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Encode topics in utf-8, not ascii
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | | |
Set buffer localvars for channel and server
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If server.alias is set, use that for the server localvar. Otherwise, use
server.team.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of setting the buffer localvar server to the domain
($team.slack.com), set it to only the team name. This makes it more like
what the irc plugin sets, which is the server name.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These are the same as what the irc plugin sets, and can be used in the
logger masks among other things.
This fixes #188.
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Show nicks for each reaction
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
A user can only add a specific reaction once per message, so we can
store the users in a set instead of a list.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some may think it takes up too much space to show all the nicks for all
of the reactions. This adds a config option `show_reaction_nicks` for
configuring that. If set to false, it only shows the number of persons
that added each reaction, like before. If set to true, it shows the new
version with each nick. It defaults to false, to not change the
behavior.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since we now store and show the users for each reaction, we don't need
to store count as well. Each user can only react with a specific
reaction to a specific message once, so to get the count we can check
the length of the list of users.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of only showing the number of persons that added a reaction,
show the nicks that added them. The nicks are shown comma separated in
parenthesis after each reaction.
This adds an item named users to the reaction dict of a message, which
contains a list of all of the user ids. Since the code assumes that item
exists, which makes it incompatible with the old structure, the
CACHE_VERSION is increased by one.
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Update README to mention location of the API token required
|
|/ / / / |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Add info on manually loading wee_slack.py when weechat is already running
|
| | |_|/
| |/| |
| | | |
| | | | |
Also remove trailing whitespace on a few lines.
|
|\ \ \ \
| |_|/ /
|/| | | |
Check that a parameter is passed to /join
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Print out the name of the user when enabling/disabling integrations
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previous:
pagerduty :] | disabled an integration in this channel: https://…
Now:
pagerduty :] | foo disabled an integration in this channel: https://…
|
|\ \ \
| | | |
| | | | |
Prefix the server buffer name with slack instead of suffixing it
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of using the format `$team.slack.com` for the server buffer
name, change it to `slack.$team`. This makes it easier to see that the
buffer is a slack buffer.
Additionally, it makes it possible to set options where you specify the
start of the buffer name for all of the slack buffers. For example, it
makes it possible to set the option `logger.mask.python.slack` for
setting a logger file mask for all of the slack buffers.
|
|\ \ \
| | | |
| | | | |
Handle bots using the RTM API too
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
Some bots, such as lita (https://github.com/litaio/lita-slack) is
using the RTM API. Those show up as regular users, but have is_bot
set on their user object. Pick up on that when formatting lines.
Thanks to Whoop on IRC (@adamgibbins) for pointing this out.
|
|\ \ \
| | | |
| | | | |
Coloring 'prefix_same_nick' prefix the same as the preceding username…
|
| | | |
| | | |
| | | |
| | | | |
replacing if 'colorize_nicks' is turned on.
|
|\ \ \ \
| |_|_|/
|/| | | |
Added option to colorize messages the same color as the sending nick …
|