unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 34073@debbugs.gnu.org, Piotr Kaznowski <piotr.kaznowski@gmail.com>
Subject: bug#34073: 26.1; Missing documentation for minor mode hook behavior
Date: Wed, 10 Jul 2019 00:57:53 +0200	[thread overview]
Message-ID: <m3o9223jf2.fsf@gnus.org> (raw)
In-Reply-To: <877e8q3k0n.fsf@gmail.com> (Noam Postavsky's message of "Tue, 09 Jul 2019 18:44:56 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

> I didn't mean the docstring of define-minor-mode, I meant the docstring
> of the mode it defines.

Yes, that makes sense.  I just had a look at a random one of these:

---

auto-image-file-mode is an autoloaded interactive Lisp function in
‘image-file.el’.

(auto-image-file-mode &optional ARG)

  Probably introduced at or before Emacs version 21.1.

Toggle visiting of image files as images (Auto Image File mode).

If called interactively, enable Auto-Image-File mode if ARG is positive, and
disable it if ARG is zero or negative.  If called from Lisp,
also enable the mode if ARG is omitted or nil, and toggle it
if ARG is ‘toggle’; disable the mode otherwise.

An image file is one whose name has an extension in
‘image-file-name-extensions’, or matches a regexp in
‘image-file-name-regexps’.

---

It doesn't mention the hook at all...  which I guess it could do?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-07-09 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  9:13 bug#34073: 26.1; Missing documentation for minor mode hook behavior Piotr Kaznowski
2019-07-09 22:20 ` Lars Ingebrigtsen
2019-07-09 22:35   ` Noam Postavsky
2019-07-09 22:43     ` Lars Ingebrigtsen
2019-07-09 22:44       ` Noam Postavsky
2019-07-09 22:57         ` Lars Ingebrigtsen [this message]
2020-08-21 15:15           ` Lars Ingebrigtsen

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=m3o9223jf2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=34073@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=piotr.kaznowski@gmail.com \
    /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).