From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 47678@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#47678: 27.1; `completion-boundaries` assertion failure for file
Date: Sun, 09 May 2021 09:37:44 -0400 [thread overview]
Message-ID: <jwvfsywyr44.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8102d308-0c23-f3ac-93c2-1634abe24acc@daniel-mendler.de> (Daniel Mendler's message of "Sun, 9 May 2021 10:34:52 +0200")
> Thank you for the clarification. I agree. A while ago when fiddling with
> file based commands I had wondered why completing-read or the UI can
> even return shadowed paths leading to complications down the road. A
> canonicalize method would be a good way to achieve this generically. Are
> there more examples where one would want to do such a canonicalization?
Good question. I can imagine it being used in a few other "file-like"
completion tables (e.g. MH mailboxes), but it doesn't seem nearly as
useful. There might also be some possible uses in a context of quoting
where it could return the string but quoted in a "canonical way"
(e.g. for file names, it could maybe double the lone `$` signs that
happen not to match any env-var, or add {...} around the env-vars), ...
But no, none of those are very compelling candidates.
For this reason, the current hack lives on.
> What do you mean by "providing a method"?
Nothing specific.
Stefan
prev parent reply other threads:[~2021-05-09 13:37 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
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 [this message]
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=jwvfsywyr44.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=47678@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mail@daniel-mendler.de \
--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 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.