From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Suggestion for ZSH, who do I send it to?
Date: Wed, 17 Dec 2014 17:53:05 +0000 [thread overview]
Message-ID: <20141217175305.23e73179@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <141217090044.ZM567@torch.brasslantern.com>
On Wed, 17 Dec 2014 09:00:44 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> } My suggestion is to add a few options to the sysread and syswrite
> } builtins that come stock with ZSH in the system module:
>
> If this is a change that means these options would not work when a
> particular GNU library is not available, then it would be better to
> add them a different way so that it's possible to test beforehand
> whether they are available. I don't think the module "features"
> mechanism has granularity below the level of a new builtin (i.e., I
> don't think you can use features to test for individual options).
The "zsystem supports" command was added to this module for this
purpose. "zsystem supports anyoldrubbish" simply returns status 1
unless the zsystem module has been provided with an internal feature
called anyoldrubbish. It's not visible at the zmodule interface,
however; you have to load the module and run the command.
Explicitly linking against GNU libraries might have legal consequences.
We print a warning when we do this with libgdbm as it means the binary
is covered by the GNU public license (as they call it). It depends on
the licence (as I call it) for the library whether this would apply
here.
pws
P.S. Tests reveal zsystem does not currently support anyoldrubbish.
next prev parent reply other threads:[~2014-12-17 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 15:36 Micah Waddoups
2014-12-17 17:00 ` Bart Schaefer
2014-12-17 17:53 ` Peter Stephenson [this message]
2014-12-17 18:46 Micah Waddoups
2014-12-18 5:23 ` 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=20141217175305.23e73179@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).