From: Stephen Berman <stephen.berman@gmx.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Terminology questions
Date: Fri, 05 Jul 2013 16:08:50 +0200 [thread overview]
Message-ID: <87bo6hm74d.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: 51D1F3B2.1060506@cs.ucla.edu
On Mon, 01 Jul 2013 14:25:06 -0700 Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 07/01/2013 11:30 AM, Stephen Berman wrote:
>> if people think "persistently" is wrong here,
>> and "permanently" doesn't lead to the expectation that only one change
>> is possible, then the latter is fine with me.
>
> "persistently" is fine, but "persistently change" confused me.
> E.g., "stars persistently change in color and brightness
> during their evolution" means that stars are always
> changing, but the Emacs doc intended to say that the setting change
> persists through Emacs restarts, not that the setting is always
> changing. I changed it to "permanently" because I was too
> lazy to reword the sentence, but if "persistent" is
> preferable then it'd be fine to reword the doc to say
> something like "make the change persistent".
>
>> The other case involves two places where I wrote "cross-categorial",
>> which Paul changed to "cross-category"
>
> I used "cross-category" over "cross-categorial" because the
> former is in aspell's dictionary and the latter is not --
> sorry, I wasn't familiar with either term. If you intend
> the social-science connotation please change it back to
> "cross-categorial", otherwise I suggest leaving it alone as
> "cross-category" is less likely to furrow readers' brows.
>
> Neither of these is a big deal, of course; please feel
> free to revert both of my changes.
Thanks for the explanations. I've decided to avoid the confusing terms
altogether and reworded the doc in revision 113288; it's more verbose
but hopefully clearer.
Steve Berman
prev parent reply other threads:[~2013-07-05 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 18:30 Terminology questions Stephen Berman
2013-07-01 21:25 ` Paul Eggert
2013-07-02 10:12 ` Thien-Thi Nguyen
2013-07-05 14:08 ` Stephen Berman [this message]
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=87bo6hm74d.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).