From: "Herring, Davis" <herring@lanl.gov>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: RE: [PATCH] Showing the relevant part of a diff
Date: Sat, 16 Jul 2016 02:14:11 +0000 [thread overview]
Message-ID: <B393F5AD12955C48A84FFB08032CD04F6C56DCC3@ECS-EXG-P-MB01.win.lanl.gov> (raw)
In-Reply-To: <57895355.4010803@lanl.gov>
> "soon" has finally arrived. There are now several "preparatory"
> patches. The first is just an update of the cleanup from before
> (February), but then there's [...]
My subtlety will be by undoing. For those who haven't been waiting 5 months with bated breath, this is what "February" means: http://lists.gnu.org/archive/html/emacs-devel/2016-02/msg01066.html and following.
In short, in several circumstances where the text of a buffer is the "new" side of a diff (C-x v =, C-x v D, M-x diff-backup, and M-x diff-buffer-with-file; we could add M-x diff itself), this code displays the diff with point set to the place in the diff that corresponds to point in the buffer. This is either a context line, an added/changed line, or the boundary between two hunks (or before the first, or after the last) in case point is too far from a change to be included in the context.
C-x v = was the original inspiration: this changes it from "What have I changed in this file?" to "What have I changed _here_?". I frequently find myself wanting to ask the latter question, and searching through the diff for my current position is tedious. If the answer is "nothing, but there are changes elsewhere in the file", putting point on a hunk boundary shows what the nearest changes are.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2016-07-16 2:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 5:43 [PATCH] Showing the relevant part of a diff Herring, Davis
2016-02-19 5:49 ` Lars Ingebrigtsen
2016-02-19 8:47 ` Eli Zaretskii
2016-02-20 20:20 ` Herring, Davis
2016-02-20 20:39 ` Eli Zaretskii
2016-02-20 22:49 ` Herring, Davis
2016-07-15 21:19 ` Davis Herring
2016-07-16 2:14 ` Herring, Davis [this message]
2016-07-16 9:28 ` Dmitry Gutov
2016-07-18 14:15 ` Ted Zlatanov
2016-07-18 23:20 ` Dmitry Gutov
2016-07-19 14:12 ` Ted Zlatanov
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=B393F5AD12955C48A84FFB08032CD04F6C56DCC3@ECS-EXG-P-MB01.win.lanl.gov \
--to=herring@lanl.gov \
--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).