From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, 27871@debbugs.gnu.org
Cc: Philipp Stephani <phst@google.com>
Subject: bug#27871: [PATCH] Treat unreachable current directory as error
Date: Sun, 08 Oct 2017 14:56:11 +0000 [thread overview]
Message-ID: <CAArVCkRnbHdNx++6dbB-zUtmWieza3rKiQ-1t15P95jama5ZVg@mail.gmail.com> (raw)
In-Reply-To: <9b7b9905-dc97-feb4-9569-27372b1c6b5d@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am So., 8. Okt. 2017 um 08:06 Uhr:
> Philipp Stephani wrote:
> > All of the current directory functions exhibit this behavior, including
> > getwd and getcwd, so you need to make sure they are also covered.
>
> Thanks for letting us know. I installed the 2nd attached patch, which
> addresses
> this by making the patch behave more like what you originally proposed,
> while
> still avoiding the need to use file_name_absolute_p (which is about Emacs
> file
> names, not OS names).
>
That should work, thanks. FTR, this behavior is documented in the Linux
manpage: http://man7.org/linux/man-pages/man2/getcwd.2.html
[-- Attachment #2: Type: text/html, Size: 1020 bytes --]
prev parent reply other threads:[~2017-10-08 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 21:06 bug#27871: 26.0.50; Bad handling of unmounted directory Philipp
2017-09-23 10:19 ` Philipp Stephani
2017-09-23 10:39 ` Eli Zaretskii
2017-09-23 11:30 ` Andreas Schwab
2017-09-23 11:33 ` Philipp Stephani
2017-09-23 11:38 ` Eli Zaretskii
2017-09-23 11:41 ` Eli Zaretskii
2017-09-30 18:49 ` Philipp Stephani
2017-09-30 18:50 ` bug#27871: [PATCH] Treat unreachable current directory as error Philipp Stephani
[not found] ` <20170930185006.54096-1-phst@google.com>
2017-10-01 0:00 ` Paul Eggert
2017-10-05 10:13 ` Eli Zaretskii
2017-10-05 23:06 ` Paul Eggert
2017-10-07 8:49 ` Philipp Stephani
2017-10-08 6:04 ` Paul Eggert
2017-10-08 14:56 ` 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
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=CAArVCkRnbHdNx++6dbB-zUtmWieza3rKiQ-1t15P95jama5ZVg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=27871@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=phst@google.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 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).