From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Barros Subject: Re: Bug: org-refile-get-target offers default candidate in duplicity [9.2.6 (9.2.6-4-ge30905-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20191007/)] Date: Sun, 16 Feb 2020 21:45:06 -0300 Message-ID: <87r1yuxcrx.fsf@gmail.com> References: <87lftw1k2n.fsf@gmail.com> <875zgb7520.fsf@gnu.org> <87sgjfgsoy.fsf@gmail.com> <87a75nexqy.fsf@gnu.org> <877e0qw14d.fsf@gmail.com> <87h7zttrjo.fsf@bzg.fr> <871rqxyyiw.fsf@gmail.com> <87zhdiqfrj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33398) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j3UXA-0008MW-UN for emacs-orgmode@gnu.org; Sun, 16 Feb 2020 19:45:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j3UX9-0003a0-UI for emacs-orgmode@gnu.org; Sun, 16 Feb 2020 19:45:12 -0500 In-reply-to: <87zhdiqfrj.fsf@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Bastien Cc: emacs-orgmode@gnu.org Hi Bastien, On Sun, Feb 16 2020, Bastien wrote: > Hi Gustavo, > > Gustavo Barros writes: > >> But the fact that >> 'completing-read-default' returns the refile location with a double >> trailing slash makes me think there is still something to be fixed in >> 'org-refile-get-location'. > > if you're not tired of the hunt, please tell us when you find what > needs to be fixed--since there is no bug attached to this, I'll set > this aside for now. I'm afraid I have broken proper sequence of this thread unintentionally. This strip you quote comes from a message I eventually sent 14/Feb 12:33, right after a message of yours at 12:29 in which you concluded: > From what I understand, this is not a bug in Org. I hope you can fix > this somehow, maybe upstream. The fact is that I was writing mine when yours came, and I didn't see yours until later. And when I did, the reply was: > I don't claim a problem persists in Org, and I was just trying to be > thorough > in the testing you requested. And did so with pleasure. So... > >> From what I understand, this is not a bug in Org. > > ... if you are satisfied, I'm happy with that too. > > Thank you very very much! So, with the messages in proper order, I was taken the issue as settled. If, however, you do think in my message of 12:29 I hit something which might be relevant, I'd be happy to pursue this further. I'm "not tired of the hunt", but I fear the issue might well be out of my league, so there is a real risk of me wasting your time and increasing the noise on the list. Besides, as reported before, it appears not to impact functionality. But, if knowing that, you would like me to do so, I'll be glad to try. In this case, let me know. Otherwise just: > set this aside for now. And thanks again! Best, Gustavo.