emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "François Allisson" <francois@allisson.co>
Cc: Org mode <emacs-orgmode@gnu.org>
Subject: Re: Capture template expansion: feature or bug?
Date: Sat, 17 Mar 2018 15:17:52 +0100	[thread overview]
Message-ID: <87zi36dbvz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m1y3ixgswi.fsf@allisson.co> ("François Allisson"'s message of "Mon, 12 Mar 2018 17:28:29 +0100")

Hello,

François Allisson <francois@allisson.co> writes:

> When one uses the following template expansion,
>
>> %^{prop}p   Prompt the user for a value for property ‘prop’.
>
> it supposes one to supply a non-empty string of characters. If one
> simply hits RETURN on a given prompt for property, the capture process
> ends with an
>
>> org-capture: Capture abort: (quit)
>
> message. This means that all prompts for properties are mandatory. It
> this a feature or a bug?

I tried reproducing your issue with the following template:

  ("B" "BUG" entry (file "/tmp/bug-capture.org") "* %?%^{prop}p")

However, I cannot reproduce it.

> Of course, if I ask the question, it is because I clearly see use cases
> for optional properties prompts (which would leave empty the property in
> question): you ask for several information, which you don't always have;
> and you don't want the capture process to quit because of that. But may
> be there is a better way to achieve this?

Another problem is: do you want to skip the property altogether, or set
it to an empty string?

> Org 9.0.10 / Emacs 25.2.1

I suggest to update Org, BTW.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2018-03-17 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 16:28 Capture template expansion: feature or bug? François Allisson
2018-03-17 14:17 ` Nicolas Goaziou [this message]

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zi36dbvz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=francois@allisson.co \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).