From: Drew Adams <drew.adams@oracle.com>
To: Yoni Rabkin <yoni@rabkins.net>, Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>,
Michael Albinus <michael.albinus@gmx.de>
Subject: RE: [External] : Re: [PATCH] elisp manual patch: add to file notification documentation
Date: Tue, 13 Dec 2022 18:31:52 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488831A8F12FC8027848D06F3E39@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <875yefi5mq.fsf@rabkins.net>
> >> The following elisp manual documentation patch explains
> >> to the user how to...
^^^^
user -> reader
Reader of the manual.
> > If this is supposed to be user-facing, shouldn't it be...
>
> 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.
And yes, users, including "end" users (at any level of
familiarity), can also use Lisp.
If you want to talk about both users of some code and
writers of some code, do that. But yes, a user of `cons'
or `format' is a Lisp user, and in the case of Emacs
that's an Elisp user, which implies an Emacs user.
prev parent reply other threads:[~2022-12-13 18:31 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
2022-12-13 18:31 ` Drew Adams [this message]
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=SJ0PR10MB5488831A8F12FC8027848D06F3E39@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@gmail.com \
--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.