From: "T.V Raman" <raman@google.com>
To: larsi@gnus.org
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: Feature Request: Help: Display Relevant Bits First?
Date: Sat, 2 Apr 2022 10:13:53 -0700 [thread overview]
Message-ID: <25160.33873.989817.895858@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <87czhzlhbz.fsf@gnus.org>
Awesome, Thanks!
And speaking of the boiler-plate, I have always found the sense in
which -1 vs 1 is used in all the minor-mode toggle functions, where
nil actually turns it on --that usage is too late to change. But
could we perhaps alleviate the pain by adding two special values 'on
and 'off so that
(font-lock-mode 'on) turns it on and (font-lock-mode 'offf) turns it
off?
Lars Ingebrigtsen writes:
> "T.V Raman" <raman@google.com> writes:
>
> > At present, if you do describe-function on any command that toggles a
> > mode, you get a lot of common boiler-plate, with the salient bits
> > about that particular function at the end -- could we reverse this?
>
> I agree completely, especially as the boilerplate has expanded over the
> years. I've now moved it to the end of the doc strings in Emacs 29.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2022-04-02 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 20:22 Feature Request: Help: Display Relevant Bits First? T.V Raman
2022-03-31 20:50 ` [External] : " Drew Adams
2022-03-31 21:01 ` T.V Raman
2022-04-02 13:56 ` Lars Ingebrigtsen
2022-04-02 14:36 ` Basil L. Contovounesios
2022-04-02 14:53 ` Lars Ingebrigtsen
2022-04-02 17:13 ` T.V Raman [this message]
2022-04-03 11:54 ` Lars Ingebrigtsen
2022-04-03 0:37 ` Po Lu
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=25160.33873.989817.895858@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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.