From: Marc Chantreux <mc@unistra.fr>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: line continuation with sed
Date: Fri, 14 Oct 2022 12:57:01 +0200 [thread overview]
Message-ID: <Y0lAfTo2GBznkI0l@prometheus.u-strasbg.fr> (raw)
In-Reply-To: <9184bbff-9e68-7b02-2595-3474b016dfff@eastlink.ca>
hello Ray,
I don't know about the \ problem (maybe you should provide a real
non-working example so we can play ourselves: setting variables,
having working substitions ...)
also: here are some workarounds:
a) is there a reason not to use what I believe to be the common way to do it?
var=$( print -l $var | sed -r '
s/.../.../
s/.../.../
s/.../.../
s/.../.../
')
b) why not embbed in a function?
a and b are not exclusive, you can write
substitute_things() sed -r '
s/.../.../
s/.../.../
s/.../.../
s/.../.../
'
var=$( print -l $var | substitute_things )
c) dig into a pure zsh substitution ?
I imagine $var is an array as you use print -l so
var=( those_are long_words )
print -l ${var/???/AAA}
gimme
AAAse_are
AAAg_words
HTH
--
Marc Chantreux
Pôle de Calcul et Services Avancés à la Recherche (CESAR)
http://annuaire.unistra.fr/p/20200
next prev parent reply other threads:[~2022-10-14 10:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:25 Ray Andrews
2022-10-14 6:35 ` Lawrence Velázquez
2022-10-14 11:20 ` Dominik Vogt
2022-10-14 15:44 ` Ray Andrews
2022-10-14 17:10 ` Dominik Vogt
2022-10-14 20:38 ` Lawrence Velázquez
2022-10-14 22:26 ` Ray Andrews
2022-10-14 10:57 ` Marc Chantreux [this message]
2022-10-14 11:19 ` Peter Stephenson
2022-10-14 17:15 ` Dominik Vogt
2022-10-14 22:21 ` Ray Andrews
2022-10-15 2:34 ` Aaron Schrab
2022-10-15 2:57 ` Ray Andrews
2022-10-15 5:08 ` Bart Schaefer
2022-10-15 16:53 ` Ray Andrews
2022-10-17 1:07 ` Bart Schaefer
2022-10-17 3:40 ` Ray Andrews
2022-10-17 4:20 ` Bart Schaefer
2022-10-17 9:19 ` Pier Paolo Grassi
2022-10-17 9:24 ` Pier Paolo Grassi
2022-10-17 9:31 ` Pier Paolo Grassi
2022-10-17 16:11 ` Bart Schaefer
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=Y0lAfTo2GBznkI0l@prometheus.u-strasbg.fr \
--to=mc@unistra.fr \
--cc=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).