From: Daniel Mendler <mail@daniel-mendler.de>
To: 53053@debbugs.gnu.org
Subject: bug#53053: 28.0.90; Tramp completion bug of path /sudo::~/
Date: Thu, 6 Jan 2022 13:52:49 +0100 [thread overview]
Message-ID: <58e88707-e8e1-604d-945a-4a1e234b86a5@daniel-mendler.de> (raw)
1. emacs -Q
2. C-x f /sudo::~/ (alternatively use an ssh path of a similar form)
3. Open the completion buffer by pressing ?
4. Click/select a directory in the completions buffer
The resulting path looks like this:
/sudo::~dir/
The underlying issue is that somewhere a wrong completion boundary is
reported by the Emacs completion table for non-normalized file paths
which contain ~. This issue also affects other completion UIs. The issue
is present on both 27 and 28.
(Original report: https://github.com/minad/vertico/issues/174)
In GNU Emacs 28.0.90 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.5,
cairo version 1.16.0)
of 2022-01-01 built on projects
Repository revision: efb1c7ec379430f560c5b801969ae43023c52734
Repository branch: emacs-28
Windowing system distributor 'The X.Org Foundation', version 11.0.12004000
System Description: Debian GNU/Linux 10 (buster)
next reply other threads:[~2022-01-06 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 12:52 Daniel Mendler [this message]
2022-01-07 14:05 ` bug#53053: 28.0.90; Tramp completion bug of path /sudo::~/ Michael Albinus
2022-02-04 0:11 ` Daniel Mendler
2022-02-05 14:42 ` Michael Albinus
2022-02-05 18:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-07 16:11 ` Daniel Mendler
2022-02-07 21:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 9:43 ` Michael Albinus
2022-02-17 13:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 15:04 ` Michael Albinus
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=58e88707-e8e1-604d-945a-4a1e234b86a5@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=53053@debbugs.gnu.org \
/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.