From: Drew Adams <drew.adams@oracle.com>
To: John Shahid <jvshahid@gmail.com>, Glenn Morris <rgm@gnu.org>
Cc: 10754@debbugs.gnu.org
Subject: bug#10754: define-minor-mode and doc of derived mode
Date: Thu, 7 Jun 2018 13:46:40 +0000 (UTC) [thread overview]
Message-ID: <0edf0759-1044-4c6f-b70a-addebc9078f8@default> (raw)
In-Reply-To: <87po12g7x4.fsf@gmail.com>
> There are over 200 modes that use define-minor-mode. I'm not sure how
> many of those docstring have argument documentation. For some of those
> modes documenting arg doesn't make much sense.
>
> For those who have an arg document, does it make sense to do them all in
> a single patch ? Also, is there any consensus on using %{arg} ? I have a
> local patch with linum-mode changed, which I can send for review.
Is this related to bug #29497?
next prev parent reply other threads:[~2018-06-07 13:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 18:02 bug#10754: define-minor-mode and doc of derived mode Glenn Morris
2012-02-07 20:27 ` Glenn Morris
2018-06-07 11:20 ` John Shahid
2018-06-07 13:46 ` Drew Adams [this message]
2018-06-08 2:25 ` John Shahid
2018-06-08 21:45 ` John Shahid
2018-06-16 10:52 ` Eli Zaretskii
2018-06-16 17:23 ` Stefan Monnier
2018-06-17 15:55 ` John Shahid
2018-06-17 18:31 ` Stefan Monnier
2018-06-17 19:45 ` John Shahid
2018-06-17 21:00 ` Stefan Monnier
2018-06-17 23:19 ` John Shahid
2018-06-18 13:47 ` Stefan Monnier
2018-06-20 19:33 ` John Shahid
2018-06-20 21:55 ` Stefan Monnier
2018-06-27 21:26 ` John Shahid
2018-06-27 21:31 ` John Shahid
2018-06-29 1:02 ` Stefan Monnier
2018-06-29 13:45 ` John Shahid
2018-06-29 13:55 ` Stefan Monnier
2018-06-29 14:52 ` John Shahid
2018-06-29 15:12 ` Noam Postavsky
2018-06-29 15:48 ` John Shahid
2018-06-30 7:55 ` Eli Zaretskii
2018-06-30 20:44 ` John Shahid
2018-07-02 3:36 ` Stefan Monnier
2018-06-30 7:56 ` 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=0edf0759-1044-4c6f-b70a-addebc9078f8@default \
--to=drew.adams@oracle.com \
--cc=10754@debbugs.gnu.org \
--cc=jvshahid@gmail.com \
--cc=rgm@gnu.org \
/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).