From: "Drew Adams" <drew.adams@oracle.com>
To: "'Thierry Volpiatto'" <thierry.volpiatto@gmail.com>,
<6636@debbugs.gnu.org>
Subject: bug#6636: 24.0.50; special dired feature confuse all dired commands.
Date: Thu, 15 Jul 2010 11:16:58 -0700 [thread overview]
Message-ID: <B0FE0DD833CF4B69BE37A885EF05D6C7@us.oracle.com> (raw)
In-Reply-To: <8739vlurj7.fsf@tux.homenetwork>
> Start in directory "/home/you"
> (dired (cons "My Working dir" (dired-get-marked-files)))
>
> Now trying any dired commands (e.g delete, copy etc...) partially fail
> with wrong type argument stringp....(("/foo" "/bar" "/baz"))
>
> If you eval dired-buffers you can see that "/home/you" is linked to
> buffer "My Working dir" (done by `dired-advertise')
> which is wrong and confuse all dired commands.
The is in `dired-buffers-for-dir'. It has this code:
(file-name-non-directory dired-directory)
This is wrong. `dired-directory' has every right to be a cons, as it is in this
case.
Function `dired-buffers-for-dir' was introduced in 23.1, creating this
regression wrt Emacs 22.3 and prior releases.
--
FWIW -
This problem, like previous (fixed) bugs surrounding the use of a cons as the
arg to `dired', comes about because this wonderful Dired feature is not
sufficiently well known. It is hardly even documented, yet it is very useful.
IOW, IMO the first bug wrt this is that the doc is paltry wrt this feature.
Code bugs tend to follow, because Emacs developers (like Emacs users in general)
are not thinking about the cons case for `dired-directory'.
next prev parent reply other threads:[~2010-07-15 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 7:34 bug#6636: 24.0.50; special dired feature confuse all dired commands Thierry Volpiatto
2010-07-15 18:16 ` Drew Adams [this message]
2010-07-17 20:43 ` Chong Yidong
2010-07-17 21:06 ` Drew Adams
2010-07-18 5:24 ` Thierry Volpiatto
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=B0FE0DD833CF4B69BE37A885EF05D6C7@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=6636@debbugs.gnu.org \
--cc=thierry.volpiatto@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.