zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Frank Gallacher <franxg@gmail.com>,
	"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Alias call in function fails...
Date: Mon, 29 Jun 2020 18:24:56 +0200	[thread overview]
Message-ID: <CAKc7PVB_0V=f4UCmbOeb=WvR9ewdUvNW0PtrGGOdJFvBHq_3Pw@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3TcSbwBn4cxFoTLs7Cr2bWNQ_k_Zh9kjgMMPDrvipGHWg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

I once was testing with Eric on IRC and the aliases sometimes do work
within the same file. I think that the distance between the definition and
usage is important. I wonder why? Are the scripts (zshrc in this case)
being parsed in an advancing manner?


On Tue, 23 Jun 2020 at 01:25, Mikael Magnusson <mikachu@gmail.com> wrote:

> On 6/22/20, Frank Gallacher <franxg@gmail.com> wrote:
> > Greetings,
> >
> > I have a function:
> >
> [...]
> >
> > Which calls an alias:
> >
> > alias dumpit='hexdump -C -n 128'
> >
> > It works fine in bash, but with zsh now I get:
> >
> > :::::::: test.txt ::::::::
> > dumpall:11: command not found: dumpit
> >
> > Am I doing something wrong???
>
> Yes, don't use aliases for anything but interactive usage. Eg if you
> want to use dumpit in a script, make it be a function:
> dumpit() { hexdump -C -n 128 }
>
> Aliases are expanded on parse time, which means aliases defined in a
> file won't be usable in that same file. (Because it is parsed in its
> entirety before any of the code is actually run).
>
> --
> Mikael Magnusson
>


-- 
Sebastian Gniazdowski
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zinit
Blog: http://zdharma.org

  parent reply	other threads:[~2020-06-29 16:26 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
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 [this message]
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='CAKc7PVB_0V=f4UCmbOeb=WvR9ewdUvNW0PtrGGOdJFvBHq_3Pw@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=franxg@gmail.com \
    --cc=mikachu@gmail.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).