zsh-users
 help / color / mirror / code / Atom feed
From: Perry Smith <pedz@easesoftware.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Alias call in function fails...
Date: Wed, 24 Jun 2020 07:55:46 -0500	[thread overview]
Message-ID: <C9FC8FC2-81D6-495B-8089-D567EC9D9DFC@easesoftware.com> (raw)
In-Reply-To: <20200624092804.GA19280@tarpaulin.shahaf.local2>



> On Jun 24, 2020, at 4:28 AM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> 
> Perry Smith wrote on Tue, Jun 23, 2020 at 19:47:05 -0500:
>> 
>> 
>>> On Jun 23, 2020, at 6:43 PM, Bart Schaefer <schaefer@brasslantern.com> wrote:
>>> 
>>> On Tue, Jun 23, 2020 at 4:30 PM Perry Smith <pedz@easesoftware.com> wrote:
>>>> 
>>>> Ahh… ok.  Thank you.  I remember reading that now (before your changes)
>>>> but didn’t really ingest it.
>>> 
>>> The more classic example is something excessively abbreviated such as
>>> 
>>> % alias -g L='|less'
>>> % find ~ -name \*.gif L
>> 
>> For me, I think I would more likely do something like:
>> 
>> % alias -g opts=“-a -b -c -d”
>> % foo opts path/to/file
>> 
>> But, given my relative inexperience with zsh, I not think about alias -g and
>> would likely do:
>> 
>> % opts=“-a -b -c -d”
>> % foo $opts path/to/file
>> 
>> or use alias -g to save a really long ugly path.  etc.
>> 
> 
> The second example won't work with the default settings (see
> http://zsh.sourceforge.net/FAQ/zshfaq03.html#l18).  The standard
> workaround is to use an array variable, and I'd like the example to show
> a use of aliases that can't easily be achieved without them.  (This also
> goes for Grant's example.)

Ah… yes, you are right of course.  It demonstrates that my mind is still
using bash.


  reply	other threads:[~2020-06-24 12:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 12:49 Frank Gallacher
2020-06-22 23:23 ` Mikael Magnusson
2020-06-23  8:37   ` Andreas Kusalananda Kähäri
2020-06-23  9:14     ` Peter Stephenson
2020-06-23  9:55     ` Mikael Magnusson
2020-06-23 11:28       ` Andreas Kusalananda Kähäri
2020-06-23 12:04         ` Daniel Shahaf
2020-06-23 12:46           ` Perry Smith
2020-06-23 13:10             ` Kamil Dudka
2020-06-23 16:03               ` Bart Schaefer
2020-06-23 21:14                 ` Perry Smith
2020-06-23 22:54                   ` Daniel Shahaf
2020-06-23 23:29                     ` Perry Smith
2020-06-23 23:43                       ` Bart Schaefer
2020-06-24  0:47                         ` Perry Smith
2020-06-24  9:28                           ` Daniel Shahaf
2020-06-24 12:55                             ` Perry Smith [this message]
2020-06-23 23:40                     ` Bart Schaefer
2020-06-24 10:10                       ` Daniel Shahaf
2020-06-24 10:47                         ` Daniel Shahaf
2020-06-24  2:58                   ` Grant Taylor
2020-06-29 16:24   ` Sebastian Gniazdowski
2020-06-29 16:55     ` Bart Schaefer
2020-06-30  4:02       ` 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=C9FC8FC2-81D6-495B-8089-D567EC9D9DFC@easesoftware.com \
    --to=pedz@easesoftware.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=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).