From: Ivan Kozlov <kanichos@yandex.ru>
To: "36733@debbugs.gnu.org" <36733@debbugs.gnu.org>
Subject: bug#36733: (no subject)
Date: Sat, 29 Feb 2020 12:40:15 +0300 [thread overview]
Message-ID: <1661721582969215@myt6-09be74140f25.qloud-c.yandex.net> (raw)
In-Reply-To: <1364681582939815@myt5-bc0f9d8e5f27.qloud-c.yandex.net>
29.02.2020, 04:30, "Ivan Kozlov" <kanichos@yandex.ru>:
>One further example: when complete-in-region-mode is active (again, _apparently_) and there is some text before the point, typing * (the asterisk character) runs some undocumented command which completes the argument if there is exactly one possible completion and doesn’t do anything otherwise, so it’s like TAB without the *Completions* buffer.
>
>So typing ls a<TAB>/* will produce ls a/b if b is the only file in a/, and ls a/ otherwise.
>
>This makes entering glob patterns (one of the most common tasks in shell) a *giant pain* with constantly hitting C-g and what not to make the completion stuff go away. I have no idea whether using * for the command was a deliberate decision, but it is really bad.
>
>Moreover, typing \ inserts \<TAB>! This one is inexplicable. It makes quoting characters a giant pain with constantly erasing the tab or cancelling the completion garbage as above.
I now realise what is actually going on here. Typing * and \ when completion-in-region-mode is active is exactly equivalent to activating this mode from a pattern ending in these characters.
In other words, a<TAB>* is equivalent to a*<TAB>, and a<TAB>\ is equivalent to a\<TAB>, which is actually supposed to allow escaping TAB.
Awful. The two cases should be treated completely differently.
next prev parent reply other threads:[~2020-02-29 9:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 21:21 bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion Jean Louis
2019-07-20 7:16 ` Eli Zaretskii
2019-07-20 7:50 ` Jean Louis
2019-07-20 8:31 ` Eli Zaretskii
2019-07-20 9:07 ` Jean Louis
2019-07-20 10:08 ` Eli Zaretskii
2019-07-20 10:31 ` Jean Louis
2019-07-20 10:55 ` Eli Zaretskii
2019-07-20 15:28 ` Jean Louis
2019-07-20 15:56 ` Eli Zaretskii
2019-07-20 16:22 ` Jean Louis
2019-07-20 16:40 ` Eli Zaretskii
2020-02-29 1:30 ` bug#36733: (no subject) Ivan Kozlov
2020-02-29 9:40 ` Ivan Kozlov [this message]
2020-02-29 3:51 ` bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion Ivan Kozlov
2020-02-29 6:40 ` Ivan Kozlov
2020-02-29 7:24 ` Ivan Kozlov
2020-02-29 7:56 ` Ivan Kozlov
2020-02-29 9:02 ` Ivan Kozlov
2020-02-29 9:33 ` Ivan Kozlov
2024-07-28 20:06 ` Jim Porter
2024-07-30 16:16 ` Jean Louis
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=1661721582969215@myt6-09be74140f25.qloud-c.yandex.net \
--to=kanichos@yandex.ru \
--cc=36733@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.