all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28567@debbugs.gnu.org
Subject: bug#28567: 27.0.50; `directory-files-recursively' signals an error if there is some inaccessible subdirectory
Date: Wed, 7 Aug 2019 13:10:29 +0200	[thread overview]
Message-ID: <CAArVCkSw=Emk_fC7uJ-4m++WQwwBR4xTTPhps9fnQXj0MaZA=A@mail.gmail.com> (raw)
In-Reply-To: <877e8jei8c.fsf@mouse.gnus.org>

Am Mo., 15. Juli 2019 um 11:53 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Philipp <p.stephani2@gmail.com> writes:
>
> > mkdir c c/c
> > chmod 0000 c/c
> > emacs -Q -batch -f toggle-debug-on-error -eval '(directory-files-recursively "/tmp/c" "foo")'
> > Debug on Error enabled globally
> > Debugger entered--Lisp error: (file-error "Opening directory" "Permission denied" "/tmp/c/c")
> >   file-name-all-completions("" "/tmp/c/c")
> >   directory-files-recursively("/tmp/c/c" "foo" nil)
> >   directory-files-recursively("/tmp/c" "foo")
> >   eval((directory-files-recursively "/tmp/c" "foo"))
> >   command-line-1(("-f" "toggle-debug-on-error" "-eval" "(directory-files-recursively \"/tmp/c\" \"foo\")"))
> >   command-line()
> >   normal-top-level()
> >
> > It's probably fine to have this behavior by default (some users might
> > want strict errors when some subdirectory couldn't be listed), but I
> > think the function should have an optional argument to control the
> > behavior.
>
> Yup.  I've now fixed this on the trunk -- there's now an optional
> PREDICATE parameter that can be t for "ignore file-error".

Thanks!





      reply	other threads:[~2019-08-07 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-23 12:06 bug#28567: 27.0.50; `directory-files-recursively' signals an error if there is some inaccessible subdirectory Philipp
2019-07-15  9:53 ` Lars Ingebrigtsen
2019-08-07 11:10   ` Philipp Stephani [this message]

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='CAArVCkSw=Emk_fC7uJ-4m++WQwwBR4xTTPhps9fnQXj0MaZA=A@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=28567@debbugs.gnu.org \
    --cc=larsi@gnus.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 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.