unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: "50926@debbugs.gnu.org" <50926@debbugs.gnu.org>
Subject: bug#50926: [External] : bug#50926: Light edits to the Emacs Manual (screen.texi)
Date: Sat, 9 Oct 2021 16:41:50 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488655E5551CF7A0A265F04F3B39@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83a6jiy87t.fsf@gnu.org>

> > > > -  Some commands display informative messages in the echo area to
> > > >    tell
> > > > -you what the command has done, or to provide you with some
> > > >    specific
> > > > +  Some commands display messages in the echo area to tell
> > > > +you what it has done, or some other specific
> > >
> > > you replaced "the command" with "it", which made the text
> > > ambiguous: "it" could refer to the echo area.
> >
> > I believe this is fixed by Drew's correction to use the plural
> > "they":
> 
> No, it isn't, because "they" could refer to the "informative
> messages".

Only if a reader doesn't understand that it
would make no sense to display a message to tell
you what that message itself has done.

(That might be amusing, however...)

And in that case I expect our docs will present
much more serious problems for that reader.)

But if you really want to be sure such a reader
doesn't get confused, then say "those commands"
instead of "they".

The point is that the messages tell you what the
commands _have_ done, not what "the command" has
done.

> >-  Each Emacs frame normally has a @dfn{menu bar} 

FWIW, I think "normally" is inappropriate here.
It's not about normality or abnormality.

I suggest something like "by default" (or
"usually" or "typically", if that's what you
really mean).





  reply	other threads:[~2021-10-09 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 23:51 bug#50926: Light edits to the Emacs Manual (screen.texi) Stefan Kangas
2021-10-01  1:50 ` bug#50926: [External] : " Drew Adams
2021-10-01 13:29   ` Stefan Kangas
2021-10-01 17:13     ` Drew Adams
2021-10-01  7:20 ` Eli Zaretskii
2021-10-09  0:40   ` Stefan Kangas
2021-10-09  7:21     ` Eli Zaretskii
2021-10-09 16:41       ` Drew Adams [this message]
2021-10-09 16:54         ` bug#50926: [External] : " Eli Zaretskii
2021-10-09 17:18           ` 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=SJ0PR10MB5488655E5551CF7A0A265F04F3B39@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=50926@debbugs.gnu.org \
    --cc=eliz@gnu.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).