From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bug: cannot refile x to x, or go to x, where headers have the same name
Date: Tue, 05 Apr 2016 23:49:57 +0200 [thread overview]
Message-ID: <87mvp74tfe.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8uAOKr2ZvMDLB703NeOP5U+Rv0UVjU-KDoE7tZHNS-mCQ@mail.gmail.com> (Samuel Wales's message of "Mon, 4 Apr 2016 21:09:55 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> i often refile a header to a target that has the same name as the
> source. they are different headers, but they have the same name.
>
> my goal is to send x(1) to x(2) so that the olpath looks like
> x(2)/x(1). this to me is totally legitimate. i often have headers
> with the same name, for various reasons.
>
> but org-refile removes the /source/ header name from the list of
> /target/ candidates. perhaps the intention was to prevent refiling
> something to itself. did that cause problems?
There's a guard against it later in the process, so I guess it doesn't
matter here.
> but i am not refiling something to itself. they just have the same
> name. they are different headers.
>
> furthermore, the same bug occurs with refile goto.
>
> i can work around this by adding random text to the source header, or
> moving point for goto, but i'd rather not have to.
>
> can this interlock ve disabled or modified to allow different headers
> with the same name?
I disabled this exclusion in master.
Thank you for suggesting it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-04-05 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 4:09 bug: cannot refile x to x, or go to x, where headers have the same name Samuel Wales
2016-04-05 21:49 ` Nicolas Goaziou [this message]
2016-04-05 22:26 ` Samuel Wales
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=87mvp74tfe.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).