zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: line continuation with sed
Date: Fri, 14 Oct 2022 19:57:55 -0700	[thread overview]
Message-ID: <a24ea038-0a73-cc86-25af-239738dd6de3@eastlink.ca> (raw)
In-Reply-To: <Y0ocNjoVIUo/zH3o@pug.qqx.org>


On 2022-10-14 19:34, Aaron Schrab wrote:
> Instead I'll give a method to help avoid the problem. For awhile now, 
> anytime I'm using calling a command with enough options to warrant 
> line continuation I build them up in an array instead. This allows 
> splitting across lines without using a backslash at the end, and 
> *actually* allows comments.
>
> This also allows the arguments to be build up gradually with some 
> being added conditionally.
>
> The below actually works as written including the comments:
>
>     args=(
>       -re 's/abc/xyx/' # End of the alphabet is better
>       -re 's/123/456/' # Bigger numbers are better
>       # -re 's/foo/bar/' # Disable for now
>     )
>
>     if [ -r /some/file ]
>     then
>       args+=(-re 's/new/old/')
>     fi
>
>     echo abc123 | sed "${args[@]}"
>
> For zsh you can just use $args to reference it, the way I wrote it 
> above will work in bash as well.
>
That is most clever!  As it is, when I have a long set of seds, I copy 
the whole thing, comment it, and then add comments (within the comments) 
so as to inform myself what the seds are doing since I tend to forget 
all the syntactic details. You method permits the comments where they 
naturally belong.  Mind, it seems to me that comments after a line wrap 
would be easy to implement but that's not what we have.  Thanks again.




  reply	other threads:[~2022-10-15  2: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
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 [this message]
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=a24ea038-0a73-cc86-25af-239738dd6de3@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).