From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: optimal expansions?
Date: Sun, 21 Apr 2024 07:09:39 -0700 [thread overview]
Message-ID: <9fe68299-c89f-46a1-b10f-eefadd03a262@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMqoWSkGbnDuBqBBfCW602FeROjHV0npQVoTw+phRvZDAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On 2024-04-21 05:23, Roman Perepelitsa wrote:
>> Seems we want '-r' most of the time. And the '--' should always be there.
> The missing `-r` is a bug. It should be there. The `--` in this case
> is optional because the positional argument cannot start with a dash.
But the '--' is good standard practice, yes? It's like putting on your
turn signal even when there's nobody behind you. As it was explained to
me, it's easier to do it than to think about whether you need to do it
or not. Just make it a habit. Meanwhile I have 313K of code that's all
built around my understanding that 'split on newlines' means add
newlines where you want to split :-( ... so I'll slowly go thru it all
and get that sorted out -- which will remove a hundred '\n's which will
in turn permit 'print -r'.
[-- Attachment #2: Type: text/html, Size: 1384 bytes --]
next prev parent reply other threads:[~2024-04-21 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 19:22 Ray Andrews
2024-04-19 20:40 ` Lawrence Velázquez
2024-04-19 23:25 ` Ray Andrews
2024-04-20 7:42 ` Roman Perepelitsa
2024-04-20 14:23 ` Ray Andrews
2024-04-20 22:54 ` Lawrence Velázquez
2024-04-20 23:59 ` Ray Andrews
2024-04-21 12:23 ` Roman Perepelitsa
2024-04-21 14:09 ` Ray Andrews [this message]
2024-04-21 14:19 ` Roman Perepelitsa
2024-04-21 16:14 ` Stephane Chazelas
2024-04-21 17:39 ` Roman Perepelitsa
2024-04-21 20:13 ` Stephane Chazelas
2024-04-21 20:46 ` Lawrence Velázquez
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=9fe68299-c89f-46a1-b10f-eefadd03a262@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).