zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Oliver Kiddle" <opk@u.genie.co.uk>,
	"Zsh workers" <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: new _zpty, _getconf and improved _compdef
Date: Thu, 9 Mar 2000 14:52:14 +0300	[thread overview]
Message-ID: <001301bf89bd$e96a1110$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <38C78D7B.10FB6242@u.genie.co.uk>

>
> If anyone feels the need to implement getconf as a builtin

Please, do not do it. This must remain system-specific, not shell-specific.

If anybody absolutely needs access to (sys|path)conf from inside of Zsh - better, use
associative array to hold values. Even in this case - can anybody be sure, that all
possible conf parameters are covered?

-andrej


  reply	other threads:[~2000-03-09 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-09 11:39 Oliver Kiddle
2000-03-09 11:52 ` Andrej Borsenkow [this message]
2000-03-09 12:46 Sven Wischnowsky

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='001301bf89bd$e96a1110$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=opk@u.genie.co.uk \
    --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).