From: Christoph <cschol2112@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: ido.el doc fixes
Date: Mon, 28 Feb 2011 18:00:42 -0700 [thread overview]
Message-ID: <4D6C453A.4020201@gmail.com> (raw)
In-Reply-To: <83tyfnna7a.fsf@gnu.org>
On 2/28/2011 2:03 PM, Eli Zaretskii wrote:
> "C-x 4 a" knows how to concatenate several symbols. You just need to
> leave point after the closing parenthesis. Like so: first C-x 4 a
> inserts this:
>
> * ido.el (ido-everywhere):
> ^
> leaving point where I indicated. Then the next C-x 4 a adds another
> symbol:
>
> * ido.el (ido-everywhere, ido-mode):
> ^
> Now you are ready to type "Doc fixes.".
Nice. Thanks Eli. The manual didn't mention this specific behavior, so I
added a little section. See patch below.
I also added a reference to `add-log-full-name' in the changelog format
section. `add-log-mailing-address' was already referenced, but I was
trying to figure out how Change Log mode knows my name. This information
was missing.
I don't know what the etiquette is for adding examples like the
Changelog entry below. The example is made up (copied and modified from
another example in the format section).
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-02-28 23:21:39 +0000
@@ -1486,6 +1486,21 @@
non-@code{nil}, @kbd{C-x 4 a} adds to any existing item for the file
rather than starting a new item.
+Multiple changes of the same nature can be combined. First, leave the
+point after the closing parenthesis after the inital @kbd{C-x 4
+a}. Then, any subsequent @kbd{C-x 4 a} adds another symbol to the
+change.
+
+For example:
+@iftex
+@medbreak
+@end iftex
+@smallexample
+1993-05-25 Richard Stallman <rms@@gnu.org>
+
+ * man.el (man, man-follow): Doc fix.
+@end smallexample
+
@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 +1550,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 1:00 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 [this message]
2011-03-01 1:35 ` Glenn Morris
2011-03-01 2:36 ` Christoph Scholtes
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=4D6C453A.4020201@gmail.com \
--to=cschol2112@googlemail.com \
--cc=eliz@gnu.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).