From: Allen Li <vianchielfaura@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [RFC] Could we get rid of Org specific "mark ring"
Date: Tue, 30 Jan 2018 15:53:10 -0800 [thread overview]
Message-ID: <CAJr1M6fyE0vp7sDSDHpJSRCHcwJUmXkTf5LQjRy7JrzedQJGOw@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8sbUv2MQiGcfDxBifTVwfg-jVO_NJV=UD2QpQuFMYaFjg@mail.gmail.com>
On Tue, Jan 30, 2018 at 3:15 PM, Samuel Wales <samologist@gmail.com> wrote:
> On 1/30/18, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> With local ring, you do, not with global one. That is standard Emacs
>> behaviour.
>
> does this constitute a change in org behavior? i'd want the same
> behavior as now. it would be confusing to follow a link, then follow
> another link in the same buffer, then go back globally, and end up not
> in the original place [or even the same buffer].
It does change org behavior, since the native mark ring
distinguishes local from global, whereas org-mark-ring does not.
With the proposed change, there won't be a single
org-mark-ring-goto, you would have to make sure you call the
right command out of pop-to-mark-command or pop-global-mark.
As a counterpoint, it is not entirely without precedent to
implement our own mark ring. xref.el also has its own "marker"
ring.
Maybe there should be a standard specialized marker ring macro in
Emacs, then org and xref (and others) can use it.
>
> probably i have the wrong end of the stick. but i find that asking
> weird questions like this can lead to people being on the same page
> where they were not.
>
next prev parent reply other threads:[~2018-01-31 0:42 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 [this message]
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
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=CAJr1M6fyE0vp7sDSDHpJSRCHcwJUmXkTf5LQjRy7JrzedQJGOw@mail.gmail.com \
--to=vianchielfaura@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--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).