all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: 32629@debbugs.gnu.org
Subject: bug#32629: 26; `buffer-list-update-hook' doc string
Date: Thu, 3 Oct 2019 03:45:48 +0200	[thread overview]
Message-ID: <CADwFkmmwEV+T+j-c-uU6yQ02E2Li-m8NhOcO8O+uyqKAGJ3hWQ@mail.gmail.com> (raw)
In-Reply-To: <a3bf93ca-f6a1-4b72-9b2e-794993f34d05@default>

tags 32629 + wontfix
close 32629
thanks

Drew Adams <drew.adams@oracle.com> writes:

>> > > > The doc string should not list the functions that run the hook.
>> > >
>> > > Why not?
>> >
>> > Same reason we don't do that elsewhere (do we?).
>>
>> I see no reason for such a stringent consistency.
>
> No, there's no need for a stringent consistency.
> That's generally true.
>
>> Of course not.  But in this case doing that makes sense.
>> Because it tells one indirectly what changes are considered to "update
>> the buffer list".
>
> OK. Thanks for thinking about it.

The conclusion here was that the doc string is fine as it is.  Closing.

Best regards,
Stefan Kangas





  parent reply	other threads:[~2019-10-03  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 20:34 bug#32629: 26; `buffer-list-update-hook' doc string Drew Adams
2018-09-04  7:52 ` martin rudalics
2018-09-10 13:23 ` Eli Zaretskii
2019-10-03  1:45 ` Stefan Kangas [this message]
     [not found] <<a3bf93ca-f6a1-4b72-9b2e-794993f34d05@default>
     [not found] ` <<83y3c9o59k.fsf@gnu.org>
2018-09-10 13:51   ` Drew Adams
2018-09-10 14:18     ` Eli Zaretskii
2018-09-11  4:22       ` Richard Stallman
     [not found] <<<a3bf93ca-f6a1-4b72-9b2e-794993f34d05@default>
     [not found] ` <<<83y3c9o59k.fsf@gnu.org>
     [not found]   ` <<a906fe5b-ac26-4fe8-ad89-fe476c5b707a@default>
     [not found]     ` <<83pnxlo2ph.fsf@gnu.org>
2018-09-10 15:00       ` 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=CADwFkmmwEV+T+j-c-uU6yQ02E2Li-m8NhOcO8O+uyqKAGJ3hWQ@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=32629@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.