From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Daniel Martín" <mardani29@yahoo.es>, emacs-devel@gnu.org
Subject: Re: A feature to go to last edit locations
Date: Mon, 13 Feb 2023 21:22:28 +0100 [thread overview]
Message-ID: <87mt5hl38s.fsf@web.de> (raw)
In-Reply-To: <e8fa1ade-61f4-b218-f055-13990d89bbbc@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 13/02/2023 21:24, Jean Louis wrote:
>> But Eli said something important, why go somewhere back randomly, but
>> better going where user marked it to need it.
>
> Because by the time the user knows they need to go back, they might
> have missed the opportunity to mark the place.
That’s why I like dumb-jump-back so much. dumb-jump / xref is a
cross-file command. C-M-g gets me to another file. C-M-p gets me back
where I jumped off.
A command that jumps into some other file like go-to-reference or
go-to-definition is a natural recording point. After jumping multiple
times I have a linked list of jump-locations to which I can jump back in
order. As a model that works much better than plain movement recording
in IntelliJ and also somewhat better than edit-locations. (though edit
locations could still be useful — but changing the buffer when going
back through edits can blur the sense which file I’m in at the moment)
If I switch buffers with switch-buffer, I know where I came from. If I
switch with a command, I am likely to quickly jump through multiple
files. So those jump-to-other-file commands are natural recording
points.
When I run xref, this is the point in a file where I’m likely to want to
return to.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2023-02-13 20:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1fsbakchr.fsf.ref@yahoo.es>
2023-02-12 17:41 ` A feature to go to last edit locations Daniel Martín
2023-02-12 17:52 ` Eli Zaretskii
2023-02-12 18:59 ` Daniel Martín
2023-02-12 19:26 ` Eli Zaretskii
2023-02-12 19:42 ` andrés ramírez
2023-02-12 22:19 ` Daniel Martín
2023-02-12 23:54 ` Dr. Arne Babenhauserheide
2023-02-13 7:50 ` Juri Linkov
2023-02-12 21:40 ` [External] : " Drew Adams
2023-02-13 20:28 ` Jean Louis
2023-02-12 18:07 ` Dmitry Gutov
2023-02-12 18:50 ` Daniel Martín
2023-02-12 18:52 ` Dmitry Gutov
2023-02-12 19:23 ` Daniel Martín
2023-02-13 19:28 ` Jean Louis
2023-02-13 19:24 ` Jean Louis
2023-02-13 19:41 ` Dmitry Gutov
2023-02-13 20:22 ` Dr. Arne Babenhauserheide [this message]
2023-02-13 20:56 ` Jean Louis
2023-02-14 3:25 ` Eli Zaretskii
2023-02-14 4:36 ` [External] : " Drew Adams
2023-02-14 4:56 ` Drew Adams
2023-02-14 5:53 ` Jean Louis
2023-02-14 16:24 ` Drew Adams
2023-02-15 5:45 ` Jean Louis
2023-02-15 16:34 ` Drew Adams
2023-02-16 8:17 ` On Bookmarks+ package Jean Louis
2023-02-16 17:38 ` [External] : " Drew Adams
2023-02-14 20:08 ` A feature to go to last edit locations Dmitry Gutov
2023-02-13 19:48 ` [External] : " Drew Adams
2023-02-13 20:28 ` Dr. Arne Babenhauserheide
2023-02-13 21:17 ` Drew Adams
2023-02-13 21:21 ` Jean Louis
2023-02-13 21:14 ` Jean Louis
2023-02-14 5:21 ` Drew Adams
2023-02-13 19:49 ` Michael Welsh Duggan
2023-02-13 21:35 ` Jean Louis
2023-02-13 23:14 ` Konstantin Kharlamov
2023-02-14 0:00 ` Ergus
2023-02-14 6:29 ` Dr. Arne Babenhauserheide
2023-02-15 0:00 ` Karthik Chikmagalur
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=87mt5hl38s.fsf@web.de \
--to=arne_bab@web.de \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
/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.