unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Stefan Kangas <stefan@marxist.se>,
	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: Sun, 25 Aug 2019 15:03:07 -0700 (PDT)	[thread overview]
Message-ID: <d0089b3d-6ade-4414-8a85-97d61b20cf9a@default> (raw)
In-Reply-To: <87a7bxm12m.fsf@mail.linkov.net>

> > The enhancement request is to fix this wrong
> > terminology wrt BOTH `global-mark-ring' and
> > `mark-ring'.
> 
> And `yank' doesn't yank, and `kill' doesn't kill literally.
> What is the most important is that docstrings should describe
> the behavior in all details.  The name is more a matter of taste.

Irrelevant.  Emacs _has_ "pop" in its terminology,
just like it has "yank" and "kill" (buffer, text).

This mistaken use of "pop" doesn't fit Emacs's use
of the word (or even typical outside uses of it).

And Emacs _has_ a term, "cycle", for the behavior
here.  "Cycle" is the term Emacs uses for rings.

And it's not just about the name.  It's also about
the doc, which incorrectly tells users that the
behavior is to "pop" the mark/position "off" the
ring.

That's wrong; it's not what happens.  That doesn't
"describe the behavior in all details".  Instead,
it describes a different behavior, which doesn't
happen.

Hand-waving alone can't justify this misleading.

On the other hand, as I replied to Eli, you can
decide whether fixing this is "worth the necessary
time, energy, VC resources and your whatnot."
That's up to you.





  reply	other threads:[~2019-08-25 22:03 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
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 [this message]
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=d0089b3d-6ade-4414-8a85-97d61b20cf9a@default \
    --to=drew.adams@oracle.com \
    --cc=16074@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --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).