From: Heime <heimeborgia@protonmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: List line numbers for easy navigation
Date: Thu, 18 Apr 2024 22:06:00 +0000 [thread overview]
Message-ID: <I1N3KvOULYK3hgWWcIH5rR_am-4LmiukEiOEMM-hyL45VlB0mkU8XnLuqW5p6S1InJ75y-XG16mdp5k8DR3K7ZEPUwlsuKsn7WZoGju4FyQ=@protonmail.com> (raw)
In-Reply-To: <87frvifk2c.fsf@gmx.net>
On Friday, April 19th, 2024 at 9:16 AM, Stephen Berman <stephen.berman@gmx.net> wrote:
> On Thu, 18 Apr 2024 21:02:56 +0000 Heime heimeborgia@protonmail.com wrote:
>
> > On Friday, April 19th, 2024 at 8:54 AM, Stephen Berman
> > stephen.berman@gmx.net wrote:
> >
> > > On Thu, 18 Apr 2024 20:38:44 +0000 Heime heimeborgia@protonmail.com wrote:
>
> [...]
>
> > > > Suppose I am writing some code at row 1358 and want to check on two functions,
> > > > one starting at row 355, the other at row 589. I want to go to the row and add
> > > > the current row to the list (Will do this three times). Then have a command to
> > > > navigate between them. Call command te get me to the respective row.
> > >
> > > You can do this with existing Emacs commands: `M-g M-g' (or` M-g g') to
> > > get prompted for a line number and then jump to it, and then you can use
> > > the mark ring (info "(emacs) Mark Ring") or registers (info "(emacs)
> > > Position Registers") to navigate between positions. Why reinvent the
> > > wheel?
> > >
> > > Steve Berman
> >
> > Because I am finding that going to the marks with the current keybindings
> > difficult to remember. Perhaps I can make a new easier command that takes
> > care of the marks for me and help me use the existing emacs commands without
> > too much struggle.
>
>
> Then I can only suggest reading those sections of the Emacs manual and
> if necessary looking at the source code of the functions (I think most
> of the are Lisp functions in simple.el). Then maybe you can put
> something together for yourself, though I suspect it won't be easy to
> get something that works as well as the existing commands. One other
> tip: if what you really want to do is navigate between existing
> functions or other named pieces of code, then using `M-.' and` M-,' is
> probably the most efficient way, see (info "(emacs) Looking Up Identifiers").
>
> Steve Berman
I know that C-<SPC> calls the command (set-mark-command ARG)
But have no idea of the commands associated with "C-<SPC> C-<SPC>" and with "C-u C-<SPC>". Would like a command I can
call with M-x that does the marking functionality.
next prev parent reply other threads:[~2024-04-18 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 19:38 List line numbers for easy navigation Heime
2024-04-18 20:14 ` Stephen Berman
2024-04-18 20:23 ` Heime
2024-04-18 20:32 ` Stephen Berman
2024-04-18 20:38 ` Heime
2024-04-18 20:54 ` Stephen Berman
2024-04-18 21:02 ` Heime
2024-04-18 21:16 ` Stephen Berman
2024-04-18 22:06 ` Heime [this message]
2024-04-18 23:10 ` Heime
2024-04-19 4:52 ` Yuri Khan
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='I1N3KvOULYK3hgWWcIH5rR_am-4LmiukEiOEMM-hyL45VlB0mkU8XnLuqW5p6S1InJ75y-XG16mdp5k8DR3K7ZEPUwlsuKsn7WZoGju4FyQ=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=stephen.berman@gmx.net \
/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).