From: Jean Louis <firstname.lastname@example.org>
To: "Omar Antolín Camarena" <email@example.com>
Cc: Bastien <firstname.lastname@example.org>, email@example.com
Subject: Re: Bug: org-capture does not work if called from minibuffer [9.4 (9.4-55-g706ba9-elpaplus @ /home/omarantolin/.emacs.d/elpa/org-plus-contrib-20201207/)]
Date: Mon, 14 Dec 2020 22:14:28 +0300 [thread overview]
Message-ID: <X9e5lAyqYQ8cJmON@protected.rcdrun.com> (raw)
* Omar Antolín Camarena <firstname.lastname@example.org> [2020-12-14 22:03]:
> > 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.
On my side that works. When it is enabled I get screen for Org capture
and I can do it.
> 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.
One solution you can use is that you open separate Emacs instance or
Emacs as server that loads org-capture and serves for capturing
things. It may run in background without interrupting your work. It
can then spawn emacsclient to annotate or write the captured note.
next prev parent reply other threads:[~2020-12-14 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 18:23 Bug: org-capture does not work if called from minibuffer [9.4 (9.4-55-g706ba9-elpaplus @ /home/omarantolin/.emacs.d/elpa/org-plus-contrib-20201207/)] Omar Antolín Camarena
2020-12-12 17:55 ` Bastien
2020-12-14 18:58 ` Omar Antolín Camarena
2020-12-14 19:14 ` Jean Louis [this message]
2020-12-15 0:40 ` Omar Antolín Camarena
2020-12-15 4:51 ` Jean Louis
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).