From: Tino Calancha <tino.calancha@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Tino Calancha <tino.calancha@gmail.com>,
Michael Albinus <michael.albinus@gmx.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master e82c4f5: Don't assume /bin/sh as the 'sh' location in the local host
Date: Wed, 2 Aug 2017 22:46:06 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1708022232430.7310@calancha-pc> (raw)
In-Reply-To: <jwvefsuayk6.fsf-monnier+emacsdiffs@gnu.org>
On Wed, 2 Aug 2017, Stefan Monnier wrote:
>> Don't assume /bin/sh as the 'sh' location in the local host
> [...]
>> + (and (bound-and-true-p explicit-shell-file-name)
>> + (executable-find explicit-shell-file-name))
>
> Hmm... why did you choose explicit-shell-file-name over shell-file-name?
It was mentioned by Michael as a possibility. I chose it because is a
defcustom: it might reflect an user preference compared with
shell-file-name which is given.
For example, my shell-file-name is bash. I might customize
explicit-shell-file-name to '/bin/zsh', then i can
use '**/' zsh syntaxis in the wildcard expansion:
(let ((buf
(dired-noselect (expand-file-name "**/*.el" source-directory))))
(with-current-buffer buf
(dired-toggle-marks)
(length (dired-get-marked-files))))
=> 1731
;; => 277 ; If i would use shell-file-name
We might changed it if you don't like it.
next prev parent reply other threads:[~2017-08-02 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170802075459.16207.16636@vcs0.savannah.gnu.org>
[not found] ` <20170802075500.60BEA20E71@vcs0.savannah.gnu.org>
2017-08-02 13:29 ` [Emacs-diffs] master e82c4f5: Don't assume /bin/sh as the 'sh' location in the local host Stefan Monnier
2017-08-02 13:46 ` Tino Calancha [this message]
2017-08-02 15:54 ` Stefan Monnier
2017-08-02 16:04 ` Tino Calancha
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=alpine.DEB.2.20.1708022232430.7310@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.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 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).