emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Allow %<num> escapes to capture templates, expanded	to text	entered in <num>'th prompt
Date: Tue, 24 Apr 2012 14:51:29 +0200	[thread overview]
Message-ID: <8762cp70oe.fsf@gnu.org> (raw)
In-Reply-To: <20120424110558.GA23688@c3po> (Toby Cubitt's message of "Tue, 24 Apr 2012 13:05:58 +0200")

Toby Cubitt <tsc25@cantab.net> writes:

> On Tue, Apr 24, 2012 at 11:57:02AM +0200, Bastien wrote:
>> I've pushed a change to this new feature: 
>> http://orgmode.org/w/?p=org-mode.git;a=commit;h=1666b9
>> Using %n is not good, because it will match many escaped 
>> strings that you don't want to match.  Using %\n looks
>> good to me as it resonates with \1 in replace-regexp.
>> Toby, let me know if you agree with this change.
> I'm fine with it. But I don't understand, what other escapes will it
> match? None of the other % escapes documented in org-capture-templates
> start with a digit, they all start with a letter or punctuation.

It is not the escapes from the capture template itself, but at the time
the capture buffer is prepared, links go to `org-make-link-string' which
calls `org-link-escape' which might in turn insert "%20" strings.


  reply	other threads:[~2012-04-24 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 22:47 [PATCH] Allow %<num> escapes to capture templates, expanded to text entered in <num>'th prompt Toby Cubitt
2012-04-23 12:54 ` Bastien
2012-04-23 15:08   ` Toby Cubitt
2012-04-23 15:12     ` Bastien
2012-04-23 15:29       ` Toby Cubitt
2012-04-23 15:34         ` Bastien
2012-04-24  9:57         ` Bastien
2012-04-24 11:05           ` Toby Cubitt
2012-04-24 12:51             ` Bastien [this message]
2012-04-24 13:37               ` Toby Cubitt

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:

  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=8762cp70oe.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


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