From: Ihor Radchenko <yantar92@posteo.net>
To: Samuel Wales <samologist@gmail.com>
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 14:51:37 +0000 [thread overview]
Message-ID: <87wmlmiu86.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8tsy3bmB_dv6O3_Nf9TLDSQnq8YgjB_eRJ0vXt+xg3pLw@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> a redesign: i think it would probably be great if all three rings stopped
> being rings and started being trees, much like undo-tree, perhaps even with
> visualizer, with a consistent interface. if you think of info's navigation
> commands like l and r, you can imagine various things you can do. in
> undo-tree and vundo you can switch branches for the next place you might
> want to go to. point locs could use the same type of navigation commands.
I can see what you mean, although I am not sure if there is a good UI
for tree-like navigation in this scenario. At least, I can't think of
one. I am not sure how undo-tree-like interface would work here.
> draft spec: here is a draft spec i wrote for a point history ui.
>
> the spec applies to local, global, and link oriented, with an expanded idea
> of links to include such things, if desired by user, as identifiers,
> timestamps, bare fs paths, and many other things.
>
> dispatcher f and b go to next and prev point loc in buffer, much like m-tab
> in org. it is settable on the fly whether it navigates local, global, or
> link, or it can use different prefixes or initial key sequences.
This is not like mark ring though - just search across specific object
types in buffer. Something akin next/previous-button.
> 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.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-07-15 14:58 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 [this message]
2024-07-16 1:00 ` Samuel Wales
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=87wmlmiu86.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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.
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).