From: Tino Calancha <tino.calancha@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Tom Tromey <tom@tromey.com>, 31495@debbugs.gnu.org
Subject: bug#31495: 26.1; filename completion -vs- "*"
Date: Sun, 20 May 2018 11:19:37 +0900 [thread overview]
Message-ID: <871se7hxvq.fsf@gmail.com> (raw)
In-Reply-To: <87tvr3mrwh.fsf@gmx.de> (Michael Albinus's message of "Sat, 19 May 2018 20:17:34 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Tino Calancha <tino.calancha@gmail.com> writes:
>
> Hi Tino,
>
>> We could even let the user enable globstar in those shells supporting
>> it but having it disable by default (e.g. bash).
>
> What about ls-lisp?
It would be great to have there but it's out of the
scope of the patch yet. This is not about add a new dired
feature. Instead, the target is to turn on a
feature from your shell that is disabled by default.
If you use em-ls you have this feature. Same as if you use
external program `ls' from zsh or fish shells.
The idea is to let users if they want to enable globstar
in their shell when its disabled by default.
>> +(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.")
>
> This works only if the shell name like bash or ksh is used. Often, just
> /bin/sh is used, and you don't know which real shell this file is linked to.
My patch use `file-truename' to get the actual shell
used by `dired-insert-directory'.
next prev parent reply other threads:[~2018-05-20 2:19 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 [this message]
2018-06-20 12:36 ` Noam Postavsky
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=871se7hxvq.fsf@gmail.com \
--to=tino.calancha@gmail.com \
--cc=31495@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--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).