From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: add more ulimit extensions from BSDs
Date: Thu, 31 Oct 2013 11:33:07 +0000 [thread overview]
Message-ID: <20131031113307.30f95260@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <131030082930.ZM8009@torch.brasslantern.com>
On Wed, 30 Oct 2013 08:29:30 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Oct 30, 10:59am, Peter Stephenson wrote:
> } Subject: Re: PATCH: add more ulimit extensions from BSDs
> }
> } > while sh's ulimit -a describes them as
> } >
> } > kqueues (-k) unlimited
> } >
> } > and DragonFly only has
> } >
> } > posixlocks (-k) unlimited
> }
> } Thanks for the changes... are we sure that posixlocks and kqueues are
> } mutually incompatible, or should we move one to -K via #define's if both
> } exist?
>
> It makes me nervous to have two limits on the same option letter even if
> they are not mutually incompatible. Lots of people (including me) have
> "portable" RC files.
Yes, having versions of zsh incompatible with one another is probably a
much bigger problem than having it incompatible with other shells in a
case where some form of incompatibility is unavoidable.
In the absence of other suggestions(*) I think I'll just turn posixlocks
itno -K (but note the incompatibility in the manual).
pws
(*) I nearly said "absent other suggestions". What is the world coming
to? (**)
(**) I don't need a "tongue in cheek" marker, do I? They take ages to
draw.
next prev parent reply other threads:[~2013-10-31 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 1:33 Stefan Neudorf
2013-10-30 10:59 ` Peter Stephenson
2013-10-30 15:29 ` Bart Schaefer
2013-10-31 11:33 ` Peter Stephenson [this message]
2013-10-31 20:10 ` Peter Stephenson
2013-10-31 23:09 ` PATCH: " Stefan Neudorf
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=20131031113307.30f95260@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@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).