all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Campbell Barton <ideasman42@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 36526@debbugs.gnu.org
Subject: bug#36526: 26.2; Open diff at current location (feature request with suggested code)
Date: Wed, 06 Nov 2019 22:15:19 +1100	[thread overview]
Message-ID: <d262115750bad51fd94d27fff594c5d52967649c.camel@gmail.com> (raw)
In-Reply-To: <875zk3t7ji.fsf@marxist.se>

On Sat, 2019-11-02 at 02:02 +0100, Stefan Kangas wrote:
> Stefan Kangas <stefan@marxist.se> writes:
> 
> >> Would someone be able to check the code and see if it's going in
> the
> >> right direction?
> >
> > OK, but see below.
> >
> >> >> This is a feature suggestion which I've written example code
> for
> >> >>
> >> >> `vc-root-diff` (or a new function), could jump to the closest
> line.
> >> >>
> >> >> This is useful since you move to the context of the current
> line.
> >
> > I'm not sure I understand what this code is supposed to do or how
> to
> > use it. Could you please give a recipe for how to test it?
> 
> Hi Campbell,
> 
> Just to follow up on this, could you please provide instructions for
> how to test your patch?
> 
> Thanks in advance.
> 
> Best regards,
> Stefan Kangas


Hi Stefan,

I've updated the Q&A to include the code and a utility function to use
it:

https://emacs.stackexchange.com/a/51439/2418

Try binding "vc-root-diff-fullscreen-and-jump-to-point" from a key in a
git repository with local edits, this will open the diff at (or close
to) the location being edited.

Included example video, showing how this is useful:

https://youtu.be/hbD8WrtWfEg






  reply	other threads:[~2019-11-06 11:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06 13:08 bug#36526: 26.2; Open diff at current location (feature request with suggested code) Campbell Barton
2019-09-13 11:59 ` Stefan Kangas
2019-09-13 19:29   ` Cambell Barton
2019-09-15 14:52     ` Stefan Kangas
2019-11-02  1:02       ` Stefan Kangas
2019-11-06 11:15         ` Campbell Barton [this message]
2019-12-27  8:18         ` Campbell Barton
2020-01-15  2:20           ` Stefan Kangas
2020-01-15 22:50             ` Dmitry Gutov
2020-08-09 19:37               ` Lars Ingebrigtsen
2020-08-09 21:08                 ` Dmitry Gutov
2020-08-10 10:43                   ` Lars Ingebrigtsen
2020-08-10 10:52                     ` Dmitry Gutov
2020-08-15 13:12           ` Lars Ingebrigtsen
2020-10-17  6:00 ` bug#36526: Previous work on this subject Herring, Davis via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-16 21:12   ` Juri Linkov
2020-11-16 21:29     ` Dmitry Gutov
2020-11-16 22:04       ` Juri Linkov
2020-11-17 21:02         ` Dmitry Gutov

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=d262115750bad51fd94d27fff594c5d52967649c.camel@gmail.com \
    --to=ideasman42@gmail.com \
    --cc=36526@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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.