From: Michael Albinus <michael.albinus@gmx.de>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 26126@debbugs.gnu.org
Subject: bug#26126: 26.0.50; file-notify-rm-watch removes arbitrary watches
Date: Sat, 18 Mar 2017 09:30:42 +0100 [thread overview]
Message-ID: <87pohfkmvh.fsf@detlef> (raw)
In-Reply-To: <87tw6rssoi.fsf@luca> (Andreas Politz's message of "Fri, 17 Mar 2017 18:45:49 +0100")
Andreas Politz <politza@hochschule-trier.de> writes:
> What I would do, is box the internal descriptor in file-notify-add-watch,
> to make it unique to the caller and unbox it in file-notify-rm-watch and
> file-notify-valid-p.
Sounds OK to me. Do you want to do this only for inotify, or also for
the other backends?
> A different question is, whether file-notify-add-watch should behave
> like add-hook with regards to adding a function multiple times. I don't
> think it does at the moment, so I probably leave it as such (?).
I believe adding the *same* function twice for the same file/directory
doesn't make sense. Maybe we should document this in the Elisp manual,
and test it also in `file-notify-test01-add-watch'.
> -ap
Best regards, Michael.
next prev parent reply other threads:[~2017-03-18 8:30 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 14:14 bug#26126: 26.0.50; file-notify-rm-watch removes arbitrary watches Andreas Politz
2017-03-17 14:41 ` Michael Albinus
2017-03-17 14:59 ` Andreas Politz
2017-03-17 16:08 ` Michael Albinus
2017-03-17 17:45 ` Andreas Politz
2017-03-18 8:30 ` Michael Albinus [this message]
2017-03-18 13:32 ` Andreas Politz
2017-03-18 19:36 ` Michael Albinus
2017-03-18 20:37 ` Andreas Politz
2017-03-19 9:39 ` Michael Albinus
2017-03-19 11:14 ` Andreas Politz
2017-03-19 19:23 ` Michael Albinus
2017-03-20 20:39 ` Andreas Politz
2017-03-21 8:44 ` Michael Albinus
2017-03-21 15:37 ` Eli Zaretskii
2017-03-21 18:59 ` Andreas Politz
2017-03-22 13:23 ` Michael Albinus
2017-03-22 15:44 ` Eli Zaretskii
2017-03-22 16:01 ` Michael Albinus
2017-03-22 16:13 ` Eli Zaretskii
2017-03-22 16:23 ` Michael Albinus
2017-03-24 19:54 ` Andreas Politz
2017-03-25 12:50 ` Michael Albinus
2017-03-25 13:59 ` Andreas Politz
2017-03-25 14:08 ` Michael Albinus
2017-03-25 16:27 ` Andreas Politz
2017-03-25 16:37 ` Michael Albinus
2017-03-25 17:12 ` Andreas Politz
2017-03-25 18:36 ` Michael Albinus
2017-03-25 19:34 ` Andreas Politz
2017-03-26 7:08 ` Michael Albinus
2017-03-21 15:56 ` Andreas Politz
2017-03-22 12:56 ` Michael Albinus
2017-03-22 17:34 ` Andreas Politz
2017-03-22 18:49 ` Michael Albinus
2017-03-19 22:05 ` Andreas Politz
2017-03-21 13:05 ` Michael Albinus
2017-03-21 15:06 ` Andreas Politz
2017-03-21 15:54 ` Eli Zaretskii
2017-03-22 13:17 ` Michael Albinus
2017-03-22 17:43 ` Andreas Politz
2017-03-22 18:57 ` Michael Albinus
2017-03-22 20:02 ` Eli Zaretskii
2017-03-23 7:36 ` Michael Albinus
2017-03-23 15:22 ` Eli Zaretskii
2017-03-23 16:10 ` Michael Albinus
2017-03-22 19:40 ` Michael Albinus
2017-03-24 20:44 ` Andreas Politz
2017-03-25 6:35 ` Eli Zaretskii
2017-03-25 8:57 ` Andreas Politz
2017-03-25 14:17 ` Eli Zaretskii
2017-03-25 16:34 ` Andreas Politz
2017-03-25 14:04 ` Michael Albinus
2017-03-25 16:19 ` Andreas Politz
2017-03-25 17:09 ` Michael Albinus
2017-03-25 17:26 ` Andreas Politz
2017-03-25 18:18 ` Andreas Politz
2017-03-25 18:40 ` Michael Albinus
2017-03-25 16:21 ` Andreas Politz
2017-03-18 19:28 ` Andreas Politz
2017-03-18 19:49 ` Michael Albinus
2017-03-18 20:48 ` Andreas Politz
2017-03-30 18:15 ` Paul Eggert
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=87pohfkmvh.fsf@detlef \
--to=michael.albinus@gmx.de \
--cc=26126@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
/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.