From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: Allen Li <vianchielfaura@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Could we get rid of Org specific "mark ring"
Date: Tue, 27 Feb 2018 01:27:48 +0100 [thread overview]
Message-ID: <87po4rxomz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8v12ur_0ZvBAt3jeHqB_8D12ZngCXXZABd6C5wXdy1Gtw@mail.gmail.com> (Samuel Wales's message of "Sun, 25 Feb 2018 13:28:52 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> On 2/25/18, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> If you're still in the same document, the local mark ring moves you back
>> to the previous location. If you are not in the same document anymore,
>> the global mark ring brings you back to the previous location.
> i am at a link in file a that sends me to file b. i click on it
> [actually ret on it]. i pop the global mark ring.
>
> you are saying i will always get back to the link in file a always?
>
> now same example with the link pointing to file a. will the global
> mark ring take me there?
I guess these are rhetorical questions because I answered them above.
> if not, then i will have to use local mark
> ring. this means i have to think about whether the file i was in was
> the same file or not.
In practice, when I have no clue about where I was before, I first try
a local ring jump. If it fails, I do a global ring jump. This is
a no-brainer.
> almost always, by the time i have done whatever
> i was doing at target, that is totally forgotten. the cognitive
> overhead criterion in my first paragraph is violated. so i /think/ my
> statement about the back button behavior being broken with your change
> is true. please correct if that is wrong.
The current situation is worse. I have to know how I made it to the
current location, i.e., with an Org command or not. It is harder to
mitigate.
>>> [for the bug that seems to have prompted your proposal, we could be
>>> discussing pushing to the global and local mark rings. but this does
>>> not seem to be what we are discussing.]
I changed `org-mark-ring-push' to also push to Emacs mark ring. This is
better, but, out of the 3 problems I stated at the beginning of this
thread, it only solves the second one.
> i am saying that it's not a substitute for the current org behavior.
My proposal is slightly different than the current Org behaviour, but
the features are the same. I don't think Org own mark ring is really
needed. It makes Org less integrated in the Emacs ecosystem.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-02-27 0:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 23:21 [RFC] Could we get rid of Org specific "mark ring" Nicolas Goaziou
2018-01-30 5:06 ` Allen Li
2018-01-30 11:35 ` Kaushal Modi
2018-01-30 12:02 ` Rasmus
2018-01-30 12:36 ` Tim Cross
2018-01-30 20:47 ` Samuel Wales
2018-01-30 21:29 ` Nicolas Goaziou
2018-01-30 22:30 ` Samuel Wales
2018-01-30 22:33 ` Samuel Wales
2018-01-30 22:42 ` Nicolas Goaziou
2018-01-30 23:00 ` Samuel Wales
2018-01-30 23:06 ` Nicolas Goaziou
2018-01-30 23:15 ` Samuel Wales
2018-01-30 23:53 ` Allen Li
2018-01-31 2:02 ` Samuel Wales
2018-01-31 11:40 ` Nicolas Goaziou
2018-01-31 19:24 ` Samuel Wales
2018-01-31 19:29 ` Samuel Wales
2018-02-24 22:30 ` Nicolas Goaziou
2018-02-24 23:50 ` Samuel Wales
2018-02-25 8:08 ` Nicolas Goaziou
2018-02-25 20:28 ` Samuel Wales
2018-02-27 0:27 ` Nicolas Goaziou [this message]
2018-02-27 1:54 ` Samuel Wales
2018-02-27 7:09 ` Allen Li
2018-02-27 15:53 ` Nicolas Goaziou
2018-02-27 20:40 ` Samuel Wales
2018-02-27 20:48 ` Samuel Wales
2018-02-25 0:02 ` Samuel Wales
2018-04-26 23:34 ` Bastien
2018-04-27 0:32 ` Samuel Wales
2018-04-27 1:21 ` Bastien
2018-04-27 1:24 ` Samuel Wales
2018-04-27 1:56 ` Bastien
2018-05-03 22:04 ` Samuel Wales
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=87po4rxomz.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
--cc=vianchielfaura@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).