| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
According to one comment it was necessary for them to include this
cookie as well.
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #869
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that conversations.mark works for all tokens, just using the
conversations API the same way as the old APIs works fine as far as I
can see.
Loosing unread_count_display by replacing mpim.open with
conversations.open and channels.info with conversations.info means that
mpims and channels will not be marked as unread when wee-slack loads if
background_load_all_history has been set to false anymore. As far as I
can see, the only way to check if they have unread messages is by
loading the history, so there is no way around this.
Fixes #792
|
| |
|
|
|
|
| |
How to install the dependencies for development and running tests is now
documented in docs/contributing.md, so change the development section to
just a debugging section.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Pipenv][0] makes it easier to maintain a consistent development
environment for projects using Python. You no longer need to manage
`pip` and `virtualenv` separately, nor deal with the drift and other
issues requirements.txt brings. It enables gaining insights into your
dependency graph, but most importantly - it enables deterministic
builds, which prevents the entire class of "it works on my machine"
problems.
[Pipenv][0] is similar to package managers from other ecosystems, such
as Node.js' `npm` or Rust's `cargo`. Additionally, [Pipenv][0] is an
[officially recommended package manager][1] by the Python project.
This patch brings [Pipenv][0] to the wee-slack project to simplify the
development and contribution experience. Additionally, this patch brings
basic contributing documentation to help onboarding.
[0]: https://github.com/pypa/pipenv
[1]: https://packaging.python.org/tutorials/managing-dependencies/#managing-dependencies
|
| |
|
|
|
|
| |
lnotify.py and all of the other local notification scripts for linux in
the repo have issues (see https://github.com/weechat/scripts/issues/433),
so recommend the trigger in the wiki instead, which seems to work great.
|
| | |
|
| |
|
|
| |
This was fixed in commit ad1a715.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
