From: "Lawrence Velázquez" <vq@larryv.me>
To: Bart Schaefer <schaefer@brasslantern.com>,
Stephane Chazelas <stephane@chazelas.org>
Cc: zsh-workers@zsh.org
Subject: Re: Block comments ala Ray
Date: Fri, 12 Feb 2021 13:16:28 -0500 [thread overview]
Message-ID: <B2B62C95-EEDF-442A-9ACA-75EE653CEB72@larryv.me> (raw)
In-Reply-To: <CAH+w=7bLXK_rZPsx33BTyKb5Q43uPc3W4Ayf0A8Gfkik0W9r9A@mail.gmail.com>
> On Feb 12, 2021, at 11:55 AM, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Fri, Feb 12, 2021 at 7:45 AM Stephane Chazelas <stephane@chazelas.org> wrote:
>>
>> 2021-02-12 07:30:23 -0800, Bart Schaefer:
>>> On Thu, Feb 11, 2021 at 11:40 PM Stephane Chazelas
>>> <stephane@chazelas.org> wrote:
>>>>
>>>> :||:<<'# some comment'
>>>
>>> That's exactly what the zsh-users discussion has been telling Ray he
>>> should not do, because at some point it's not going to work the way he
>>> expects.
>> [...]
>>
>> How so?
>
> What was said on zsh-users (not by me):
>
> "Here-documents are not comments, despite your best efforts to abuse
> them for that role."
This was me, addressing someone with shaky shell fundamentals who
was aliasing the here-document idiom and expecting it to behave
identically to real comments (discarded during lexing, no further
impact on the script).
Naturally, the remark is rather less applicable to someone who
remains aware of the nature and limitations of the idiom.
vq
next prev parent reply other threads:[~2021-02-12 18:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 6:05 Bart Schaefer
2021-02-10 6:16 ` Roman Perepelitsa
2021-02-12 6:17 ` Bart Schaefer
2021-02-12 6:26 ` Bart Schaefer
2021-02-12 6:41 ` Roman Perepelitsa
2021-02-12 7:40 ` Stephane Chazelas
2021-02-12 7:46 ` Roman Perepelitsa
2021-02-12 15:30 ` Bart Schaefer
2021-02-12 15:45 ` Stephane Chazelas
2021-02-12 16:55 ` Bart Schaefer
2021-02-12 18:16 ` Lawrence Velázquez [this message]
2021-02-12 21:02 ` Stephane Chazelas
2021-02-12 21:12 ` Stephane Chazelas
2021-02-12 21:29 ` Bart Schaefer
2021-02-13 7:37 ` Stephane Chazelas
2021-02-15 22:28 ` Daniel Shahaf
2021-02-13 4:33 ` Bart Schaefer
2021-02-15 0:42 ` Greg Klanderman
2021-02-12 15:24 ` Matthew Martin
2021-02-12 16:18 ` Bart Schaefer
2021-02-15 21:30 ` Daniel Shahaf
2021-02-15 22:35 ` Bart Schaefer
2021-02-12 20:48 ` Bart Schaefer
2021-02-13 8:35 ` Stephane Chazelas
2021-02-13 8:53 ` Stephane Chazelas
2021-02-14 20:50 ` Bart Schaefer
2021-02-14 20:15 ` Bart Schaefer
2021-02-15 0:36 ` Vincent Lefevre
2021-02-15 1:07 ` Bart Schaefer
2021-02-15 1:38 ` Vincent Lefevre
2021-02-15 17:43 ` Stephane Chazelas
2021-02-15 22:06 ` Daniel Shahaf
2021-02-15 22:39 ` Bart Schaefer
2021-02-14 20:58 ` Bart Schaefer
2021-02-16 15:30 ` Juergen Christoffel
2021-02-16 17:21 ` Vincent Lefevre
2021-02-16 18:29 ` Bart Schaefer
2021-02-16 21:35 ` Juergen Christoffel
2021-02-16 18:21 ` pod documentation in zsh scripts (Was: Block comments ala Ray) Stephane Chazelas
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=B2B62C95-EEDF-442A-9ACA-75EE653CEB72@larryv.me \
--to=vq@larryv.me \
--cc=schaefer@brasslantern.com \
--cc=stephane@chazelas.org \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).