zsh-users
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane@chazelas.org>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: preserving single quotes
Date: Wed, 28 Sep 2022 11:00:20 +0100	[thread overview]
Message-ID: <20220928100020.tn3debb7jkytyluz@chazelas.org> (raw)
In-Reply-To: <b1f88f62-0dba-92df-d09d-9025c6846551@eastlink.ca>

2022-09-27 20:12:22 -0700, Ray Andrews:
> I've done this before but I can't remember the invocation.
> 
>    $ dd="echo howdy"
> 
>    $ ee=$($=dd); echo $ee
>    howdy
> 
>    $ dd="aptitude search '?name(libreoffice-java-common)'"
> 
>    $ ee=$($=dd); echo $ee
> 
>    $ (no output)
> 
> 
> ... I have to be able to run the aptitude command with the single quotes
> intact.  I've tried every little trick that's worked before but I'm just not
> finding the magic.


Use either:

dd() aptitude search '?name(libreoffice-java-common)'
ee=$(dd)

Or:

dd="aptitude search '?name(libreoffice-java-common)'"
ee=$(eval -- $dd)

Or:

dd=( aptitude search '?name(libreoffice-java-common)' )
# or
dd=(
  aptitude
  search
  '?name(libreoffice-java-common)'
)
# just to show that it's several arguments you want to store in
# that array
ee=$( "$dd[@]" )

$=dd just does $IFS-splitting. If $dd is meant to contain shell code,
you should use eval to evaluate it. But to store code, you
generally use functions not variables. The z and Q parameter
expansion flags can do the same tokenisation and quote removal
as the shell syntax parser does, but I don't think you want to
go there.

-- 
Stephane


  parent reply	other threads:[~2022-09-28 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  3:12 Ray Andrews
2022-09-28  9:10 ` Roman Perepelitsa
2022-09-28 10:00 ` Stephane Chazelas [this message]
2022-09-28 14:32   ` Ray Andrews
2022-09-28 18:49     ` Stephane Chazelas
2022-09-28 19:29       ` Ray Andrews

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=20220928100020.tn3debb7jkytyluz@chazelas.org \
    --to=stephane@chazelas.org \
    --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).