From: Drew Adams <drew.adams@oracle.com>
To: Jean Louis <bugs@gnu.support>, Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: RE: Jumping from one position to other position
Date: Sat, 5 Dec 2020 13:29:24 -0800 (PST) [thread overview]
Message-ID: <2f54a399-a632-4000-97f4-d0775165de9b@default> (raw)
In-Reply-To: <<courier.000000005FCBD00B.00007ECE@static.rcdrun.com>>
> All the time I have to jump from one function to other function. What
> I used so far is C-SPC C-SPC to leave mark at the point and deactivate
> it. Then I can jump to other places and come back with C-u SPC.
>
> What I would like is to keep somehow automatically source position as
> new mark, when I do C-u SPC at position X that I jump to position Y,
> and then from Y with C-u SPC again back to X.
>
> But Emacs does not work this way.
>
> If anybody have better way of jumping from one place A to place B and
> returning again to place A, and again to place B, let me know.
(`C-SPC') `C-x C-x' Repeat to move back.
`C-g' do deactivate region.
There are also libraries that give you ways to
browse among the marks, including by choosing
the text surrounding them using completion.
___
Icicles does that, for example, with `C-- C-SPC'.
Completion candidates are the text lines that
include the markers. (`C-- C-SPC' uses only local
markers, `C-- C-x C-SPC' uses only global markers,
and `C-0 C-SPC' uses all markers).
Because these are multi-commands you can trip among
any number of markers, in any order, during a single
invocation.
___
If you use Isearch+ then you can also have it
set the mark at the start point before searching,
so you can return to it with `C-x C-x' or
`C-u C-SPC'. You can toggle such mark-setting
anytime during Isearch using `M-s M-SPC'.
(Isearch is often a good way to move around, not
just to search.)
___
https://www.emacswiki.org/emacs/Icicles
https://www.emacswiki.org/emacs/IsearchPlus
next parent reply other threads:[~2020-12-05 21:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<courier.000000005FCBD00B.00007ECE@static.rcdrun.com>
2020-12-05 21:29 ` Drew Adams [this message]
2020-12-06 5:24 ` Jumping from one position to other position Jean Louis
2020-12-06 23:25 ` Michael Heerdegen
2020-12-05 18:23 Jean Louis
2020-12-05 22:11 ` Michael Heerdegen
2020-12-05 22:21 ` arthur miller
2020-12-05 22:54 ` Drew Adams
2020-12-06 0:55 ` arthur miller
2020-12-06 2:06 ` Drew Adams
2020-12-07 6:50 ` Jean Louis
2020-12-07 19:41 ` Arthur Miller
2020-12-07 20:26 ` Jean Louis
2020-12-05 23:38 ` Eric Abrahamsen
2020-12-06 0:12 ` Michael Heerdegen
2020-12-06 3:42 ` Eric Abrahamsen
2020-12-06 11:51 ` Stefan Möding
2020-12-06 18:15 ` Eric Abrahamsen
2020-12-06 23:07 ` Michael Heerdegen
2020-12-06 23:06 ` Michael Heerdegen
2020-12-06 5:41 ` Jean Louis
2020-12-06 23:11 ` Michael Heerdegen
2020-12-06 9:13 ` Marcin Borkowski
2020-12-06 2:12 ` 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=2f54a399-a632-4000-97f4-d0775165de9b@default \
--to=drew.adams@oracle.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
/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).