Skip to content
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

Attempt to delete minibuffer or sole ordinary window (take 2) #2487

Closed
3 tasks done
tpapp opened this issue May 8, 2023 · 0 comments
Closed
3 tasks done

Attempt to delete minibuffer or sole ordinary window (take 2) #2487

tpapp opened this issue May 8, 2023 · 0 comments
Labels
bug mu4e specific for mu4e

Comments

@tpapp
Copy link

tpapp commented May 8, 2023

Describe the bug

This looks like #789 resurfacing. Stacktrace:

Debugger entered--Lisp error: (error "Attempt to delete minibuffer or sole ordinary wind...")
  error("Attempt to delete minibuffer or sole ordinary wind...")
  delete-window()
  kill-buffer-and-window()
  mu4e-view-quit()
  funcall-interactively(mu4e-view-quit)
  command-execute(mu4e-view-quit)

The issue is otherwise innocuous, no buffers corrupted, etc. Just quitting the stacktrace is enough to proceed.

How to Reproduce

I find it very hard to reproduce. It occurs more or less randomly, very occasionally, when pressing q in a view buffer.

Environment

Emacs 28.2 on Ubuntu 23.04, mu4e release 1.10.3, git tag 80a2d4c.

Checklist

  • you are running either an 1.8.x/1.10.x release or master (otherwise please upgrade)
  • you can reproduce the problem without 3rd party extensions (including Doom/Evil, various extensions etc.)
  • you have read all of the above
@tpapp tpapp added bug mu4e specific for mu4e new labels May 8, 2023
@djcb djcb closed this as completed in 0ed7dc2 May 10, 2023
@djcb djcb removed the new label May 10, 2023
djcb added a commit that referenced this issue Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mu4e specific for mu4e
Projects
None yet
Development

No branches or pull requests

2 participants