From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 25357@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#25357: 25.1; Doc for `cursor-sensor-mode' (and modes generally)
Date: Fri, 06 Jan 2017 09:57:55 +0200 [thread overview]
Message-ID: <83lguod3i4.fsf@gnu.org> (raw)
In-Reply-To: <bcd0da83-e266-4c27-a678-d429f07d7d58@default> (message from Drew Adams on Thu, 5 Jan 2017 21:50:29 -0800 (PST))
> Date: Thu, 5 Jan 2017 21:50:29 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 25357@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
>
> > This is a subjective thing of course. I guess it seems obvious to me
> > that a command can be called as a function, and it's explained in
> > `(elisp) What Is a Function'. Adding cross references to that in every
> > place we talk about invoking some command is just clutter.
>
> Yes, of course. But I don't think it is obvious to some
> who read the _Emacs_ manual how they might turn on a major
> mode using Lisp.
People who write Lisp should read the ELisp manual, and expect issues
related to Lisp to be covered there. The user manual is not the right
place for that.
next prev parent reply other threads:[~2017-01-06 7:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<de93b37f-921f-4a6e-9f29-a357cf6b1c55@default>
[not found] ` <<83o9zmemfo.fsf@gnu.org>
2017-01-04 18:07 ` bug#25357: 25.1; Doc for `cursor-sensor-mode' (and modes generally) Drew Adams
2017-01-04 18:56 ` Noam Postavsky
2017-01-04 19:06 ` Drew Adams
2017-01-04 19:27 ` Noam Postavsky
2017-01-04 21:02 ` Drew Adams
2017-01-05 3:45 ` npostavs
2017-01-05 4:29 ` Drew Adams
2017-01-06 3:58 ` npostavs
2017-01-06 5:50 ` Drew Adams
2017-01-06 7:57 ` Eli Zaretskii [this message]
2017-01-08 17:15 ` npostavs
2017-01-05 15:28 ` Eli Zaretskii
[not found] ` <<83mvf6em4p.fsf@gnu.org>
2017-01-04 18:08 ` Drew Adams
[not found] <<9ad8b225-73da-4533-a676-b0f8e84e54ca@default>
[not found] ` <<CAM-tV--ymvk7wQ9VyBCSse1fQQqVxoH9htTnZdHmZGZYeH543A@mail.gmail.com>
[not found] ` <<a9c8bee8-1564-4bd3-81c4-2753a14e53a9@default>
[not found] ` <<CAM-tV-_+WRvc6+jZpHgywOx0XdgPUxdqyGc40cJ+R2s8ZyL=TQ@mail.gmail.com>
[not found] ` <<a2675f96-d075-408b-81e2-3a3045148b76@default>
[not found] ` <<878tqq5fw2.fsf@users.sourceforge.net>
[not found] ` <<678f8299-e6e8-4b08-a412-bf367194f6d7@default>
[not found] ` <<87a8b44z72.fsf@users.sourceforge.net>
[not found] ` <<bcd0da83-e266-4c27-a678-d429f07d7d58@default>
[not found] ` <<83lguod3i4.fsf@gnu.org>
2017-01-06 14:50 ` Drew Adams
2017-01-04 17:44 Drew Adams
2017-01-04 17:59 ` Eli Zaretskii
2017-01-04 18:05 ` Eli Zaretskii
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=83lguod3i4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25357@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=npostavs@users.sourceforge.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).