search

yuya373 / emacs-slack

slack client for emacs
1.11k stars 117 forks source link

error when trying to kill Slack buffers #567

Open benthamite opened 2 years ago

benthamite commented 2 years ago

Describe the bug I sometimes (not always) get the following error when trying to kill an emacs-slack buffer:

(wrong-type-argument hash-table-p nil)

To Reproduce Steps to reproduce the behavior:

  1. Go to an emacs-slack buffer.
  2. Invoke kill-this-buffer.
  3. See error

Backtrace

Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
  remhash("D038XBDPGHW" nil)
  #f(compiled-function () #<bytecode -0x4df68c110b9f7ea>)()
  kill-this-buffer()
  funcall-interactively(kill-this-buffer)
  command-execute(kill-this-buffer record)
  execute-extended-command(nil "kill-this-buffer" "kill ")
  funcall-interactively(execute-extended-command nil "kill-this-buffer" "kill ")
  command-execute(execute-extended-command)

Expected behavior The buffer is killed.

Environment:

jeremygooch commented 1 year ago

I'm running into the same issue with kill-buffer, kill-this-buffer etc. Backtrace

Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
  remhash("C01605QLNKD" nil)
  #f(compiled-function () #<bytecode -0x11f5668a71c2d4d>)()
  kill-buffer(#<buffer *Slack - TeamName : channel-name>)
  kill-current-buffer()
  funcall-interactively(kill-current-buffer)
  call-interactively(kill-current-buffer nil nil)
  command-execute(kill-current-buffer)

Environment