From: Noam Postavsky <npostavs@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Tom Tromey <tom@tromey.com>,
Michael Albinus <michael.albinus@gmx.de>,
31495@debbugs.gnu.org
Subject: bug#31495: 26.1; filename completion -vs- "*"
Date: Wed, 20 Jun 2018 08:36:35 -0400 [thread overview]
Message-ID: <87d0wlskh8.fsf@gmail.com> (raw)
In-Reply-To: <87wovzzs8c.fsf@gmail.com> (Tino Calancha's message of "Sat, 19 May 2018 22:32:03 +0900")
severity 31495 minor
quit
Tino Calancha <tino.calancha@gmail.com> writes:
> Tom Tromey <tom@tromey.com> writes:
>
>> Now in Emacs, C-x C-f /tmp/a/*/c TAB
>>
>> On the first TAB, a "/" is appended, and then point moves to the "/"
>> before "c".
> Yeah, it's broken.
> In this example adding a '/' makes the completion works
> C-x C-f /tmp/a/*/c/ TAB
Hmm, that makes it seem like the different behaviour without the
trailing slash is on purpose (though I can't see what that would be).
> +(defconst dired-enable-globstar-in-shell
> + '(("ksh" . "set -G")
> + ("bash" . "shopt -s globstar"))
> + "Alist of (SHELL . COMMAND), where COMMAND enables globstar in SHELL.
> +If `dired-maybe-use-globstar' is non-nil, then `dired-insert-directory'
> +checks this alist to enable globstar in the shell subprocess.")
Shouldn't this be a defvar or a defcustom? Using defconst makes it seem
like the code wouldn't handle it being changed.
next prev parent reply other threads:[~2018-06-20 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 15:33 bug#31495: 26.1; filename completion -vs- "*" Tom Tromey
2018-05-19 13:32 ` Tino Calancha
2018-05-19 18:17 ` Michael Albinus
2018-05-20 2:19 ` Tino Calancha
2018-06-20 12:36 ` Noam Postavsky [this message]
2018-06-20 12:48 ` Tino Calancha
2018-06-20 13:08 ` Tino Calancha
2018-06-20 14:05 ` Michael Albinus
2018-06-21 1:50 ` Tino Calancha
2018-06-21 7:19 ` Michael Albinus
2018-06-21 7:44 ` Tino Calancha
2020-08-22 15:40 ` Lars Ingebrigtsen
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=87d0wlskh8.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31495@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=tino.calancha@gmail.com \
--cc=tom@tromey.com \
/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).