emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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: Sun, 25 Feb 2018 13:28:52 -0700	[thread overview]
Message-ID: <CAJcAo8v12ur_0ZvBAt3jeHqB_8D12ZngCXXZABd6C5wXdy1Gtw@mail.gmail.com> (raw)
In-Reply-To: <87inal1og8.fsf@nicolasgoaziou.fr>

On 2/25/18, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Samuel Wales <samologist@gmail.com> writes:
>
>> in org maint, i can click on a link and, without any cognitive
>> overhead, and with certainty, run a command to get back to the link i
>> clicked on.  to me this seems like basic hypertext ability, such as
>> you might find in info or the back button on firefox.
>>
>> i think your change will make this "back button" behavior as stated in
>> the previous paragraph impossible.  please correct me if that is not
>> true.
>
> That is not true.
>
> 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?  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.  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.

>> [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 don't want to alter the Emacs mark ring behaviour.

not asking you to.  my imperssion was that you could fix the bug by
having org mark ring push push to both rings.  you would keep the
current behavior of the org mark ring.  perhaps i misremember the bug.

> You are complaining about the global mark ring, which is an Emacs
> feature. So, this complaint should reach Emacs devel.

i am saying that it's not a substitute for the current org behavior.

iiuc, of course.

i don't want to have to care about the global mark ring.  i don't use
it, but if i am forced to by your change, then and only then do i
think it's a problem that its behavior is too fancy.  i don't think
emacs devs will fix it.  it has a mysterious value to its users.

  reply	other threads:[~2018-02-25 20:28 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 [this message]
2018-02-27  0:27                               ` Nicolas Goaziou
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=CAJcAo8v12ur_0ZvBAt3jeHqB_8D12ZngCXXZABd6C5wXdy1Gtw@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --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).