From: Christoph Scholtes <cschol2112@googlemail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: ido.el doc fixes
Date: Mon, 28 Feb 2011 19:36:17 -0700 [thread overview]
Message-ID: <86lj0za7oe.fsf@gmail.com> (raw)
In-Reply-To: <55y64z8vx6.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 28 Feb 2011 20:35:33 -0500")
Glenn Morris <rgm@gnu.org> writes:
> I don't think that is correct. You can move point wherever you like. So
> long as you have not entered any text for an entry, the next entry from
> the same file will merge with it. (If add-log-always-start-new-record is
> nil.)
That looks correct. I modified the patch as below.
> I don't think an example ChangeLog entry is needed for this behaviour.
> It's good to try to keep the manual from expanding too much.
OK. I think with the above corrections it might be clear enough without
example.
> It's better to use the active voice (see tips.texi). Eg "You can combine
> multiple changes of the same nature".
Thanks.
Christoph
=== modified file 'doc/emacs/ChangeLog'
--- doc/emacs/ChangeLog 2011-02-28 01:07:29 +0000
+++ doc/emacs/ChangeLog 2011-02-28 23:17:26 +0000
@@ -1,3 +1,10 @@
+2011-02-28 Christoph Scholtes <cschol2112@googlemail.com>
+
+ * maintaining.texi (Format of ChangeLog): Add reference to
+ add-log-full-name.
+ (Change Log Commands): Add documentation and example for combining
+ multiple symbols in one change.
+
2011-02-28 Eli Zaretskii <eliz@gnu.org>
* search.texi (Regexp Search): Move index entries about regexps to the
=== modified file 'doc/emacs/maintaining.texi'
--- doc/emacs/maintaining.texi 2011-02-05 22:30:14 +0000
+++ doc/emacs/maintaining.texi 2011-03-01 02:28:44 +0000
@@ -1486,6 +1486,10 @@
non-@code{nil}, @kbd{C-x 4 a} adds to any existing item for the file
rather than starting a new item.
+You can combine multiple changes of the same nature. If you don't
+enter any text after the initial @kbd{C-x 4 a}, any subsequent
+@kbd{C-x 4 a} adds another symbol to the change.
+
@vindex add-log-always-start-new-record
If @code{add-log-always-start-new-record} is non-@code{nil},
@kbd{C-x 4 a} always makes a new entry, even if the last entry
@@ -1535,13 +1539,14 @@
@node Format of ChangeLog
@subsection Format of ChangeLog
- A change log entry starts with a header line that contains the current
-date, your name, and your email address (taken from the variable
-@code{add-log-mailing-address}). Aside from these header lines, every
-line in the change log starts with a space or a tab. The bulk of the
-entry consists of @dfn{items}, each of which starts with a line starting
-with whitespace and a star. Here are two entries, both dated in May
-1993, with two items and one item respectively.
+ A change log entry starts with a header line that contains the
+current date, your name (taken from the variable
+@code{add-log-full-name}), and your email address (taken from the
+variable @code{add-log-mailing-address}). Aside from these header
+lines, every line in the change log starts with a space or a tab. The
+bulk of the entry consists of @dfn{items}, each of which starts with a
+line starting with whitespace and a star. Here are two entries, both
+dated in May 1993, with two items and one item respectively.
@iftex
@medbreak
next prev parent reply other threads:[~2011-03-01 2:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 19:06 ido.el doc fixes Christoph
2011-02-28 19:27 ` Eli Zaretskii
2011-02-28 20:01 ` Glenn Morris
2011-02-28 20:44 ` Christoph Scholtes
2011-02-28 21:03 ` Eli Zaretskii
2011-03-01 1:00 ` Christoph
2011-03-01 1:35 ` Glenn Morris
2011-03-01 2:36 ` Christoph Scholtes [this message]
2011-03-01 4:04 ` Eli Zaretskii
2011-03-01 4:23 ` Christoph Scholtes
2011-02-28 20:42 ` Christoph Scholtes
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=86lj0za7oe.fsf@gmail.com \
--to=cschol2112@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).