From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: order of sourcing
Date: Wed, 18 Jan 2023 13:23:07 -0800 [thread overview]
Message-ID: <CAH+w=7biVwWopQ8LQD6zr16BHeUUTBDf46zPvmkpQ5oVspRcRw@mail.gmail.com> (raw)
In-Reply-To: <d72491b0-aafc-667f-d31f-fb7e021b51a7@eastlink.ca>
On Tue, Jan 17, 2023 at 1:48 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> On 2023-01-17 13:34, Bart Schaefer wrote:
> > -- also makes me suspect that Ray has more than one function per file,
> > which further messes with autoload.
> True. I have help screens as subsidiary functions but defined within
> the file named after the function itself.
That should be fine as long as you never want to run the subsidiary
function without first running the primary function.
> Mind I'm happy just sourcing everything, but getting
> them in order is the small issue mentioned.
It does seem odd that the order of sourcing should matter, unless the
files so sourced actually do something other than defining functions.
E.g., do they either execute conditional expressions, or define
aliases that are then used in other files?
next prev parent reply other threads:[~2023-01-18 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-01-18 23:44 ` Ray Andrews
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
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='CAH+w=7biVwWopQ8LQD6zr16BHeUUTBDf46zPvmkpQ5oVspRcRw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).