From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: nl section delimiters
Date: Sat, 11 May 2024 22:48:16 +0200 [thread overview]
Message-ID: <20240511204816.UwAcweCX@steffen%sdaoden.eu> (raw)
In-Reply-To: <CAKH6PiWG-cFwQYPKDhKg_LdDKChC8odbxnnTOjC9+KZea7OgQA@mail.gmail.com>
Douglas McIlroy wrote in
<CAKH6PiWG-cFwQYPKDhKg_LdDKChC8odbxnnTOjC9+KZea7OgQA@mail.gmail.com>:
|> But it misses the coolness of the empty true(1).
|
|Too cool. With an empty true(1), execl("true", "true", 0) is out in the
|cold.
There i stand singing "ein Männlein steht im Walde" (a "little
man" stands in the forest).
..ok, but then i do note here and now the certain lists where the
question on whether an additional entry in the search path does
make any sense at all for certain constructs comes up regulary,
(even) i have lived this multiple times already, it is about
The [.] command search [.] allows for a standard utility to be
implemented as a regular built-in as long as it is found in the
appropriate place in a PATH search.
[.]command -v true might yield /bin/true or some similar pathname.
Other [non-standard] utilities [.] might exist only as built-ins
and have no pathname associated with them. These produce output
identified as (regular) built-ins. Applications encountering
these are not able to count on execing them, using them with
nohup, overriding them with a different PATH, and so on.
The next POSIX standard will have around 4058 pages (3950 without
index) and 137171 lines (not counting index).
And i was surely laughing when this list it surely was came along
this somewhen in the past, and isn't that just "a muscle car":
#?0|kent:unix-hist$ git show Research-V7:bin/true | wc -c
0
Many greetings and best wishes!!
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2024-05-11 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 2:19 [TUHS] " Douglas McIlroy
2024-05-11 20:48 ` Steffen Nurpmeso [this message]
2024-05-13 13:12 ` [TUHS] " Chet Ramey
-- strict thread matches above, loose matches on Subject: below --
2024-05-10 6:15 [TUHS] " David Arnold
2024-05-10 10:08 ` [TUHS] " Rob Pike
2024-05-10 16:05 ` segaloco via TUHS
2024-05-10 16:50 ` John P. Linderman
2024-05-10 23:05 ` Steffen Nurpmeso
2024-05-11 9:07 ` Ralph Corderoy
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=20240511204816.UwAcweCX@steffen%sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).