From: markus schnalke <meillo@marmaro.de>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] sh: cmd | >file
Date: Sat, 04 Jan 2020 23:44:35 +0100 [thread overview]
Message-ID: <1ins9r-4KA-00@marmaro.de> (raw)
In-Reply-To: <CACqnu4UAUQmPOfjmz1ZVgNtVRFG=9a=PYtGu4vSKGHv05aNjSg@mail.gmail.com>
Hoi.
[2020-01-04 23:19] Terry Jones <terry@jon.es>
>
> Was : actually designed for commenting?
Hardly, because who would want comments to have side effects:
: don't do this
Or this:
: ignored; echo executed
Or this dangerously ``outcommented'' line:
: test ... && rm file
!
Using : for comments is only possible as the command does nothing
and ignores its arguments ... but the shell parses the arguments
as for every other command ... and executes stuff in the line that
are no arguments to :.
In case of #, the rest of the line is truly ignored, as comments
should be like.
> but : is much nicer because you can "comment" out a
> single command in (e.g.) an if/then and it remains syntactically valid and
> executable. I find it very elegant.
Can you please give an example for me to understand what you mean
by that?
meillo
next prev parent reply other threads:[~2020-01-04 22:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 2:58 Doug McIlroy
2020-01-04 10:07 ` markus schnalke
2020-01-04 11:47 ` Robert Clausecker
2020-01-04 22:31 ` Chet Ramey
2020-01-04 21:02 ` Dave Horsfall
2020-01-04 21:06 ` Jon Steinhart
2020-01-05 0:03 ` Eric Allman
2020-01-05 1:49 ` Adam Thornton
2020-01-05 2:44 ` Chet Ramey
2020-01-05 8:15 ` Brantley Coile
2020-01-05 15:16 ` Chet Ramey
2020-01-04 21:11 ` Dave Horsfall
2020-01-04 21:39 ` Warner Losh
2020-01-04 22:19 ` Terry Jones
2020-01-04 22:33 ` Chet Ramey
2020-01-04 23:53 ` Dave Horsfall
2020-01-05 0:04 ` Andreas Kusalananda Kähäri
2020-01-05 2:41 ` Chet Ramey
2020-01-05 13:45 ` Sven Mascheck via TUHS
2020-01-05 15:18 ` Chet Ramey
2020-01-05 21:21 ` Dave Horsfall
2020-01-06 13:53 ` Chet Ramey
2020-01-06 15:42 ` Brantley Coile
2020-01-06 15:46 ` arnold
2020-01-06 16:13 ` Clem Cole
2020-01-06 20:44 ` arnold
2020-01-06 20:51 ` Steve Nickolas
2020-01-06 21:32 ` Clem Cole
2020-01-06 21:39 ` Brad Spencer
2020-01-06 21:29 ` Dave Horsfall
2020-01-06 21:55 ` Chet Ramey
2020-01-06 22:22 ` Dave Horsfall
2020-01-06 22:52 ` Dan Cross
2020-01-07 0:50 ` Adam Thornton
2020-01-06 22:10 ` Bakul Shah
2020-01-04 22:44 ` markus schnalke [this message]
2020-01-04 23:01 ` Terry Jones
2020-01-04 22:22 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 5:03 Brian Walden
2020-01-07 4:49 Brian Walden
2020-01-06 19:47 Doug McIlroy
2020-01-06 16:11 Brian Walden
2020-01-06 16:33 ` Clem Cole
2020-01-06 3:24 Brian Walden
2020-01-06 15:42 ` Richard Salz
2020-01-06 15:45 ` Brantley Coile
2020-01-03 12:45 markus schnalke
2020-01-03 14:00 ` Steffen Nurpmeso
2020-01-03 17:03 ` Brian Zick
2020-01-03 17:18 ` markus schnalke
2020-01-04 0:53 ` Sven Mascheck via TUHS
2020-01-04 20:41 ` Steffen Nurpmeso
2020-01-03 19:38 ` markus schnalke
2020-01-03 19:44 ` Warner Losh
2020-01-03 22:49 ` Michael Parson
2020-01-03 23:32 ` Dave Horsfall
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=1ins9r-4KA-00@marmaro.de \
--to=meillo@marmaro.de \
--cc=tuhs@minnie.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).