From: Gustavo Barros <gusbrs.2016@gmail.com>
To: numbchild@gmail.com
Cc: emacs-orgmode@gnu.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: Wed, 23 Sep 2020 11:49:41 -0300 [thread overview]
Message-ID: <871rislf97.fsf@gmail.com> (raw)
In-Reply-To: <5f6b58e7.1c69fb81.c7d4c.c515@mx.google.com>
Hi stardiviner,
On Wed, 23 Sep 2020 at 11:17, stardiviner <numbchild@gmail.com> wrote:
> I have same issue when using Ivy. But can't reproduce this by disabled
> ivy-mode.
> And only happened when I refiled once, then the target will has two
> slash like this:
>
> #+begin_example
> Tasks/kk// (file.org)
> Tasks/hello/ (file.org)
> #+end_example
>
Thank you for checking this and for confirming you also observe this
behavior with Ivy.
Regarding when ivy-mode is off, as I argued in the original report, the
problem is indeed *not visible* when using `completing-read-default',
the double trailing slash is nevertheless there if you inspect the value
being passed as default value to the completing-read-function. The
tests included with ivy-mode turned off were meant to emphasize things
are expected to work with the suggested fix also in this case, in other
words, that this is not "just a fix for ivy-mode", which is not the
problem here.
Best,
Gustavo.
next prev parent reply other threads:[~2020-09-23 14:51 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 [this message]
2021-02-14 12:55 ` Gustavo Barros
2021-05-04 6:27 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
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
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=871rislf97.fsf@gmail.com \
--to=gusbrs.2016@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@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).