From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: new buffer display action: display-buffer-reuse-frame
Date: Thu, 30 Jul 2015 10:24:45 -0500 [thread overview]
Message-ID: <86r3np7jnm.fsf@stephe-leake.org> (raw)
In-Reply-To: <55B9BD99.6010909@gmx.at> (martin rudalics's message of "Thu, 30 Jul 2015 08:00:57 +0200")
martin rudalics <rudalics@gmx.at> writes:
> * lisp/window.el (display-buffer-use-some-frame): improve doc string
>
> * doc/lispref/windows.texi (Display Action Functions): add
> display-buffer-use-some-frame
>
> * etc/NEWS: mention display-buffer-use-some-frame
>
> Please note that ChangeLog entries should be unindented and "complete
> sentences starting with a capital and ending with a period". So
>
> * lisp/window.el (display-buffer-use-some-frame): Improve doc string.
>
> would be the preferred format.
Right. Sorry. Eli had the same comment on earlier commits.
I don't pay attention to "complete sentences" in other projects, and I
haven't figured out how to change that habit for this one.
I'll have to write another commit check hook to do that!
I guess by "unindented" you are refering to the second ine in the
windows.texi entry? So that should be:
* doc/lispref/windows.texi (Display Action Functions): Add
display-buffer-use-some-frame.
Ok. I think indenting makes it easier to read. But the examples in
CONTRIBUTE and
http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs
clearly show "unindented", and standards are important. One more item
for the commit check.
--
-- Stephe
next prev parent reply other threads:[~2015-07-30 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 19:48 new buffer display action: display-buffer-reuse-frame Stephen Leake
2015-07-27 16:03 ` martin rudalics
2015-07-30 0:24 ` Stephen Leake
2015-07-30 6:00 ` martin rudalics
2015-07-30 15:24 ` Stephen Leake [this message]
2015-07-30 16:41 ` 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=86r3np7jnm.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@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).