From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 41727@debbugs.gnu.org
Subject: bug#41727: 26.3; Doc of `define-minor-mode' and minor-mode commands
Date: Mon, 8 Jun 2020 10:38:43 -0700 (PDT) [thread overview]
Message-ID: <9a2f8463-42a6-4f0c-82d9-de15192fffe2@default> (raw)
In-Reply-To: <87mu5dbhqv.fsf@web.de>
> > That's misleading enough to make me wonder whether,
> > in that case, it might be better to say nothing at
> > all about the call-from-Lisp case, forcing Lisp
> > users to consult the code.
>
> How about leaving only cases like ARG -> '- undocumented?
>
> When called from Lisp, the mode command toggles the mode if the argument
> is `toggle', disables the mode if the argument is a non-positive
> integer, and enables the mode if the argument is a positive integer or
> omitted or nil.
That's what we say now, and the reason I filed the bug.
> Good enough for daily business. ...
Not good enough for me. ;-)
Consider a case where some command A invokes a minor-mode
command B, to turn B on or off for some purpose/extent.
Consider the case where A's prefix arg is passed to B, to
do that.
The programmer writing the Lisp code to define A should
know that s?he can just pass the raw prefix arg. The
resulting code will be simpler, easier to read, etc.
I see no reason at all why we wouldn't provide an accurate
(complete) description of what ARG is for Lisp use.
What do we gain by not doing this right?
next prev parent reply other threads:[~2020-06-08 17:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 20:39 bug#41727: 26.3; Doc of `define-minor-mode' and minor-mode commands Drew Adams
2020-06-06 0:01 ` Drew Adams
2020-06-07 10:04 ` Michael Heerdegen
2020-06-07 16:06 ` Drew Adams
2020-06-07 16:19 ` Michael Heerdegen
2020-06-07 16:30 ` Drew Adams
2020-06-06 6:13 ` Eli Zaretskii
2020-06-06 16:45 ` Drew Adams
2020-06-06 18:56 ` Eli Zaretskii
2020-06-07 10:08 ` Michael Heerdegen
2020-06-07 14:31 ` Eli Zaretskii
2020-06-07 14:45 ` Michael Heerdegen
2020-06-07 16:08 ` Drew Adams
[not found] ` <<87wo4jb33s.fsf@web.de>
[not found] ` <<83y2oz6j6x.fsf@gnu.org>
2020-06-07 16:16 ` Drew Adams
2020-06-08 17:16 ` Michael Heerdegen
2020-06-08 17:38 ` Drew Adams [this message]
2020-06-09 7:58 ` Michael Heerdegen
2020-06-09 14:39 ` Eli Zaretskii
2020-06-09 15:21 ` Michael Heerdegen
2020-06-09 15:40 ` Drew Adams
[not found] ` <<87h7vkbrh3.fsf@web.de>
[not found] ` <<835zc0717e.fsf@gnu.org>
2020-06-09 15:51 ` Drew Adams
2021-09-25 15:41 ` Stefan Kangas
2021-09-25 16:58 ` bug#41727: [External] : " Drew Adams
2021-09-25 17:18 ` Eli Zaretskii
[not found] <<963d4189-17dc-4f4e-9993-0335fa271e50@default>
[not found] ` <<83k10kafha.fsf@gnu.org>
[not found] ` <<9d7f8447-1c0b-46db-a40c-c1ed2a398c46@default>
[not found] ` <<838sh081lt.fsf@gnu.org>
2020-06-06 20:39 ` 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=9a2f8463-42a6-4f0c-82d9-de15192fffe2@default \
--to=drew.adams@oracle.com \
--cc=41727@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.