zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: more selection
Date: Tue, 21 May 2002 14:11:54 +0100	[thread overview]
Message-ID: <27410.1021986714@csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Tue, 21 May 2002 13:48:32 BST." <20020521124832.GA10428@logica.com>

Oliver Kiddle wrote:
> On Tue, May 21, 2002 at 12:21:27PM +0100, Peter Stephenson wrote:
> 
> > only with zle -F, so that part could be done without the module if we
> > implemented the bash version of `read -t <timeout>'.  It's annoying I
> > picked that letter for polling.)
> 
> If the timeout is considered to be an optional argument, is there
> really any conflict there? The timeout defaulting to zero would 
> give exactly the same as current behaviour so it could be compatible
> with both older zsh and bash/ksh93. right?

Yes, I was wondering about that.  The major objection at the moment is
that zsh's internal handling for options with arguments is awful ---
look at the hacks for dealing with read -k and read -u, similarly
typeset -i/-Z/-R/-L.  (I tried to combine read -k and -u and it took an
effort to work out what was happening.)  I've been hoping for ages
someone would fix this and save me having to do anything.

The neatest thing I can think of is turn ops into a union and do some
more sophisticated form of getopts string processing.  This increases
the stack usage for each execbuiltin() by some considerable amount,
however.  We can probably do something with the value of the individual
option value.  Currently 2 is used for turning off with `+', but scope
for something more.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


      reply	other threads:[~2002-05-21 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 15:33 Peter Stephenson
2002-05-14  9:48 ` Borsenkow Andrej
2002-05-14 10:04   ` Peter Stephenson
2002-05-14 11:37 ` Peter Stephenson
2002-05-21 11:21 ` Peter Stephenson
2002-05-21 12:48   ` Oliver Kiddle
2002-05-21 13:11     ` Peter Stephenson [this message]

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=27410.1021986714@csr.com \
    --to=pws@csr.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).