unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "62862@debbugs.gnu.org" <62862@debbugs.gnu.org>
Subject: bug#62862: 26.3; Minor bug in (emacs) Shift Selection
Date: Wed, 6 Sep 2023 14:26:17 +0000	[thread overview]
Message-ID: <SJ0PR10MB54884EA8BCD7C46678B63D77F3EFA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmndSGM7khw2TzRwkw8+o3n+5v0norxwZgSQ1U7mcZ59HQ@mail.gmail.com>

> > but: how is this different from byte-compilation, native-compilation,
> > and other similar terminology that we use all over the place?
> 
> Maybe Drew can answer this as a general point of interest, but...
> 
> > In any case, I agree that this bug report is splitting hair.
> 
> ...since we seem to agree, I'm closing this bug report.

The general rule applies also to byte-compilation etc.
But it's a general rule.  What matters in the end is
usage.  If a particular writing of a composite word
becomes most common then that's it.  It's not unusual
to see an evolution from xxx yyy to xxx-yyy to xxxyyy.

The general rule is that when used as a noun it's a
noun phrase, and is written as separate words.  When
it's used as an adjective before a noun it's written
with a hyphen.  So:

"This happens during byte compilation."
"Byte-compilation optimization happens on Tuesday."

It's fine to decide whatever style you like.  It's
generally good to then be consistent in using it, of
course.

The reason for the rule is for readability: ease of
parsing when used as an adjective.  Nothing more.

In any case, I'd still suggest a glossary entry for
shift selection (or shift-selection, if that's your
decision).


  reply	other threads:[~2023-09-06 14:26 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
2023-09-06 11:21     ` Stefan Kangas
2023-09-06 14:26       ` Drew Adams [this message]
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=SJ0PR10MB54884EA8BCD7C46678B63D77F3EFA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=62862@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).