From: "Sebastian Reuße" <seb@wirrsal.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org: Support creating arbitrary headline paths when refiling
Date: Sun, 14 Oct 2018 10:05:38 +0200 [thread overview]
Message-ID: <87bm7xhs19.fsf@wirrsal.net> (raw)
In-Reply-To: <87tvlpdlke.fsf@nicolasgoaziou.fr>
Hello Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> I still cannot make it work property.
>
> With the following document:
>
> --8<---------------cut
> here---------------start------------->8---
> * Foo
> ** Bar
> * Foo2
> --8<---------------cut
> here---------------end--------------->8---
>
> Trying to refile "Foo2" under "Foo/Bar/Baz/" results in:
>
> --8<---------------cut
> here---------------start------------->8---
> * Foo
> ** Bar
> * Foo
> ** Bar
> *** Baz
> **** Foo2
> --8<---------------cut
> here---------------end--------------->8---
This was due to the trailing slash in the refile target. I now
amended the regex to normalize such input and added a test case
with a trailing slash. Care to give it another spin?
Kind regards,
S.
--
Insane cobra split the wood
Trader of the lowland breed
Call a jittney, drive away
In the slipstream we will stay
next prev parent reply other threads:[~2018-10-14 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 13:58 [PATCH] org: Support creating arbitrary headline paths when refiling Sebastian Reuße
2018-10-10 10:49 ` Nicolas Goaziou
2018-10-10 11:24 ` Sebastian Reuße
2018-10-11 6:35 ` Sebastian Reuße
2018-10-11 11:30 ` Sebastian Reuße
2018-10-14 7:38 ` Nicolas Goaziou
2018-10-14 8:04 ` Sebastian Reuße
2018-10-14 8:58 ` Headlines with slashes " Sebastian Reuße
2018-10-14 8:05 ` Sebastian Reuße [this message]
2018-10-14 14:14 ` [PATCH] org: Support creating arbitrary headline paths " Nicolas Goaziou
2018-10-14 14:30 ` Sebastian Reuße
2018-10-14 20:24 ` Nicolas Goaziou
2018-10-10 11:27 ` Sebastian Reuße
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=87bm7xhs19.fsf@wirrsal.net \
--to=seb@wirrsal.net \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).