> Would you be okay with a user-error message like "Cannot call org-capture from the minibuffer"?
Oh, if I'm going to get an error message I don't care which one it is. Might as well leave things as they are currently. What I was hoping is that you would be able to fix org-capture so that you can also call it from the minibuffer, if enable-recursive-minibuffers is set to t. I like to think that I can call org-capture no matter what I am doing, take a quick note or reminder, and go back to whatever it was. It is almost like that: I can't interrupt myself if the minibuffer is open, but I can in all other cases. This is not a big deal, so if it's not easy to fix, just leave it as is. But if it happens to be easy to do I think it would be worthwhile, so that org-capture can live up to its reputation of being able to quickly capture something /no matter what you were doing at the time/! -- Omar On Sat, Dec 12, 2020 at 12:32 PM Bastien <b...@gnu.org> wrote: > Hi Omar, > > thanks for reporting this. > > Omar Antolín Camarena <o...@matem.unam.mx> writes: > > > I have enable-recursive-minibuffers set to t, and just noticed that > > org-capture does not work if called from the minibuffer. > > > > Steps to reproduce: > > > > 1. run emacs -Q > > 2. evaluate (setq enable-recursive-minibuffers t) in the scratch buffer > > 3. Open the minibuffer, say by using C-x C-f > > 4. While still in find-file, run M-x org-capture and pick a template (t > for Task seems to be offered by default). > > > > You should get an error message saying "Can't expand minibuffer to > > full frame". > > Would you be okay with a user-error message like > > "Cannot call org-capture from the minibuffer" > > ? > > -- > Bastien > -- Omar Antolín Camarena
