From: Drew Adams <drew.adams@oracle.com>
To: 18836@debbugs.gnu.org
Subject: bug#18836: 25.0.50; `insert-directory' barfs on nonexistent file, but not for `ls-lisp-insert-directory'
Date: Sat, 25 Oct 2014 12:55:05 -0700 (PDT) [thread overview]
Message-ID: <f7e93777-9e03-4430-8550-6a3fbd5d5ea0@default> (raw)
It seems that at least on some platforms (e.g. GNU/Linux), if you give
an explicit list of files and dirs to `dired', to list (which you do by
passing a cons as argument DIRNAME), the command fails with an error:
(file-error "Reading directory"
"no such file or directory"
"/usr/foo/no-such-file.txt")
No such error is raised on platforms that use `ls-lisp'.
This non-`ls-lisp' behavior is not as friendly as it could be, and not
as friendly as the `ls-lisp-insert-directory' behavior, which simply
displays a message and then calls `ding':
(message "%s: doesn't exist or is inaccessible" file)
Would it be possible to make vanilla `insert-directory' more tolerant,
i.e., make it act like `ls-lisp-insert-directory', in this respect?
Failing to access a single file should not prevent listing the others,
if this can be handled properly. But maybe it's not feasible; dunno.
[FWIW, I would even prefer to see the file or dir listed in the Dired
buffer, even if it does not (yet) exist. Let user attempts to actually
access it raise an error, and let no error be raised if the file is
created after creating the Dired buffer but before the user tries to
access the file.]
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2014-10-25 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 19:55 Drew Adams [this message]
2016-04-30 14:56 ` bug#18836: 25.0.50; `insert-directory' barfs on nonexistent file, but not for `ls-lisp-insert-directory' Lars Ingebrigtsen
2016-04-30 15:39 ` Eli Zaretskii
2016-04-30 15:46 ` Lars Ingebrigtsen
2016-04-30 15:53 ` Eli Zaretskii
2016-04-30 16:05 ` Lars Ingebrigtsen
2016-04-30 16:20 ` Eli Zaretskii
2022-01-25 14:13 ` Lars Ingebrigtsen
2022-01-25 16:07 ` bug#18836: [External] : " Drew Adams
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=f7e93777-9e03-4430-8550-6a3fbd5d5ea0@default \
--to=drew.adams@oracle.com \
--cc=18836@debbugs.gnu.org \
/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).