zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Anthony Fletcher <anthony@bifb.org>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: autoload variables
Date: Mon, 30 Aug 2021 09:49:32 -0700	[thread overview]
Message-ID: <CAH+w=7YPZoCV57+Pfo1noc-+6pfLt-CtZ8NgUiAa8qLEwTh3aA@mail.gmail.com> (raw)
In-Reply-To: <CAPT4cGdBZQDQv8ozkpgYwzm60yqmpJwCKCSPUnLaAj-Rp+F6kg@mail.gmail.com>

On Mon, Aug 30, 2021 at 8:22 AM Anthony Fletcher <anthony@bifb.org> wrote:
>
> Can I autoload these variables as needed?

It would require at least as much overhead to record when and from
where to load the variables as it does to have them defined.

Related to what Roman suggested, you coud also place the variables in
ordinary autoload functions that you run when you need to initialize
them.  Use e.g.

typeset -gx UPIF=$(ip -4 r | sed -n -e '/^default/ s/^default.*dev //;
s/ .*// p;q' )

to have the variable become a global export instead of locals.


  parent reply	other threads:[~2021-08-30 16:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 15:22 Anthony Fletcher
2021-08-30 15:41 ` Roman Perepelitsa
2021-08-30 16:40 ` René Neumann
2021-08-30 16:57   ` Anthony Fletcher
2021-08-30 19:30     ` Mikael Magnusson
2021-08-30 21:34     ` René Neumann
2021-08-30 21:46       ` Bart Schaefer
2021-08-31  0:10         ` Anthony Fletcher
2021-08-31 18:11           ` Roman Perepelitsa
2021-08-31 19:16             ` Bart Schaefer
2021-08-30 16:49 ` Bart Schaefer [this message]
2021-08-31 20:37 ` Marc Chantreux
2021-08-31 21:03   ` Roman Perepelitsa
2021-09-01  8:29     ` Marc Chantreux
2021-09-01  9:51       ` Roman Perepelitsa
2021-09-01 10:06         ` Marc Chantreux
2021-09-01 13:52           ` Bart Schaefer
2021-09-02 23:09         ` Anthony Fletcher
2021-09-03  0:07           ` Bart Schaefer
2021-09-03  6:52           ` Marc Chantreux

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=7YPZoCV57+Pfo1noc-+6pfLt-CtZ8NgUiAa8qLEwTh3aA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=anthony@bifb.org \
    --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).