zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: is variable with variable name possible?
Date: Mon, 04 Apr 2011 07:26:17 -0700	[thread overview]
Message-ID: <110404072617.ZM9904@torch.brasslantern.com> (raw)
In-Reply-To: <BANLkTikVWk9t4h3APSkFN7tOKyjTHJgmJg@mail.gmail.com>

On Apr 4,  3:51pm, Jeremie Roquet wrote:
} Subject: Re: is variable with variable name possible?
}
} 2011/4/4 Jeremie Roquet <arkanosis@gmail.com>:
} > 2011/4/4 zzapper <david@tvis.co.uk>:
} >> somevar=$(pwd)
} >>
} >> but I want somevar to be a variable name
} >
} > $ eval "$somevar=$(pwd)"
} 
} Actually, the quotes aren't even needed:
} 
} $ eval $somevar=$(pwd)

If $(pwd) has spaces in the directory name, this is going to fail.  So
you do need quotes, but a different kind:

    eval $somevar='$(pwd)'

For scalars (but not array assignments) you can also do

    typeset -g $somevar=$(pwd)

You can also use ${somevar::=$(pwd)} anywhere that you'd reference the
value of $somevar, including the no-op command:

    : ${somevar::=$(pwd)}

That also works for array assignments if you explicitly split:

    : ${(As:/:)somevar::=$(pwd)}
    print -l $somevar

Note though that here the stuff after the = is joined with the first
character of $IFS before being split, so to copy one array to another
you have to be careful.  Also note that without the (A) the split is
applied to the expansion after the assignment.


  parent reply	other threads:[~2011-04-05  7:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 13:37 zzapper
2011-04-04 13:48 ` Jérémie Roquet
2011-04-04 13:51   ` Jérémie Roquet
2011-04-04 14:13     ` zzapper
2011-04-04 14:26     ` Bart Schaefer [this message]
2011-04-05  8:31       ` Bart Schaefer
2011-04-04 14:06   ` Stephane Chazelas
2011-04-04 14:25     ` Mikael Magnusson
2011-04-04 16:28       ` Stephane Chazelas
2011-04-04 16:34         ` Mikael Magnusson
2011-04-04 20:50           ` Stephane Chazelas
2011-04-04 22:32             ` Mikael Magnusson
2011-04-05 18:39               ` Stephane Chazelas
2011-04-05  2:54             ` Aaron Davies
2011-04-05  3:54               ` Phil Pennock
2011-04-05  4:04             ` ZyX
2011-04-05  4:10             ` ZyX
2011-04-04 14:33     ` Jérémie Roquet

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=110404072617.ZM9904@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).