unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "Herring, Davis" <herring@lanl.gov>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: [PATCH] Showing the relevant part of a diff
Date: Sat, 16 Jul 2016 12:28:33 +0300	[thread overview]
Message-ID: <e622405e-4e63-22be-135c-b8b3490f24ac@yandex.ru> (raw)
In-Reply-To: <B393F5AD12955C48A84FFB08032CD04F6C56DCC3@ECS-EXG-P-MB01.win.lanl.gov>

On 07/16/2016 05:14 AM, Herring, Davis wrote:

> 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.

That's quite a lot of patches you got there. It think they should be 
considered separately.

In case you were wondering, though, diff-hl (available in ELPA) offers 
the "go to the relevant part of the diff" feature via remapping the 
vc-diff command.




  reply	other threads:[~2016-07-16  9:28 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
2016-07-16  9:28             ` Dmitry Gutov [this message]
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=e622405e-4e63-22be-135c-b8b3490f24ac@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=herring@lanl.gov \
    /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).