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

[mu4e bug] The new mu4e-compose-new function does not return buffer name #2653

Closed
armindarvish opened this issue Mar 3, 2024 · 0 comments
Closed
Labels
mu4e specific for mu4e rfe

Comments

@armindarvish
Copy link

Describe the bug
mu4e-compose-new used to return the name of the new buffer created. This was useful because then one could automate things when composing. But with the new approach using compose mail, the return value is some meaningless value that seems to do with minibuffer! It would be nice to restore the previous behavior to return the buffer that is created.

How to Reproduce
Run (setq testvar (mu4e-compose-new)) and see the return value for testvar.

Environment
MacOS, GNU Emacs 30.0.50, mu/mu4e 1.12.0

Please make sure you all items in the checklist are set/met before filing the ticket. Thank you!

@armindarvish armindarvish added bug mu4e specific for mu4e new labels Mar 3, 2024
@djcb djcb added rfe and removed bug new labels Mar 3, 2024
@djcb djcb closed this as completed in e28c248 Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mu4e specific for mu4e rfe
Projects
None yet
Development

No branches or pull requests

2 participants