From: Samuel Wales <samologist@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [fr] refile goto: push mark in the target buffer first
Date: Mon, 15 Jul 2024 18:00:39 -0700 [thread overview]
Message-ID: <CAJcAo8s=hEjVEXkPWXkB=JObe4wEwo7_H1-_A=uArXC-afNZdA@mail.gmail.com> (raw)
In-Reply-To: <87wmlmiu86.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]
On Monday, July 15, 2024, Ihor Radchenko <yantar92@posteo.net> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
> This is not like mark ring though - just search across specific object
> types in buffer. Something akin next/previous-button.
>
correct. f and b are for forward and backward. for the local mark ring,
it will go to the next or prev mark in the buffer by position in the
buffer. not a history command per se.
>
> > vvv draft spec
> > Dispatcher l and r go back and forward
> > in history of point, regardless of
> > buffer. Thus, dispatcher RET then
> > dispatcher l returns to point, even if
> > point was not on a link. The bindings
> > are modeled on l and r in info or help.
> >
> > Dispatcher n and p change at branching
> > points, cycling you to the different
> > places r might go and back.
>
> This part about branching is not very clear.
>
> in undo-tree and i think vundo, you have a tree. in the case of point
locs, suppose you were in one place, 0, and then you went to a, then back
to 0 with l, then went to b. now you have a branching point at 0. you can
do n and p to choose between a and b -- actually moving to them with a
message is an option here as is showing their lines in a visualizer. n
and p could also cycle through 0 for convenience if that's not too
confusing [a message can notify]. a command like l can also be used to go
back to it.
so the f and b thing has nothing to do with history; it is just navigation
in the buffer [if local ring] according to the sequence in the buffer, akin
to m-tab in org for links.
l and r are like in info, navigating history. n and p choose different r
locations for the case where there is more than one r.
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
[-- Attachment #2: Type: text/html, Size: 2468 bytes --]
next prev parent reply other threads:[~2024-07-16 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 0:24 [fr] refile goto: push mark in the target buffer first Samuel Wales
2024-07-06 15:28 ` Ihor Radchenko
2024-07-07 2:39 ` Samuel Wales
2024-07-13 13:32 ` Ihor Radchenko
[not found] ` <CAJcAo8tpfBvUGjs9vo7XUhUmU_2LnyqRNq0-6JwVisjhwYtBzQ@mail.gmail.com>
[not found] ` <87v818jnsi.fsf@localhost>
[not found] ` <CAJcAo8um9NtA1q6-uQ5iSCJUJeWnXoCyx=phKRbrdVNWDte36A@mail.gmail.com>
2024-07-15 2:56 ` Samuel Wales
2024-07-15 14:51 ` Ihor Radchenko
2024-07-16 1:00 ` Samuel Wales [this message]
2024-07-16 17:06 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8s=hEjVEXkPWXkB=JObe4wEwo7_H1-_A=uArXC-afNZdA@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).