this post was submitted on 31 Oct 2023
1 points (100.0% liked)
Emacs
314 readers
2 users here now
A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!
Get Emacs
Rules
- Posts should be emacs related
- Be kind please
- Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.
Emacs Resources
Emacs Tutorials
- Beginner’s Guide to Emacs
- Absolute Beginner's Guide to Emacs
- How to Learn Emacs: A Hand-drawn One-pager for Beginners
Useful Emacs configuration files and distributions
Quick pain-saver tip
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
We're expecting RET to perform
minibuffer-exit
. That's the default keybinding fromminibuffer-mode-map
. Perhaps another keybinding (from another minor-mode keymap, say) is overriding the minibuffer's RET binding.Hmmm, this sounds familiar. I had this problem last year.
Do you have Paredit mode enabled in the minibuffer? (You might look at the value of
eval-expression-minibuffer-setup-hook
.)The
paredit-mode-map
has theparedit-RET
command bound to RET instead. This command usually puts a new line in place.It was exactly this. I had a setup hook that was messing it up. Disabling it fixed the issue. Thanks for this post! This was the hook:
I think it must have been that
(enable-paredit-mode)
overrode the RET binding.