From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Somewhere between modules-bltn and zmodload ....
Date: Fri, 30 Apr 1999 11:19:59 -0700 [thread overview]
Message-ID: <990430111959.ZM18267@candle.brasslantern.com> (raw)
In-Reply-To: <199904300856.KAA21857@beta.informatik.hu-berlin.de>
On Apr 30, 10:56am, Sven Wischnowsky wrote:
} Subject: Re: Somewhere between modules-bltn and zmodload ....
}
} > Maybe this is possible and I've just missed it.
} >
} > Why is there no compile-time option equivalent to runtime "zmodload -a ..."?
}
} Just add it to xmods.conf.
Ah, OK ... and duh.
} (I don't understand this name, btw.)
I think the x is for "extension." (But why isn't modules-bltn called
"bmods.conf" or something? Maybe we should clean all this up, too.)
Here's another question:
zagzig% zmodload -ac
post after (compctl)
post between (compctl)
post suffix (compctl)
post prefix (compctl)
zagzig% zmodload -uc compctl after
zmodload: compctl: no such condition
zagzig% zmodload -ac
post between (compctl)
post suffix (compctl)
post prefix (compctl)
zagzig% zmodload -uc compctl between || echo Failed
zmodload: compctl: no such condition
Failed
zagzig% zmodload -ac
post suffix (compctl)
post prefix (compctl)
Is is really the right behavior that zmodload go on and unload the rest
of the conditions listed on the command line after one has failed? Or
should it stop when it gets to a failure? I suppose the analogy is to
"rm", but I was a bit surprised by it.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-04-30 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-30 8:56 Sven Wischnowsky
1999-04-30 18:19 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-05-03 7:36 Sven Wischnowsky
1999-04-30 7:12 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=990430111959.ZM18267@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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).