From: DervishD <raul@pleyades.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: Strange problem with ulimit
Date: Mon, 10 Nov 2003 11:57:20 +0100 [thread overview]
Message-ID: <20031110105720.GB23263@DervishD> (raw)
In-Reply-To: <1031109212136.ZM14473@candle.brasslantern.com>
Hi Bart :)
* Bart Schaefer <schaefer@brasslantern.com> dixit:
> [Hmm, I don't seem to have received the first message in this thread.]
That's a problem that I have had frequently with this list.
Sometimes I don't receive posts :(( Lately that seemed to be solved
(for me, at least)...
> } I can reproduce it here, with zsh 4.0.7. I've took a look at the
> } sources, with no success :((
> That's because the code in question is in the file "bltinmods.list"
> which is generated at configure time and then #include'd by init.c.
OK ;))
> The "ulimit" builtin is not a full-fledged builtin -- it's supplied by
> the zsh/rlimits module.
I knew that. What I didn't know was that modules weren't loaded
when zsh was invoked as sh. Which, on the other hand, makes sense...
> Modules are zmodload'd automatically at startup only when the shell is
> invoked as zsh. This is to prevent clashes with command and variable
> names used e.g. by "sh" scripts that are expecting a clean namespace.
Does that mean that you can zmodload zsh/rlimits and have again
the builtin?
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2003-11-10 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 9:50 David Gómez
2003-11-09 16:18 ` DervishD
2003-11-09 21:21 ` Bart Schaefer
2003-11-10 10:24 ` David Gómez
2003-11-10 16:42 ` Bart Schaefer
2003-11-10 19:23 ` David Gómez
2003-11-10 10:57 ` DervishD [this message]
2003-11-10 16:42 ` 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=20031110105720.GB23263@DervishD \
--to=raul@pleyades.net \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).