all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org, Drew Adams <drew.adams@oracle.com>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: RE: delete-other-frames
Date: Sat, 27 Aug 2016 17:41:03 -0700 (PDT)	[thread overview]
Message-ID: <dfec8f14-9868-439f-a12d-4b6465c85144@default> (raw)
In-Reply-To: <<E1bdlPn-0005Ch-I4@fencepost.gnu.org>>

>   > 1. If there is only one frame in the discussion, and @var{f}
>   > is a name for it, then "delete the frame, @var{f}" is correct.
> 
> You're right.  I must have been in a daze.

You're human. ;-)

>   > But if there might be more than one frame in the discussion,
>   > and @var{f} is the one we are concerned with at present, then
>   > this is correct: "delete the frame @var{f}".  (Note: no comma.)
>   > And so is this: "delete frame @var{f}".
> 
> Yes.  Exactly.  A comparable example in algebra is "Square the number x."
> 
>   > 2. I think Eli was talking about something different, but
>   > related: the fact that in Emacs doc the name of a parameter
>   > is often chosen to be a type name,
> 
> Grammatically, it does not matter whether the argument's name is f or
> frame.  In the first case, the sentence should be, "delete the frame
> @var{f}", shortened to "delete frame @var{f}".  In the second case,
> the sentence should be, "delete the frame @var{frame}", shortened to
> "delete frame @var{frame}".
> 
> Whether the argument name is the same as the description, or not,
> has no effect.
> 
> 				       and a convention is to
>   > omit the type noun to which the restrictive appositive
>   > applies and let the parameter name stand alone.
> 
>   > IOW, if the name of the individual echoes the name of the
>   > type then we can get by with just the individual name.
> 
> It is grammatical to omit the description of the argument, and use
> just its name.  There must be no article, in this usage.

Right.

>   > Example:
>   > Just "copy FILE to DIRECTORY",
> 
> Here FILE and DIRECTORY are both names of argument values,
> so they must have no articles.
> 
>    "copy F to D"
> 
> is equally grammatical, but it is clear only if the reader already
> knows that F is a file and D is a directory.  Otherwise, we need to
> say so.
> 
>   "copy the FILE to the DIRECTORY"
> 
> is grammatically incorrect because you can't put an article on a name.

Yes.



      parent reply	other threads:[~2016-08-28  0:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  8:19 delete-other-frames martin rudalics
2016-08-23 14:09 ` delete-other-frames Eli Zaretskii
2016-08-23 17:56   ` delete-other-frames Richard Copley
2016-08-23 18:31     ` delete-other-frames Eli Zaretskii
2016-08-23 19:55       ` delete-other-frames Richard Copley
2016-08-24  9:07     ` delete-other-frames martin rudalics
2016-08-24  9:06   ` delete-other-frames martin rudalics
2016-08-25  9:16     ` delete-other-frames martin rudalics
2016-08-25 14:46       ` delete-other-frames Eli Zaretskii
2016-08-27  1:32         ` delete-other-frames Richard Stallman
2016-08-27  7:40           ` delete-other-frames Eli Zaretskii
     [not found]         ` <<E1bdSUT-00059T-8W@fencepost.gnu.org>
2016-08-27  6:31           ` delete-other-frames Drew Adams
2016-08-27  7:45             ` delete-other-frames Eli Zaretskii
2016-08-27 13:32             ` delete-other-frames allan gottlieb
2016-08-27 13:40               ` delete-other-frames allan gottlieb
2016-08-27 21:45             ` delete-other-frames Richard Stallman
     [not found]           ` <<49a2a9c7-8573-4f07-897f-3eb444679d8a@default>
     [not found]             ` <<E1bdlPn-0005Ch-I4@fencepost.gnu.org>
2016-08-28  0:41               ` Drew Adams [this message]
     [not found] <<<57BC072F.9070704@gmx.at>
     [not found] <<57BC072F.9070704@gmx.at>

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dfec8f14-9868-439f-a12d-4b6465c85144@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.