zsh-workers
 help / color / mirror / code / Atom feed
From: hzoli@cs.elte.hu (Zoltan Hidvegi)
To: zsh-workers@math.gatech.edu (zsh-workers)
Subject: Re: Z-Shell Frequently-Asked Questions (monthly posting)
Date: Thu, 29 Jun 1995 12:20:51 +0100 (MET DST)	[thread overview]
Message-ID: <9506291020.AA28075@turan.elte.hu> (raw)
In-Reply-To: <9119.9506291002@pyro.swan.ac.uk> from "P.Stephenson@swansea.ac.uk" at Jun 29, 95 11:02:31 am

P.Stephenson@swansea.ac.uk wrote:
> hzoli@cs.elte.hu wrote:
> > > B1) Differences from sh and ksh
> > > ...
> > >   Command line substitutions, globbing etc.:
> > 
> > Just one addition here: foo=* assignment assigns the list of files in the
> > current directory as an array to foo if there are at least two matches, or if
> > there is a single file in the directory, foo becames a scalar whose value is
> > the name of that file. Other Bourne shells does not glob the right hand side
> > of assignments. In my releases the default behaviour is to not glob here, but
> > this can be changed by setting the GLOB_ASSIGN option.
> 
> I agree this is a little inconsistent.  What about `foo=(*)', though?
> I use that kind of thing a lot, and it seems obvious to me that it
> should always do globbing --- at least, I tend to think of arguments
> of an array assignment behaving like command line arguments as far as
> word splitting is concerned.  Perhaps it's not obvious to others.  (I
> can do `set -A' but I like assignments to look like assignments.)

Of course I agree, that foo=(*) should do globbing. That's the right way to do
it. I did not change that in my release, moreover I recommend its usage in the
manual.

Zoltan


      reply	other threads:[~1995-06-29 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <26983.9506231110@pyro.swan.ac.uk>
1995-06-28 19:16 ` Zoltan Hidvegi
1995-06-28 19:56   ` Richard Coleman
1995-06-29 10:02   ` P.Stephenson
1995-06-29 11:20     ` Zoltan Hidvegi [this message]

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=9506291020.AA28075@turan.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=zsh-workers@math.gatech.edu \
    /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).