unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 1/3] doc: fix some typos and grammar
Date: Tue, 17 Oct 2023 00:16:19 +0200	[thread overview]
Message-ID: <20231017001619+0200.395012-stepnem@smrk.net> (raw)
In-Reply-To: <20231016211320.M268439@dcvr>

On Mon, 16 Oct 2023 21:13:20 +0000
Eric Wong wrote:

>> --- a/TODO
>> +++ b/TODO
>> @@ -26,7 +26,7 @@ all need to be considered for everything we introduce.)
>>    archive locations to avoid SPOF.
>>  
>>  * optional Cache::FastMmap support so production deployments won't
>> -  need Varnish (Varnish doesn't protect NNTP nor IMAP, either)
>> +  need Varnish (Varnish doesn't protect NNTP or IMAP, either)
>
> I'm not sure about this change, I seem to remember `nor' being
> more suited for negatives.

I'm about 100% sure about this :-P

> Any citations or comments from others reading this?

I'm sure you will find many explanations in books / guides /
Internet, here's from one of the first DDG hits:

https://grammarhow.com/or-vs-nor/

  1. When making a negative statement that doesn’t contain
  “either” or “neither”, and the second item is a noun,
  adjective, or adverb phrase, you should use “or” instead of
  “nor” to continue the negation.

    He doesn’t like pizza or pasta. 
    He isn’t coming tonight or tomorrow because he is sick.
    He doesn’t speak English clearly or fluently.

If you wanted a version with "nor", that would be "Varnish
protects neither NNTP nor IMAP", but the meaning is slightly
different.

In short, you either use the n-words or the non-n-words (the
two pairs don't mix), and if the verb itself is negated, you
use either/or.

>>  Files in this directory are designed for:
>>  
>> -* users using from git or tarballs (and not the OS package manager)
>> +* users using git repo or tarballs (and not the OS package manager)
>
> I wonder if:
>
>   * users using our code from git or tarballs (and not the OS package manager)
>
> ...is better.  I always feel the need to clarify git the software
> vs. our code repo vs. our mirror on public-inbox.org/git   *shrug*

Yeah, I agree that's better.  Maybe also change "using" to
"running"?  "Users using" is a bit awkward.

Thank you for the date-related explanations, and the rediff tip!

-- 
Štěpán

  reply	other threads:[~2023-10-16 22:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 11:33 [PATCH 1/3] doc: fix some typos and grammar Štěpán Němec
2023-10-16 11:33 ` [PATCH 2/3] doc: lei-q: drop stale TODO comment (fixed in 1f1b1f0e22f7) Štěpán Němec
2023-10-16 21:17   ` Eric Wong
2023-10-16 11:33 ` [PATCH 3/3] search: rectify comment (rt: documented since 738c4a65719e) Štěpán Němec
2023-10-16 21:39   ` Eric Wong
2023-10-16 21:13 ` [PATCH 1/3] doc: fix some typos and grammar Eric Wong
2023-10-16 22:16   ` Štěpán Němec [this message]
2023-10-17  6:43     ` [PATCH 4/3] install/README: improve wording Eric Wong
2023-10-17  7:19       ` Štěpán Němec
2023-10-17  7:54         ` Eric Wong
2023-10-17  8:07           ` Štěpán Němec

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20231017001619+0200.395012-stepnem@smrk.net \
    --to=stepnem@smrk.net \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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.
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).