unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: 18128@debbugs.gnu.org
Subject: bug#18128: Diff-mode doesn't refine hunks automatically
Date: Mon, 28 Jul 2014 17:44:36 +0300	[thread overview]
Message-ID: <83bns9h7aj.fsf@gnu.org> (raw)
In-Reply-To: <CAG7BpaqZXVLE-rbs6QupqoDKANN6tYrAS3YzdqJoBVHkywE+8A@mail.gmail.com>

> Date: Mon, 28 Jul 2014 16:39:56 +0200
> From: Paul Pogonyshev <pogonyshev@gmail.com>
> Cc: 18128@debbugs.gnu.org
> 
> It is enough. Then please add a reference to it to documentation of
> diff-refine-hunk, I wasn't even aware of that mode.

It is currently mentioned there as follows:

   `M-n'
	Move to the next hunk-start (`diff-hunk-next').

	This command has a side effect: it "refines" the hunk you move to,
	highlighting its changes with better granularity.  To disable this
	feature, type `M-x diff-auto-refine-mode' to toggle off the minor
	mode Diff Auto-Refine mode.  To disable Diff Auto Refine mode by
	default, add this to your init file (*note Hooks::):

	     (add-hook 'diff-mode-hook
		       (lambda () (diff-auto-refine-mode -1)))

If you think this is not enough, please tell what else would you like
to see there about this minor mode.





  reply	other threads:[~2014-07-28 14:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 13:59 bug#18128: Diff-mode doesn't refine hunks automatically Paul Pogonyshev
2014-07-28 14:28 ` Eli Zaretskii
2014-07-28 14:39   ` Paul Pogonyshev
2014-07-28 14:44     ` Eli Zaretskii [this message]
2014-07-28 14:49       ` Paul Pogonyshev
2014-07-28 14:45     ` Paul Pogonyshev
2014-07-28 23:28 ` Stefan Monnier
2016-01-17  6:22 ` bug#18128: Should be done as part of the font-lock Hong Xu
2016-11-04  7:54   ` Hong Xu
2016-11-05  2:10 ` bug#18128: Diff-mode doesn't refine hunks automatically npostavs

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=83bns9h7aj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18128@debbugs.gnu.org \
    --cc=pogonyshev@gmail.com \
    /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).