From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: dired-tests.el fails on MS-Windows
Date: Fri, 4 Aug 2017 16:01:25 +0200 [thread overview]
Message-ID: <CAFgFV9M0ut3OcgC9zWHOqhYtP7xjrHYyZy1BumkUj=v3WrQs5g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1708042239410.15299@calancha-pc>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
2017-08-04 15:44 GMT+02:00 Tino Calancha <tino.calancha@gmail.com>:
>
>
> On Fri, 4 Aug 2017, Fabrice Popineau wrote:
>
> (with-temp-file (expand-file-name "b.txt" dir2))
>> - (setq buf (dired (expand-file-name "dir*/*.txt" dir)))
>> + (setq buf (dired (cons dir (file-expand-wildcards
>> "dir*/*.txt"))))
>> (dired-toggle-marks)
>> (should (cdr (dired-get-marked-files))))
>> (delete-directory dir 'recursive)
>>
>> Am I wrong thinking that `expand-file-name' is not supposed to expand
>> "dir*/*.txt"?
>>
> Well we are using expand for 2 different things.
>
> 2) Expand shell wildcards.
> (dired (expand-file-name "lis*/*file" source-directory))
>
> This doesn't work here.
I have :
c:/tmp/dir1/foo.txt
c:/tmp/dir2/bar.txt
and:
(expand-file-name "dir*/*.txt" "c:/tmp/")
"c:/tmp/dir*/*.txt"
Moreover, as far as I can read it, `expand-file-name' documentation says
nothing about
expanding wildcards.
And last, `dired' maybe fed with a list, but the first argument needs to be
the directory
and the next ones, the files you want in the dired buffer, so I doubt that
`dired' will accomodate
the return value(s?) of `expand-file-name'?
-> In other words: I don't understand how this should work :-)
Fabrice
Shows a dired buffer with 3 files:
> lispref/Makefile
> lispintro/Makefile
> lisp/Makefile
>
[-- Attachment #2: Type: text/html, Size: 2506 bytes --]
next prev parent reply other threads:[~2017-08-04 14:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 15:22 dired-tests.el fails on MS-Windows Eli Zaretskii
2017-08-01 17:02 ` Tino Calancha
2017-08-01 19:04 ` Eli Zaretskii
2017-08-01 20:56 ` Fabrice Popineau
2017-08-02 6:44 ` Tino Calancha
2017-08-04 13:18 ` Eli Zaretskii
2017-08-04 13:30 ` Fabrice Popineau
2017-08-04 13:44 ` Tino Calancha
2017-08-04 14:01 ` Fabrice Popineau [this message]
2017-08-04 14:00 ` Eli Zaretskii
2017-08-04 5:21 ` Tino Calancha
2017-08-04 13:14 ` Eli Zaretskii
2017-08-04 13:39 ` Tino Calancha
2017-08-04 14:23 ` Fabrice Popineau
2017-08-04 14:39 ` Fabrice Popineau
2017-08-04 14:49 ` Tino Calancha
2017-08-04 14:58 ` Fabrice Popineau
2017-08-04 15:10 ` Tino Calancha
2017-08-01 20:52 ` Fabrice Popineau
2017-08-02 3:38 ` Tino Calancha
2017-08-02 6:31 ` Michael Albinus
2017-08-02 7:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFgFV9M0ut3OcgC9zWHOqhYtP7xjrHYyZy1BumkUj=v3WrQs5g@mail.gmail.com' \
--to=fabrice.popineau@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tino.calancha@gmail.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 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.