zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Problems with zargs (Was: xargs should be a builtin)
Date: Sat, 14 Apr 2012 10:01:19 -0700	[thread overview]
Message-ID: <120414100119.ZM8559@torch.brasslantern.com> (raw)
In-Reply-To: <20120413201325.64cfcd1f@pws-pc.ntlworld.com>

On Apr 13,  8:13pm, Peter Stephenson wrote:
} Subject: Re: Problems with zargs (Was: xargs should be a builtin)
}
} On Fri, 13 Apr 2012 08:43:50 -0700
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > One concern I have is that this may have changed behavior with respect
} > to aliases.  Does the first word of $call need to be unquoted?
} 
} You're probably right that it's changed the behaviour.  I'm not sure if
} it was ever clear that aliases would be expanded, but there's no reason
} not to restore it.

I've just checked this against a few older versions of the shell and it
appears that aliases were never expanded.  So we can either leave it as
it is, or change it to allow aliases in the command position ... but
there is no way I can see to allow *global* aliases to expand without
breaking quoting of the rest of the arguments.

So perhaps the status quo is best maintained.

-- 
Barton E. Schaefer


  parent reply	other threads:[~2012-04-14 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  7:31 xargs should be a builtin Dave Yost
2012-04-11  7:44 ` Frank Terbeck
2012-04-11 10:06   ` Problems with zargs (Was: xargs should be a builtin) Stephane Chazelas
2012-04-11 16:15     ` Peter Stephenson
2012-04-12  9:28       ` Stephane Chazelas
2012-04-12 19:33         ` Peter Stephenson
     [not found]           ` <CAH+w=7Z5pUmqxpURyHMA5FX3hMGoyQeYwbC1N7AO6Ow-D=P-gw@mail.gmail.com>
     [not found]             ` <20120413201325.64cfcd1f@pws-pc.ntlworld.com>
2012-04-14 17:01               ` Bart Schaefer [this message]
2012-04-12 23:05     ` 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=120414100119.ZM8559@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).