unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21432@debbugs.gnu.org, tsdh@gnu.org
Subject: bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted
Date: Mon, 14 Sep 2015 09:37:44 +0200	[thread overview]
Message-ID: <87zj0psb7b.fsf@gmx.de> (raw)
In-Reply-To: <83mvwpa1xb.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Sep 2015 10:35:28 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I find the way inotify.c and gfilenotify.c report errors suboptimal:
> they don't report the errno value and the related data, so the error
> messages tell less than they could.  I went the way similar to
> report_file_error instead.  Maybe the other back-ends should follow
> suit.

Will do.

Best regards, Michael.





  reply	other threads:[~2015-09-14  7:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  6:36 bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted Tassilo Horn
2015-09-08  7:47 ` Michael Albinus
2015-09-08  8:11   ` Tassilo Horn
2015-09-08 15:51   ` Eli Zaretskii
2015-09-08 15:49 ` Eli Zaretskii
2015-09-08 16:01   ` Michael Albinus
2015-09-12 10:18     ` Michael Albinus
2015-09-12 15:11       ` Eli Zaretskii
2015-09-12 18:09         ` Michael Albinus
2015-09-13 19:23           ` Michael Albinus
2015-09-14  6:08             ` Tassilo Horn
2015-09-14  7:08               ` Eli Zaretskii
2015-09-14  7:40                 ` Tassilo Horn
2015-09-14  7:56                   ` Tassilo Horn
2015-09-14 13:22                     ` Eli Zaretskii
2015-09-14 20:23                       ` Michael Albinus
2015-09-15  7:38                         ` Eli Zaretskii
2015-09-15  8:00                           ` Michael Albinus
2015-09-15  8:22                             ` Eli Zaretskii
2015-09-15 11:54                               ` Michael Albinus
2015-09-15 12:51                                 ` Eli Zaretskii
2015-09-15 12:56                                   ` Michael Albinus
2015-09-16 14:45                                   ` Michael Albinus
2015-09-16 17:08                                     ` Eli Zaretskii
2015-09-16 17:26                                       ` Michael Albinus
2015-09-16 17:55                                         ` Eli Zaretskii
2015-09-16 18:28                                           ` Michael Albinus
2015-09-15  5:53                       ` Tassilo Horn
2015-09-14  7:35         ` Eli Zaretskii
2015-09-14  7:37           ` Michael Albinus [this message]
2015-09-15 13:02           ` Michael Albinus
2015-09-15 13:56             ` Eli Zaretskii
2015-09-16 13:54               ` Michael Albinus
2015-09-20 17:23 ` Michael Albinus
2015-09-20 19:19   ` Eli Zaretskii
2015-09-21 13:40     ` Michael Albinus

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=87zj0psb7b.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=21432@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=tsdh@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).