bug: cannot refile x to x, or go to x, where headers have the same name

bug: cannot refile x to x, or go to x, where headers have the same name

[Samuel Wales]

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?

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?

thanks.

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  And
ANYBODY can get it.

Denmark: free Karina Hansen NOW.

Re: bug: cannot refile x to x, or go to x, where headers have the same name

[Nicolas Goaziou]

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

Re: bug: cannot refile x to x, or go to x, where headers have the same name

[Samuel Wales]

thank you!

On 4/5/16, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> 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
>


-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  And
ANYBODY can get it.

Denmark: free Karina Hansen NOW.