From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: drew.adams@oracle.com, 62862@debbugs.gnu.org
Subject: bug#62862: 26.3; Minor bug in (emacs) Shift Selection
Date: Wed, 06 Sep 2023 14:16:48 +0300 [thread overview]
Message-ID: <83r0nb361r.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmAnbBNVQYMR_wntK+xBjwu-MYZAF5V2DCeQwMNwpjsKA@mail.gmail.com> (message from Stefan Kangas on Tue, 5 Sep 2023 13:49:24 -0700)
> Cc: 62862@debbugs.gnu.org
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Tue, 5 Sep 2023 13:49:24 -0700
>
> severity 62862 wishlist
> thanks
>
> Drew Adams <drew.adams@oracle.com> writes:
>
> > "shift-selection" isn't a noun or a programming name. It's a noun
> > phrase, and should be written as "shift selection". In particular,
> > index entry "shift-selection" should also be replaced by "shift
> > selection". It might be good to also add a glossary entry for "shift selection".
>
> I think you're probably right here, but we have many 114 occurrences of
> "shift-selection" in our tree. I think it doesn't make sense to fix one
> without fixing the others, and then you'd need to be careful because
> some of them might refer to the symbol `shift-select'.
>
> So ultimately, I'm not sure it's worth spending time on. I guess we
> could accept a patch.
>
> Eli, what do you think?
English is not my first language, so the intricacies of the grammar
frequently elude me, but: how is this different from byte-compilation,
native-compilation, and other similar terminology that we use all over
the place?
In any case, I agree that this bug report is splitting hair.
next prev parent reply other threads:[~2023-09-06 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 14:59 bug#62862: 26.3; Minor bug in (emacs) Shift Selection Drew Adams
2023-09-05 20:49 ` Stefan Kangas
2023-09-06 11:16 ` Eli Zaretskii [this message]
2023-09-06 11:21 ` Stefan Kangas
2023-09-06 14:26 ` Drew Adams
2023-09-06 15:39 ` Eli Zaretskii
2023-09-06 20:48 ` 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=83r0nb361r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62862@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=stefankangas@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.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).