all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: emacs-devel <emacs-devel@gnu.org>,
	Michael Albinus <michael.albinus@gmx.de>
Subject: Re: [PATCH] elisp manual patch: add to file notification documentation
Date: Tue, 13 Dec 2022 10:20:46 -0800	[thread overview]
Message-ID: <CADwFkmkg-LTfMiX1=Gyhw_yCsJNbcMoOr7OYAaFgMVT_wRk60Q@mail.gmail.com> (raw)
In-Reply-To: <875yefi5mq.fsf@rabkins.net>

Yoni Rabkin <yoni@rabkins.net> writes:

>> If this is supposed to be user-facing, shouldn't it be renamed to
>> `file-notify-library'?
>
> Is the content of the elisp manual supposed to be user-facing? I guess
> it depends on how you all define that term.
>
> When I wrote "user" above, I was referring to the "user" of the elisp
> manual, who is a person writing elisp.

Yes, I also include ELisp developers when I say "user-facing" here.

This is in contrast to implementation details, that ELisp developers
must not rely upon.  The convention is to mark the names of such
implementation details either with two dashes "--" (new style) or
"-internal" (old style).



  reply	other threads:[~2022-12-13 18:20 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
2022-12-13 19:05           ` Michael Albinus
2022-12-13 17:18   ` Yoni Rabkin
2022-12-13 18:20     ` Stefan Kangas [this message]
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='CADwFkmkg-LTfMiX1=Gyhw_yCsJNbcMoOr7OYAaFgMVT_wRk60Q@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 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.