unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16074@debbugs.gnu.org
Subject: bug#16074: 24.3.50; enhancement request: Remove "pop" from command names & doc for `C-(u|x) C-SPC'
Date: Sat, 24 Aug 2019 07:20:16 -0700 (PDT)	[thread overview]
Message-ID: <c215ef6c-aeeb-4cc8-9ac2-68492c07343a@default> (raw)
In-Reply-To: <CADwFkmm5ZZZjR6Ua0POYcHTcwubTSnEwzSTZoGUHN42fgWf8aw@mail.gmail.com>

> >> The names and doc of the commands bound to `C-u C-SPC' and `C-x C-
> >> SPC' are misleading, in that the commands do not really "pop" the 
> >> marker rings. They cycle the rings.  Markers are not removed from
> >> the rings by such "popping".
> >>
> >> Emacs uses the verb "cycle" for this kind of behavior elsewhere.
> >> The same terminology should be used here also.  We should rename
> >> `pop-global-mark' and rephrase the doc.
> >
> > Yes, renaming here seems like a good idea.
> 
> How about the attached patch?

Maybe I missed something when perusing the patch,
but it looks like it addresses only the global
mark ring (`C-x C-SPC'), not also the (local)
mark ring (`C-u C-SPC').

The enhancement request is about both.  The doc
for both speaks of "pop" instead of cycle.





  parent reply	other threads:[~2019-08-24 14:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 15:46 bug#16074: 24.3.50; enhancement request: Remove "pop" from command names & doc for `C-(u|x) C-SPC' Drew Adams
2016-04-29 14:47 ` Lars Ingebrigtsen
2019-08-24  5:40 ` Stefan Kangas
2019-08-24  6:28   ` Eli Zaretskii
2019-08-24 14:20   ` Drew Adams [this message]
2019-08-25  5:48   ` Lars Ingebrigtsen
2019-08-25 16:14     ` Drew Adams
2019-08-25 20:09       ` Juri Linkov
2019-08-25 22:03         ` Drew Adams
2019-08-26  6:26         ` Eli Zaretskii
2020-08-13 10:47           ` Lars Ingebrigtsen
     [not found] <<cb3c1188-7123-413c-b945-6f73ba4557c7@default>
     [not found] ` <<CADwFkmm5ZZZjR6Ua0POYcHTcwubTSnEwzSTZoGUHN42fgWf8aw@mail.gmail.com>
     [not found]   ` <<831rxbjcv1.fsf@gnu.org>
2019-08-24 14:22     ` Drew Adams
     [not found]   ` <<87y2zh94nz.fsf@gnus.org>
     [not found]     ` <<b2e6dd7c-d877-4e48-80eb-3c219eb1d4d7@default>
     [not found]       ` <<87a7bxm12m.fsf@mail.linkov.net>
     [not found]         ` <<837e70h284.fsf@gnu.org>
2019-08-26 13:13           ` Drew Adams

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c215ef6c-aeeb-4cc8-9ac2-68492c07343a@default \
    --to=drew.adams@oracle.com \
    --cc=16074@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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.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).