Re: Docs: Use non-default throughout the documentation

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Docs: Use non-default throughout the documentation
Date: 2026-02-04 17:02:17
Message-ID: CAKFQuwb-mQFJPKDFUZe8uSWBgn8mmcB9XwvXZ+NJviCTK7tP6g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, February 4, 2026, Peter Eisentraut <peter(at)eisentraut(dot)org>
wrote:

> On 29.01.26 00:48, David G. Johnston wrote:
>
>> Ended up looking at "non-default" and found four spellings of
>> "nondefault" in the user-facing documentation (vs. 40ish non-default).
>> Patch attached to fix the 4.
>>
>
> I think "non" is not normally used with a hyphen, since it is not a
> standalone word. So the fix should be the other way around.
>

Maybe it’s ironic.

I was looking at other words too, and indeed the absence of hyphen is
prevalent.

Agree on moving to nondefault.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Soloviev 2026-02-04 17:33:44 Re: Introduce Index Aggregate - new GROUP BY strategy
Previous Message Nathan Bossart 2026-02-04 16:54:22 Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects