zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: order of sourcing
Date: Sun, 16 Apr 2023 13:22:59 -0700	[thread overview]
Message-ID: <5d48d48c-340b-760b-f307-5613c9aaf081@eastlink.ca> (raw)
In-Reply-To: <ae48cfda-ca79-c0b5-dd7c-3ee889b26ed4@eastlink.ca>


On 2023-04-16 09:48, Ray Andrews wrote:
>
> On 2023-04-16 09:17, Roman Perepelitsa wrote:
>
> $ for aa in *(.); do source $aa; done
>
> ... doing that in my test directory cures the problem, but I still 
> have the problem with my real functions -- I have to re-source 
> function files that call other functions if the called function is 
> sourced latter than the calling function.

Here's the real example:

All functions in the directory are sourced with

$ for aa in *(.); do source $aa; done

... the two functions are 'i' and 'v', with the former calling the later.

4 /aWorking/Zsh/Source/Wk 3 % i zsh

_i:104: permission denied: v

4 /aWorking/Zsh/Source/Wk 3 % . i; i zsh

... All OK.  Could aliases have something to do with it?  I can't 
duplicate the problem with test functions tho.





  reply	other threads:[~2023-04-16 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 16:14 Ray Andrews
2023-04-16 16:17 ` Roman Perepelitsa
2023-04-16 16:48   ` Ray Andrews
2023-04-16 20:22     ` Ray Andrews [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-17 21:07 Ray Andrews
2023-01-17 21:24 ` Roman Perepelitsa
2023-01-17 21:34   ` Bart Schaefer
2023-01-17 21:42     ` Roman Perepelitsa
2023-01-17 21:48     ` Ray Andrews
2023-01-18 21:23       ` Bart Schaefer
2023-01-18 23:44         ` Ray Andrews

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=5d48d48c-340b-760b-f307-5613c9aaf081@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).