From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 4673@debbugs.gnu.org
Subject: bug#4673: Not the same as 4674
Date: Fri, 03 Feb 2012 13:18:12 +0200 [thread overview]
Message-ID: <83vcnodv2j.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ojei=rkuaMx3EFj2zN0H=yrBjwAaoKYUvXJND-pRnqVgQ@mail.gmail.com>
> Date: Tue, 31 Jan 2012 11:51:27 +0000
> From: Richard Copley <rcopley@gmail.com>
>
> This is a separate bug from 4673 (which I believe is fixed). Can they
> be un-merged?
Done.
> Visiting a Windows DFS share when ".." is not accessible still crashes
> in `ls-lisp-insert-directory' in the trunk of Emacs, as the attribute
> list for ".." in the `file-alist' returned for by
> `directory-files-and-attributes' is empty.
What does the following yield for a DFS share?
M-: (file-attributes "//root/share/.." 'string) RET
For that matter, what does the following cmd command display?
dir /n/q/a:d \\root\share
> Meanwhile, back in `ls-lisp-insert-directory', (format "%d" fuid)
> fails with (error "Format specifier doesn't match argument type").
I will work on making ls-lisp-insert-directory be more tolerant of
such use cases, but it is important for me to understand whether or
not there is really a ".." entry on such shares, as this will
determine if we want to display them in some way or simply omit them
from the directory listing in Dired. The above questions will help me
make up my mind about that.
TIA
next prev parent reply other threads:[~2012-02-03 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 13:43 bug#4673: 23.1; UNC paths of the form "//DFSROOT/SHARE" Richard Copley
2012-01-31 11:51 ` bug#4673: Not the same as 4674 Richard Copley
2012-02-03 11:18 ` Eli Zaretskii [this message]
2012-02-03 12:17 ` Richard Copley
2012-02-04 9:05 ` Eli Zaretskii
2012-02-07 15:30 ` Richard Copley
2012-02-07 17:30 ` 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=83vcnodv2j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=4673@debbugs.gnu.org \
--cc=rcopley@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.