From: Jambunathan K <kjambunathan@gmail.com>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tips for quick jumping back and forth
Date: Fri, 20 Jul 2012 18:45:57 +0530 [thread overview]
Message-ID: <81pq7qbmk2.fsf@gmail.com> (raw)
In-Reply-To: <jubkso$qiu$1@dough.gmane.org> (Kevin Rodgers's message of "Fri, 20 Jul 2012 07:02:58 -0600")
Kevin Rodgers <kevin.d.rodgers@gmail.com> writes:
> On 7/7/12 8:44 AM, notbob wrote:
>> On 2012-07-07, Francesco Mazzoli<f@mazzo.li> wrote:
>>>
>>> I use `C-<SPC> C-<SPC>' to set the mark, and `C-u C-<SPC>' to jump back. No
>>> registers involved.
>>
>> I occasionally do something stupid like hit the wrong keystroke, usually
>> C-e, which puts me at the end of the line. I was somewhat sure there
>> was an equally simple keystroked to return me to where I once was
>> where. NO!? If not, I'm bummed. I thought emacs was "powerful".
>> Seems a simple function. And by GOD, can't let vi outdo on this!
>
> buffer-undo-list can record the position before the inadvertant command
> so that C-x u would move you back, but the movement commands don't take
> advantage of that feature.
>
> C-h v buffer-undo-list:
> ...
> An entry of the form POSITION indicates that point was at the buffer
> location given by the integer. Undoing an entry of this form places
> point at POSITION.
When one is browsing a source repository - the context for the OP, IIRC
- one is most likely visiting unmodified files. So a question of undo
does arise.
I think if one wants to visit the point where changes were introduced,
one can use
C-h f highlight-changes-mode
and use the navigation command provided by that mode.
Personally - I mostly work with version controlled files - I use a
combination of
M-x diff-buffer-with-file
and use hunks in diff buffer to provide me a map of places that are of
interest to me.
--
next prev parent reply other threads:[~2012-07-20 13:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 5:43 Tips for quick jumping back and forth C K Kashyap
2012-07-07 6:19 ` Jambunathan K
2012-07-11 9:57 ` Philipp Haselwarter
2012-07-07 6:45 ` Andreas Röhler
2012-07-07 13:56 ` Francesco Mazzoli
[not found] ` <mailman.4249.1341669396.855.help-gnu-emacs@gnu.org>
2012-07-07 14:44 ` notbob
2012-07-20 13:02 ` Kevin Rodgers
2012-07-20 13:15 ` Jambunathan K [this message]
2012-07-09 2:59 ` Le Wang
[not found] <mailman.4232.1341639863.855.help-gnu-emacs@gnu.org>
2012-07-07 8:02 ` José A. Romero L.
2012-07-07 10:48 ` Xah Lee
2012-07-08 4:25 ` B. T. Raven
2012-07-12 0:04 ` Edward at Work
-- strict thread matches above, loose matches on Subject: below --
2012-07-07 13:39 Dmitry Gutov
2012-07-07 15:27 Dmitry Gutov
2012-07-08 3:28 ` C K Kashyap
2012-07-08 3:31 ` suvayu ali
2012-07-08 3:35 ` C K Kashyap
2012-07-09 2:01 ` Ken Goldman
[not found] ` <mailman.4284.1341718295.855.help-gnu-emacs@gnu.org>
2012-07-08 3:47 ` rusi
[not found] ` <mailman.4283.1341718129.855.help-gnu-emacs@gnu.org>
2012-07-08 17:28 ` Xah Lee
2012-07-11 13:36 Dmitry Gutov
2012-07-11 14:40 ` Eric Abrahamsen
2012-07-11 15:02 ` Drew Adams
2012-07-11 17:31 ` Dmitry Gutov
2012-07-11 18:33 ` Drew Adams
2012-07-11 21:03 ` Dmitry Gutov
2012-07-11 23:44 ` Drew Adams
2012-07-12 21:30 ` 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
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=81pq7qbmk2.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=kevin.d.rodgers@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.
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).