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: Juri Linkov <juri@jurta.org>
Cc: Manuel Uberti <manuel.uberti@inventati.org>,
	Stefan Kangas <stefankangas@gmail.com>,
	50732@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#50732: 28.0.50; project-find-dir: blank line in fido-vertical-mode
Date: Wed, 22 Sep 2021 17:55:01 +0100	[thread overview]
Message-ID: <CALDnm50Ct+eu9oovxNKymm0asjpDzG2FqZznh0tn+zY0G+AT6g@mail.gmail.com> (raw)
In-Reply-To: <87pmt0sgdl.fsf@mail.linkov.net>

On Wed, Sep 22, 2021 at 5:52 PM Juri Linkov <juri@jurta.org> wrote:

> > Regardless (I really think you should do the above), I don't object
> > to adding your "<empty>" idea to Icomplete and everywhere else
> > in Emacs that is affected by this.  At least I don't see any immediate
> > problems with that idea.  So the two things aren't mutually exclusive.
>
> I don't know if empty strings make sense as completion candidates.

I also don't. But if some backends do produce them, maybe it does make
sense to represent them in a slightly better way.

João





  reply	other threads:[~2021-09-22 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22  8:23 bug#50732: 28.0.50; project-find-dir: blank line in fido-vertical-mode Manuel Uberti
2021-09-22 12:01 ` Dmitry Gutov
2021-09-22 13:10   ` Manuel Uberti
2021-09-22 13:25     ` Dmitry Gutov
2021-09-22 13:36       ` João Távora
2021-09-22 14:46         ` Manuel Uberti
2021-09-22 16:14       ` Juri Linkov
2021-09-22 16:21         ` João Távora
2021-09-22 16:24           ` João Távora
2021-09-22 16:51             ` Juri Linkov
2021-09-22 16:55               ` João Távora [this message]
2021-09-22 18:09         ` Dmitry Gutov
2021-09-24 17:19           ` Stefan Kangas

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=CALDnm50Ct+eu9oovxNKymm0asjpDzG2FqZznh0tn+zY0G+AT6g@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=50732@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=juri@jurta.org \
    --cc=manuel.uberti@inventati.org \
    --cc=stefankangas@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 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.