unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Sean Whitton <spwhitton@spwhitton.name>, Eli Zaretskii <eliz@gnu.org>
Cc: "philipk@posteo.net" <philipk@posteo.net>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: New optional Eshell module: em-elecslash
Date: Sat, 16 Apr 2022 21:42:19 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488DC84BE590E3B0DF1ACEBF3F19@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87fsmckd6d.fsf@melete.silentflame.com>

(A reply for the list, not necessarily for you.)

> but in the U.K. we don't have this idea that
> the passive voice is worse than the active --
> I didn't learn the distinction until after
> finishing a humanities degree

https://en.wikipedia.org/wiki/Talk%3AEnglish_passive_voice#Differences_between_US_and_British_English
___

Guidance about the active/passive choice is generally
more subtle/involved than just one being considered
systematically "worse than" the other.

See https://en.wikipedia.org/wiki/English_passive_voice#Style_advice,
and that whole page, generally.  For example:

 "Use of the passive in English varies with writing
  style and field. It is generally much less used
  than the active voice but is more prevalent in
  scientific writing than in other prose.

  Contemporary style guides discourage excessive
  use of the passive but appropriate use is
  generally accepted, for instance where the
  patient is the topic, the agent is unimportant
  (and therefore omitted), or the agent is to be 
  highlighted (and therefore placed toward the end)."

And see https://www.grammarly.com/blog/passive-voice/.
___

One study of the use of passive voice in scientific writing:

https://jcom.sissa.it/sites/default/files/documents/JCOM_1301_2014_A03.pdf
___

IMO it's more about avoiding a systematic or
habitual overuse of the passive voice, which is
not unknown to writing that's more formalistic in
style. ;-)

There's no formula that applies well absolutely.
Neither active nor passive voice is systematically
"worse than" the other.

But if you have a doubt in some case, read both
and see which you think is clearer.  If still in
doubt, it probably means you see no special
reason for the passive voice there - use active.



  reply	other threads:[~2022-04-16 21:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  2:48 Optional Eshell modules -- to emacs.git or ELPA? Sean Whitton
2022-01-29 11:51 ` Philip Kaludercic
2022-04-16 18:57   ` New optional Eshell module: em-elecslash Sean Whitton
2022-04-16 19:18     ` Eli Zaretskii
2022-04-16 20:04       ` Sean Whitton
2022-04-16 21:42         ` Drew Adams [this message]
2022-04-17  6:20         ` Eli Zaretskii
2022-04-17 16:48           ` [External] : " Drew Adams
2022-04-19 16:52           ` Sean Whitton
2022-04-20  0:36             ` Sean Whitton
2022-04-20  6:19               ` Eli Zaretskii
2022-04-20 20:14                 ` Sean Whitton
2022-04-21  6:15                   ` Eli Zaretskii
2022-04-16 21:12       ` Sean Whitton
2022-04-16 22:58     ` Stefan Monnier
2022-04-17  5:02       ` Sean Whitton
2022-04-17  6:24     ` Jim Porter
2022-04-19 15:28       ` Sean Whitton

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=SJ0PR10MB5488DC84BE590E3B0DF1ACEBF3F19@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=spwhitton@spwhitton.name \
    /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).