From: Yoni Rabkin <yoni@rabkins.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH] elisp manual patch: add to file notification documentation
Date: Tue, 13 Dec 2022 13:23:20 -0500 [thread overview]
Message-ID: <87o7s7go2v.fsf@rabkins.net> (raw)
In-Reply-To: <83pmcnnqlz.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Dec 2022 19:46:48 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Yoni Rabkin <yoni@rabkins.net>
>> Cc: Stefan Kangas <stefankangas@gmail.com>, emacs-devel <emacs-devel@gnu.org>
>> Date: Tue, 13 Dec 2022 12:34:25 -0500
>>
>> I think that there is value in documenting a way for us to check if the
>> emacs we are running supports file notification
>
> You should be able to do that easily by looking at the value of the
> variable system-configuration-features.
The documentation for `system-configuration-features' says:
"This is mainly intended for diagnostic purposes in bug reports. Don't
rely on it for testing whether a feature you want to use is available."
--
"Cut your own wood and it will warm you twice"
next prev parent reply other threads:[~2022-12-13 18:23 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7s7go2v.fsf@rabkins.net \
--to=yoni@rabkins.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@gmail.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 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.