From: Anthony Fletcher <anthony@bifb.org>
To: zsh-users@zsh.org
Subject: Re: autoload variables
Date: Mon, 30 Aug 2021 12:57:49 -0400 [thread overview]
Message-ID: <CAPT4cGf3xGbvKuhrPVfzKo3FnB_-zb7pRwAs_musjCjS_BfuLw@mail.gmail.com> (raw)
In-Reply-To: <a2b84d0a-1af4-c51c-16fe-957ce84f25c4@necoro.eu>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Mon, 30 Aug 2021 at 12:40, René Neumann <lists@necoro.eu> wrote:
> Am 30.08.21 um 17:22 schrieb Anthony Fletcher:
> > For instance, one variable is to identify the default uplink
> > interface
> >
> > export UPIF=$(ip -4 r | sed -n -e '/^default/ s/^default.*dev //; s/
> > .*// p;q' )
> >
> > Useful when I'm debugging the network but not needed otherwise.
>
> Is there a reason you need this as a variable? Would a function
>
> upif() { ip -4 r | ... }
>
> not suffice?
>
> - René
>
A function would work but then you need to run it every time to get the
same value..... and of course the variable is for other commands. Thus
systemcommand $(upif)
In this particular case anything to do with the uplink interface (eg
dump_dhcp6). I guess the function could cache the result for speed.
Anthony.
[-- Attachment #2: Type: text/html, Size: 1280 bytes --]
next prev parent reply other threads:[~2021-08-30 16:58 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 [this message]
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
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=CAPT4cGf3xGbvKuhrPVfzKo3FnB_-zb7pRwAs_musjCjS_BfuLw@mail.gmail.com \
--to=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).