From: Daniel Mendler <mail@daniel-mendler.de>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 47678@debbugs.gnu.org
Subject: bug#47678: 27.1; `completion-boundaries` assertion failure for file
Date: Thu, 6 May 2021 13:07:40 +0200 [thread overview]
Message-ID: <214d78e9-cda2-e2f2-7284-0f4f6bda43b7@daniel-mendler.de> (raw)
In-Reply-To: <87v97wxjtf.fsf@gnus.org>
On 5/6/21 12:01 PM, Lars Ingebrigtsen wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> IOW I consider the existence of `vertico--tidy-shadowed-file` as a bug
>> in itself ;-)
>
> Skimming this thread, I'm not sure whether there's anything to be done
> in Emacs here?
@Stefan The existence of this function is a bug for people who want to
keep their shadowed paths. This is a matter of preference. For me
shadowed paths are a cheap means of changing the directory during
completion and I usually don't want to go back to the old path in the
process. Icomplete has the same function, but guarded behind a
customization option. Why do you prefer to keep the shadowed paths?
@Lars From what I see, Stefan already fixed the bug?
Daniel
next prev parent reply other threads:[~2021-05-06 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 20:35 bug#47678: 27.1; `completion-boundaries` assertion failure for file Daniel Mendler
2021-04-12 23:28 ` Stefan Monnier
2021-04-13 4:04 ` Daniel Mendler
2021-04-13 12:46 ` Stefan Monnier
2021-04-13 14:44 ` Daniel Mendler
2021-04-13 22:34 ` Stefan Monnier
2021-05-06 10:01 ` Lars Ingebrigtsen
2021-05-06 11:07 ` Daniel Mendler [this message]
2021-05-07 11:14 ` Lars Ingebrigtsen
2021-05-08 23:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-09 8:34 ` Daniel Mendler
2021-05-09 13:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=214d78e9-cda2-e2f2-7284-0f4f6bda43b7@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=47678@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.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).