From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] misc.texi, files.texi
Date: Sat, 06 May 2006 10:24:42 -0400 [thread overview]
Message-ID: <E1FcNi6-0004Wv-7t@fencepost.gnu.org> (raw)
In-Reply-To: <17498.54974.330326.47241@farnswood.snap.net.nz> (message from Nick Roberts on Fri, 5 May 2006 16:38:22 +1200)
I also see you removed:
You can also use @kbd{C-x `} to visit successive changed locations
in the two source files, as in Compilation mode (@pxref{Compilation
Mode}.)
I removed this because it is a property of Diff mode rather than those
specific commands; but I overlooked that this wasn't documented in the
Diff Mode node either. I will make this change:
*** files.texi 05 May 2006 16:57:47 -0400 1.142
--- files.texi 05 May 2006 20:19:10 -0400
***************
*** 2225,2232 ****
One general feature of Diff mode is that manual edits to the patch
automatically correct line numbers, including those in the hunk
header, so that you can actually apply the edited patch. Diff mode
! also provides the following commands to navigate, manipulate and apply
! parts of patches:
@table @kbd
@item M-n
--- 2225,2234 ----
One general feature of Diff mode is that manual edits to the patch
automatically correct line numbers, including those in the hunk
header, so that you can actually apply the edited patch. Diff mode
! treats each hunk location as an ``error message'', so that you can use
! commands such as @kbd{C-x '} to visit the corresponding source
! locations. It also provides the following commands to navigate,
! manipulate and apply parts of patches:
@table @kbd
@item M-n
next prev parent reply other threads:[~2006-05-06 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 23:24 [PATCH] misc.texi, files.texi Nick Roberts
2006-05-04 14:17 ` Richard Stallman
2006-05-04 21:37 ` Nick Roberts
2006-05-05 4:38 ` Nick Roberts
2006-05-06 14:24 ` Richard Stallman [this message]
2006-05-07 1:32 ` Nick Roberts
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=E1FcNi6-0004Wv-7t@fencepost.gnu.org \
--to=rms@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 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.