all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23746@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#23746: 25.0.95; Doc fixes (grammar, typos, clarification)
Date: Mon, 13 Jun 2016 17:14:35 +0300	[thread overview]
Message-ID: <83d1nlfa5w.fsf@gnu.org> (raw)
In-Reply-To: <87eg818mxg.fsf@gmx.net> (message from Stephen Berman on Mon, 13 Jun 2016 11:20:43 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Noam Postavsky <npostavs@users.sourceforge.net>,  kbrown@cornell.edu,  23746@debbugs.gnu.org
> Date: Mon, 13 Jun 2016 11:20:43 +0200
> 
> The line between grammaticality and stylistic variation isn't always
> clearcut, but I think there would be little or no disagreement among
> native speakers of the most widely spoken dialects of English (there may
> be dialects that differ, though I am not aware of any) regarding at
> least two of the three underlined parts above: "wish" and "allow" can
> both occur with non-finite clausal complements, but with differences:
> "wish" can occur only with a "to"-infinitive, usually without a subject,
> as in "I wish to go" but possibly also with one, as in "I wish you to
> go" or "I wish for you to go" (to me, the first sounds rather formal or
> archaic, the second sounds colloquial but possibly non-standard); in
> contrast, an "-ing" complement (with or without a subject), as in "I
> wish (you) going" is unacceptable.  "Allow" can occur with a
> "to"-infinitive, but then only with a subject, as in "I allowed you to
> go" but not "I allowed to go" (unless the complement is passivized, as
> in "We were allowed to go"); in some cases a subjectless "-ing"
> complement is possible, as in "the header line allows sorting entries by
> clicking on column headers", where the understood subject of "sorting"
> is nonspecific, e.g., people in general, not some particular individual:
> "I allowed John going" is unacceptable (there may be some dialectal
> variation about this, but I'm not sure).  These differences are
> grammatical in the sense that native speakers by and large agree on
> what's "right" and "wrong", regardless of context or stylistic register
> (though, again, there are gray areas).
>   
> As for my suggestion to use "can" instead of "could", I suspect there
> may be less agreement about that: both entail possibility, but in the
> above context "can" sounds more natural (or appropriate) to me due to
> the present tense of the whole sentence, in contrast to the following:
> "If your program told the process the dimensions of the window, the
> process could adapt its output to those dimensions".  But I think many
> native speakers would find either form perfectly acceptable in the above
> context.

Is the text below good enough?

     If the process’s buffer is displayed in a window, your Lisp program
  may wish to tell the process the dimensions of that window, so that the
  process could adapt its output to those dimensions, much as it adapts to
  the screen dimensions.  The following functions allow communicating
  this kind of information to processes; [...]





  parent reply	other threads:[~2016-06-13 14:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 15:54 bug#23746: 25.0.95; Doc fixes (grammar, typos, clarification) Stephen Berman
2016-06-11 16:08 ` Eli Zaretskii
2016-06-11 16:32   ` Stephen Berman
2016-06-11 19:22     ` Eli Zaretskii
2016-06-11 20:21       ` Noam Postavsky
2016-06-12 17:58         ` Stephen Berman
2016-06-12 18:55           ` Eli Zaretskii
2016-06-12 19:40             ` Ken Brown
2016-06-12 21:09               ` Noam Postavsky
2016-06-13  4:04                 ` Eli Zaretskii
2016-06-13  9:20                   ` Stephen Berman
2016-06-13  9:25                     ` Stephen Berman
2016-06-13 14:14                     ` Eli Zaretskii [this message]
2016-06-13 14:27                       ` Stephen Berman
2016-06-13 15:01                         ` Eli Zaretskii
2016-06-13 16:12                           ` Stephen Berman
2016-06-13 16:22                             ` Stephen Berman
2016-06-14  2:43                   ` Noam Postavsky
2016-06-14 14:29                     ` Eli Zaretskii

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=83d1nlfa5w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23746@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    --cc=stephen.berman@gmx.net \
    /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.