public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Mike Frysinger <vapier@gentoo.org>
Cc: linux-man@vger.kernel.org, John Gardner <gardnerjohng@gmail.com>,
	groff <groff@gnu.org>
Subject: words (and commands) that I learnt because of Branden (was: preferred /proc/<pid>/xxx style?)
Date: Fri, 9 Dec 2022 22:09:57 +0100	[thread overview]
Message-ID: <b2aba4a6-2a6a-74c6-97e8-3bc11018a623@gmail.com> (raw)
In-Reply-To: <20221209210340.azlp4t6c5myz534b@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1125 bytes --]

Hi Branden!

On 12/9/22 22:03, G. Branden Robinson wrote:
> Hi Alex & Mike,
> 
> Alex, you beat me to this one...
> 
> At 2022-12-09T20:43:21+0100, Alejandro Colomar wrote:
>>> personally i find that jarring to read because it's using italics
>>> for the whole path except for the pid which has no styling at all.
> 
> I submit that it is more jarring to have to have a file specification
> with mixed literal and variable components, such as
> 
> /var/log/epidemic/pid/port
> 
> and have it all marked up in the same typeface without a visual clue as
> to which part is nonliteral.  (Observe the ambiguity.)  Yes, "the
> experienced user will usually know [which part to replace]".[1]  To rely
> on that principle in documentation is a deriliction of duty.

Your emails are the reason I know and often use dict(1).  Lol.

$ dict deriliction
No definitions found for "deriliction", perhaps you mean:
gcide:  Dereliction
wn:  dereliction
moby-thesaurus:  dereliction

And yes, dereliction has a definition compatible with your use.

Cheers,

Alex


-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-09 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  9:41 preferred /proc/<pid>/xxx style? Mike Frysinger
2022-12-09 19:43 ` Alejandro Colomar
2022-12-09 21:03   ` G. Branden Robinson
2022-12-09 21:09     ` Alejandro Colomar [this message]
2022-12-09 22:10       ` words (and commands) that I learnt because of Branden (was: preferred /proc/<pid>/xxx style?) Deri
     [not found]         ` <CAGcdajfWk+=xR3UfAnNri0F7OL0mFJ4xsp=sQoWLo_-_G5wcBA@mail.gmail.com>
2022-12-10  7:15           ` hbezemer
2022-12-10  8:57         ` G. Branden Robinson

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=b2aba4a6-2a6a-74c6-97e8-3bc11018a623@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=gardnerjohng@gmail.com \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=vapier@gentoo.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