From: Bastien <email@example.com>
To: Gustavo Barros <firstname.lastname@example.org>
Subject: Re: Bug: Double trailing slash for default candidate in org-refile-get-target [9.4 (9.4-7-g3eccc5-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200921/)]
Date: Tue, 04 May 2021 08:27:10 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Gustavo Barros's message of "Mon, 21 Sep 2020 15:34:23 -0300")
Gustavo Barros <email@example.com> writes:
> some time ago, I've reported an issue regarding duplicity of the default
> candidate in `org-refile'
> (https://firstname.lastname@example.org/). The problem was
> that, when using `org-refile-use-outline-path' an "extra" slash was
> appended at the end of every path, but candidates were stored in
> `org-refile-history' without that extra slash. Bastien took care of
> that and indeed changed things so as to pass the elements to
> `org-refile-history' with the trailing slash as appropriate.
> At the time, I reported a difference of behavior between
> `completing-read-default' and `ivy-completing-read' after the mentioned
> commit by Bastien. But the issue did not appear for Bastien, which does
> not use Ivy, and I also was not able to diagnose the problem properly.
> I felt I didn't have enough to offer as to insist, so I resorted to an
> old hack of mine. But the new release this week (thank you very much!,
> btw) has bitten me again on this, so I went back to some digging, and
> hopefully I can do a better job this time in diagnosing the problem and
> suggesting a fix.
Bump this thread so that it appears on updates.orgmode.org.
next prev parent reply other threads:[~2021-05-04 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 18:34 Bug: Double trailing slash for default candidate in org-refile-get-target [9.4 (9.4-7-g3eccc5-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200921/)] Gustavo Barros
2020-09-23 14:17 ` stardiviner
2020-09-23 14:49 ` Gustavo Barros
2021-02-14 12:55 ` Gustavo Barros
2021-05-04 6:27 ` Bastien [this message]
2021-05-10 18:04 Bhavin Gandhi
2021-05-23 18:05 ` Bhavin Gandhi
2021-05-23 18:23 ` Timothy
2021-05-23 18:58 ` Gustavo Barros
2021-05-24 16:34 ` Bhavin Gandhi
2021-05-24 16:58 ` Gustavo Barros
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 \
* 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).