search

yuya373 / emacs-slack

slack client for emacs
1.11k stars 117 forks source link

Responding to a thread deletes most keybindings #497

Closed grimnebulin closed 4 years ago

grimnebulin commented 4 years ago

Describe the bug When I reply to a Slack thread, nearly all key bindings are deleted.

To Reproduce Steps to reproduce the behavior:

  1. Go to a Slack thread buffer.
  2. Type any message and press Return.
  3. Reply "y" or "n" to the prompt "Also send to $CHANNEL ? (y or n) ", or even quit with control-G (it doesn't matter which). The message "Wrong type argument, stringp" appears in the minibuffer.
  4. Type almost any key combination. The message "$KEY is undefined" appears in the minibuffer. This happens with all ordinary text keys, and C-p, C-n, C-a, C-x, M-x, etc. One binding I have that still works somehow is super-tab. I can also use the menu bar normally, but the usual keybindings are still gone if I switch to another buffer. My only option is to quit and restart Emacs (or kill it, if I had any modified files, since I can't respond "yes" to the "really quit" prompt).

Expected behavior Thread responses are normally returned to Slack.

Environment:

Additional context Add any other context about the problem here.

grimnebulin commented 4 years ago

At first I saw the mass key unbinding occur only during posts to Slack message buffers, but I just saw it happen when trying to delete some files in Dired, so it must not be a bug particular to emacs-slack.