zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: Strange problem with ulimit
Date: Mon, 10 Nov 2003 16:42:06 +0000	[thread overview]
Message-ID: <1031110164206.ZM15639@candle.brasslantern.com> (raw)
In-Reply-To: <20031110102410.GA15979@fargo>

On Nov 10, 11:24am, David wrote:
}
} On Nov 09 at 09:21:36, Bart Schaefer wrote:
} > [Hmm, I don't seem to have received the first message in this thread.]
} 
} I won't be surprised that some messages are lost at the mail servers.

Actually it appears that my mail client had a killfile-type filter on
the iso-8859-15 character set, which I must have installed _years_ ago
(as in, pre-1996) and forgotten about.

} > Even though that module is normally linked to
} > the base executable (rather than dynamically loaded),
} 
} Are there more builtins with this behavior?

There are lots of builtins that are supplied by modules,but zsh/rlimits
appears to be the only module documented as if it's always builtin.  So,
"limit" and "unlimit"  are also affected.

Incidentally, in reference to the original article on this thread, zsh
does not have a bash emulation mode.  It emulates plain "sh" (as in,
the original Bourne shell from before the GNU project even existed),
ksh, and (approximately) csh.  It happens to treat "emulate bash" as
"emulate sh" but that doesn't get you all that far.


  reply	other threads:[~2003-11-10 16:42 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 [this message]
2003-11-10 19:23         ` David Gómez
2003-11-10 10:57     ` DervishD
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=1031110164206.ZM15639@candle.brasslantern.com \
    --to=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).