| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Fixes #764
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Slack now disallows # in OAuth redirect uris, so we can't use it to
prevent GitHub Pages from seeing the OAuth code anymore.
Since the OAuth code is only valid once and expire after 10 minutes, I
don't think it's a problem that they are exposed to GitHub Pages, so
this is the new default so the same registration process can be kept.
However, for people worried about this, there's a new -nothirdparty
option to /slack register which can be used which doesn't expose the
code.
Fixes #766
|
| |
|
|
| |
As of today, these can no longer be created.
|
| | |
|
| |
|
|
| |
This was generated with https://github.com/ekalinin/github-markdown-toc
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #465
|
| | |
|
| |
|
| |
When installing on OpenBSD, you need to specify the Python 3 version (not Python 2)
|
| | |
|
| |
|
|
|
|
| |
It tooked me a while to figure out why weechat says that websocket module was not found in wee-slack plugin.
pip list sayed websocket-client was installed.
after installing pip3 and websocket-client with pip3, everything worked fine.
The current ubuntu 19.04 `python-websocket` package has always installed the python2.7 version.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is for channels which initially were public, but then are changed
to private. They look the same as groups (channels initially created as
private) in the official clients, but can only be used with the
conversations api. They are listed in the channels list of rtm.start
with is_private set to true.
There are some remaining issues, which are documented in the readme.
I'm not sure if we can support read sync and showing unread on load
without changes from Slack to the API.
Showing thread messages in the channel is possible to fix, but we would
have to send requests to load the thread history for all the messages in
the history that has replies.
Fixes most of #644
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The weechat package on FreeBSD now uses python 3. I removed six, because
we don't use it directly, it's only a dependency of websocket-client
(and will be installed as that when you install the websocket-client
package).
|
| |
|
|
|
|
| |
Add a command to create the necessary directories, replace wget with
curl (since curl, but not wget, is available by default on macOS), and
add a note that you can skip autoload if you want.
|
| | |
|
| | |
|
| |
|
| |
Add @user-groups with tab-completion. @user-groups will be unfurl into format <!subteam^{ID}|handle> message before sending message via linktext method.
|
| | |
|
| | |
|
| |
|
|
|
| |
Instead of duplicating much of the documentation for commands and
options, refer to the /set and /help commands in weechat.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 #541
|
| | |
|
| |
|
|
| |
edition
|
| |
|
|
|
| |
Show channel names instead of id's, and show them in a more readable
format.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* print `image_url` if it exists
* add test for image_url
* requirements.txt for pytest
* fix requirements.txt
* text before image_url
* this isn’t required
* README readability for development section
thanks @trygveaa
* README reorder for this development section
|
| |
|
|
| |
Signed-off-by: Victor "multun" Collod <victor.collod@epita.fr>
|
| | |
|
| |
|
|
|
|
| |
some distributions do not distribute weechat with support for all
plugins by default, but use separate packages to provide support
for different scripting languages. users should be made aware of that
|
| | |
|
| | |
|
| |
|
|
| |
The refactor is a long time ago now, and caching has been removed.
|
| |
|
|
|
| |
In #504 I proposed to add some help to future debuggers. This is a split PR from that.
cc: @trygveaa
|
| |\
| |
| | |
Restore OAuth support
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Add completion of custom emojis
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
- Fix incorrect parameter name for MPDMs: `users` instead of `user_ids`
- Accept comma-separated nicks instead of space-separated to match
weechat's `/query` syntax
- Check user IDs instead of usernames to find channels
- Use `SLACK_API_TRANSLATOR` instead of hard coding API methods
- Update documentation
|
| | |
| |
| |
| |
| | |
`command_talk` can now accept multiple arguments, which allows commands
like `/query user1 user2` to open a MPDM with user1 and user2.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows you to send messages starting with / or messages like s/a/b/
and +:test: as normal text messages instead of performing the action
they normally would. This is done by prefixing the message with a slash
(/) or a space ( ), and then the prefix character is removed from the
resulting message.
Allowing / as a prefix, so you can write e.g. //slack is the normal way
to send messages starting with / in weechat. This will work for all
messages starting with a slash, but won't work for e.g. /+:test:, as
that is interpreted as a command. Using space as a prefix is the way
Slack does it. This will work for all messages.
|
| | | |
|
