From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Juri Linkov <juri@linkov.net>
Cc: larsi@gnus.org, 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: Mon, 26 Aug 2019 06:13:59 -0700 (PDT) [thread overview]
Message-ID: <765ae33e-8f34-4d69-9fa2-00ad24356852@default> (raw)
In-Reply-To: <<837e70h284.fsf@gnu.org>>
> > > A position is NOT popped off the ring. That's what's
> > > wrong with all of these. Likewise, the doc in the
> > > manuals.
> > >
> > > 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.
>
> And 'window' is not a window, it's a pane; and 'frame' is actually a
> window, etc. etc.
And all of those terms are standard Emacs
terminology, defined clearly and used
consistently.
That's not the case with this outlier use
of "pop", which is not a pop but is exactly
what Emacs calls "cycling" of a ring.
And again, it's about the doc also, not
just the function names.
next prev parent reply other threads:[~2019-08-26 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#16074: 24.3.50; enhancement request: Remove "pop" from command names & doc for `C-(u|x) C-SPC' 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 [this message]
2013-12-06 15:46 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
2019-08-26 6:26 ` Eli Zaretskii
2020-08-13 10:47 ` Lars Ingebrigtsen
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=765ae33e-8f34-4d69-9fa2-00ad24356852@default \
--to=drew.adams@oracle.com \
--cc=16074@debbugs.gnu.org \
--cc=eliz@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).