all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: Dired and wildcards
Date: Tue, 19 Jun 2007 22:41:09 +0300	[thread overview]
Message-ID: <uir9jraui.fsf@gnu.org> (raw)
In-Reply-To: <jeabuv6g60.fsf@sykes.suse.de> (message from Andreas Schwab on Tue, 19 Jun 2007 18:51:51 +0200)

> From: Andreas Schwab <schwab@suse.de>
> Cc: emacs-devel@gnu.org
> Date: Tue, 19 Jun 2007 18:51:51 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > And now to my original question: is there a way to tell Dired to
> > interpret "foo[bar]" as a wildcard, even though a file by that literal
> > name exists?  You seem to say there is no way, but I'm not sure I
> > understand you correctly.
> 
> An existing directory is always preferred, see dired-noselect:
> 
>     ;; If the argument was syntactically  a directory name not a file name,
>     ;; or if it happens to name a file that is a directory,
>     ;; convert it syntactically to a directory name.
>     ;; The reason for checking initially-was-dirname
>     ;; and not just file-directory-p
>     ;; is that file-directory-p is slow over ftp.
>     (if (or initially-was-dirname (file-directory-p dirname))
> 	(setq dirname  (file-name-as-directory dirname)))

Okay, thanks.

In case you are wondering, I asked these questions because the ls-lisp
emulation seems not to behave this way.

  reply	other threads:[~2007-06-19 19:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19  7:43 Dired and wildcards Eli Zaretskii
2007-06-19  8:40 ` Andreas Schwab
2007-06-19 15:17   ` Eli Zaretskii
2007-06-19 15:30     ` Andreas Schwab
2007-06-19 16:17       ` Eli Zaretskii
2007-06-19 16:51         ` Andreas Schwab
2007-06-19 19:41           ` Eli Zaretskii [this message]
2007-06-19 17:53         ` Stefan Monnier
2007-06-19 19:38           ` Eli Zaretskii

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=uir9jraui.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    /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.