From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 53053@debbugs.gnu.org
Subject: bug#53053: 28.0.90; Tramp completion bug of path /sudo::~/
Date: Sat, 05 Feb 2022 15:42:57 +0100 [thread overview]
Message-ID: <87h79dml1q.fsf@gmx.de> (raw)
In-Reply-To: <e55a5c8e-fd2a-8b1f-021b-865bd45fc188@daniel-mendler.de> (Daniel Mendler's message of "Fri, 4 Feb 2022 01:11:56 +0100")
Daniel Mendler <mail@daniel-mendler.de> writes:
> Hi Michael,
Hi Daniel,
> thank you for your response! The issue came up again in
> https://github.com/minad/vertico/issues/193. The issue is that the
> completion boundaries are reported incorrectly by the file completion
> table or the Tramp backend.
>
> For example both
>
> (completion-boundaries "/sudo::~/" #'read-file-name-internal nil "")
> (completion-boundaries "/sudo::/" #'read-file-name-internal nil "")
>
> incorrectly return (8 . 0) as boundaries. These values are reported by
> the 'boundaries action of the completion table. I am not sure if the bug
> is on the layer of Tramp or on a level above. I cc'ed Stefan, he
> probably knows the precise location.
Tramp doesn't know anything about completion-boundaries.
> Daniel
Best regards, Michael.
next prev parent reply other threads:[~2022-02-05 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 12:52 bug#53053: 28.0.90; Tramp completion bug of path /sudo::~/ Daniel Mendler
2022-01-07 14:05 ` Michael Albinus
2022-02-04 0:11 ` Daniel Mendler
2022-02-05 14:42 ` Michael Albinus [this message]
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=87h79dml1q.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=53053@debbugs.gnu.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.