New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respect short_name changes #563

Open
robertmeta opened this Issue Apr 16, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@robertmeta
Copy link

robertmeta commented Apr 16, 2018

If you like to change short_name on channels, either directly using the /buffer set short_name dogfood/general or via /buffer_autoset -- either way, wee-slack doesn't respect the change made.

I think that when updating the typing notification it doesn't respect the new short name so instead of going ">dogfood/general" then "dogfood/general" it goes to its internal name ">general" "#general".

I will look at submitting a patch to fix this behavior.

@auscompgeek

This comment has been minimized.

Copy link
Contributor

auscompgeek commented Apr 17, 2018

One workaround could be to disable plugins.var.python.slack.channel_name_typing_indicator.

@robertmeta

This comment has been minimized.

Copy link

robertmeta commented Apr 18, 2018

@auscompgeek that work around does work -- hence confirming the source of the bug.

@skrzyp

This comment has been minimized.

Copy link

skrzyp commented Dec 13, 2018

I can confirm - changed short_name is restored on some other events other than typing notification too.

I'm using short_names on buflist to maintain its small size, some abbrevs are also very handy with go.py plugin to jump between bufers with few taps (I have about 300+ buffers)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment