[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [PATCH 2/2] org-refile: Fix inconsistency when listing refile ta
Re: [O] [PATCH 2/2] org-refile: Fix inconsistency when listing refile targets
Thu, 6 Jul 2017 23:55:34 -0700
Yes, 2906e50177d47 is needed on maint. However, my understanding is
that on maint we still escape filesystem slashes in the outline path?
If so, org-protect-path will be needed around the file-truename in
My workflow recently changed such that I no longer need to set
org-refile-use-outline-path to full-file-path, so my interest in this
bug has dropped accordingly, but it is still a bug on maint that
breaks refiling, so I think the fix should be backported unless there
are plans for a main -> maint merge soon.
On Sun, Jul 2, 2017 at 11:44 PM, Nicolas Goaziou <address@hidden> wrote:
> Allen Li <address@hidden> writes:
>> I just realized that this patch was applied to the master branch, not
>> the maint branch.
>> The absence of this patch results in the continued life of a bug in
>> the maint branch where it is not possible to refile to the top level
>> of an agenda file when using full-file-path for
>> Is it possible to backport this to the maint branch? This will
>> require adding the org-protect-slash that I mentioned earlier in this
>> thread. Otherwise, refile is basically unusable for me when
>> full-file-path is set.
> Wouldn't 2906e50177d47b4f4a0e75532a0c9dcc9cf72824 be sufficient in your
> If not, what commits are required?
> Nicolas Goaziou