all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Omar Antolín Camarena" <omar@matem.unam.mx>, 40625@debbugs.gnu.org
Subject: bug#40625: 28.0.50; fido-mode cannot match candidates containing a space
Date: Thu, 16 Apr 2020 09:39:10 +0100	[thread overview]
Message-ID: <CALDnm52PieE3NEk1H1QKy0BcBL5eMdo9jgto4aZaV=WUDpqc3g@mail.gmail.com> (raw)
In-Reply-To: <4a7a228c-ddcd-0f39-d7f6-5f22aef44603@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

On Wed, Apr 15, 2020 at 8:38 PM Dmitry Gutov <dgutov@yandex.ru> wrote:
>
> On 15.04.2020 20:44, João Távora wrote:
> > Done. Closing this.
>
> There was also a complaint about icomplete-fido-backward-updir's
> misbehavior when a directory contains a space at the end of the original
> report.
>
> I think the proposed fix is fine. Although we could also consider
> whether we can fix it in a way that also supports directory names with
> '/' in them. Completion fields and boundaries come to mind.

I went with the simpler fix.  Annnd just remembered I forgot to
give Omar credit.

Sorry Omar, and many thanks,
João

[-- Attachment #2: Type: text/html, Size: 855 bytes --]

  reply	other threads:[~2020-04-16  8:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 16:01 bug#40625: 28.0.50; fido-mode cannot match candidates containing a space Omar Antolín Camarena
2020-04-14 23:06 ` Dmitry Gutov
2020-04-15  0:04   ` João Távora
2020-04-15 15:46     ` João Távora
2020-04-15 16:02       ` João Távora
2020-04-15 16:05         ` Eli Zaretskii
2020-04-15 17:17         ` Dmitry Gutov
2020-04-15 17:26           ` Omar Antolín Camarena
2020-04-15 17:41             ` João Távora
2020-04-15 17:44           ` João Távora
2020-04-15 19:38             ` Dmitry Gutov
2020-04-16  8:39               ` João Távora [this message]
2020-04-16 16:56                 ` Omar Antolín Camarena

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALDnm52PieE3NEk1H1QKy0BcBL5eMdo9jgto4aZaV=WUDpqc3g@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=40625@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=omar@matem.unam.mx \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.