From: Stefan Kangas <stefankangas@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>, Yoni Rabkin <yoni@rabkins.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] elisp manual patch: add to file notification documentation
Date: Tue, 13 Dec 2022 10:52:27 -0800 [thread overview]
Message-ID: <CADwFkmnFs090KDwtuas7Np+i93WYg1yUWo_=Anb68tue2YmXGA@mail.gmail.com> (raw)
In-Reply-To: <87y1rbrwel.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
> It's not that simple. Emacs might be compiled with file notification,
> but it isn't possible for remote files. Emacs might be compiled without
> file notification, but it is still possible for remote files.
>
> And even if it is possible for local or remote files, it might not work
> on NFS mounted file systems.
>
> The value of file-notify--library is a vague approximation for being
> able to use file notifications. That's the reason for being an internal
> constant only.
>
> Calling file-notify-add-watch gives you more precise results.
Would it make sense to add something like the above to the docstring of
`file-notify--library'?
next prev parent reply other threads:[~2022-12-13 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 3:05 [PATCH] elisp manual patch: add to file notification documentation Yoni Rabkin
2022-12-13 3:25 ` Stefan Kangas
2022-12-13 8:21 ` Michael Albinus
2022-12-13 17:34 ` Yoni Rabkin
2022-12-13 17:46 ` Eli Zaretskii
2022-12-13 18:23 ` Yoni Rabkin
2022-12-13 20:07 ` Eli Zaretskii
2022-12-13 18:06 ` Stefan Monnier
2022-12-13 18:28 ` Michael Albinus
2022-12-13 18:52 ` Stefan Kangas [this message]
2022-12-13 19:05 ` Michael Albinus
2022-12-13 17:18 ` Yoni Rabkin
2022-12-13 18:20 ` Stefan Kangas
2022-12-13 18:31 ` [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='CADwFkmnFs090KDwtuas7Np+i93WYg1yUWo_=Anb68tue2YmXGA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=yoni@rabkins.net \
/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).