zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: 4.0.1-pre-1
Date: Fri, 16 Feb 2001 15:56:32 +0100 (MET)	[thread overview]
Message-ID: <200102161456.PAA28318@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 14 Feb 2001 17:32:57 +0000


Bart Schaefer wrote:

> ...
> 
> We appear to have given up on compadd flags, 8866.

Yes, at least I have (although I admit that I had completely forgotten 
about this).  There are already several people out there who have used 
one of the 3.1.x versions.  Not many of them will have used compadd,
though.

> ...
> 
> Again not a bug, but we discussed making $_is_gnu more generic, 10998.

This still sounds like a good idea, but there wasn't any discussion.

And there's more to this, as I've just discovered, while looking
through the guide.  It has to do with services.  They should allow one 
to say:

  compdef myzcat=zcat

to make completion for myzcat do exactly the same as for zcat.  And it 
almost works, but _zcat uses $_is_gnu and tries calling $words[1] for
that.  If the myzcat really behaves like the GNU-zcat this might be
ok, but maybe it doesn't duplicate its behaviour enough to make the
test succeed even if it otherwise allows (almost) the same as the
GNU-version.  One could say that the user then gets what he deserves
(for not using `compdef myzcat=gzcat'), but I thought I should at
least mention it here...

The patch below, btw, has to do with services, too.  The `compdef myzcat=gzcat'
didn't really work because gzcat itself uses the service `gunzip' and
compdef didn't test that.  It does now.

> ...
> 
> There was some discussion of better glob-option handling for _path_files
> in 13131.

Hmhm.  I think I was just too tired at the time.

Just as a reminder, it's about bareglobquals being unset by the user.
To handle this we would have to make _main_complete store that option
setting where _path_files can look at it.  That raises the question if 
we should make _main_complete save all previous option settings in
some hash.  And then we could remove _(un|)set_options (and the
remarks about them from the manual and the Guide) and make _options
use a style to decide if it should use only set or unset options.
With the parameter module saving the option settings is much less
expensive than it was when we decided not to do that.  Is anyone
against making these changes?

> ...
> 
> There was an apparent race condition discussed in 13297 and 13298.

I still can't reproduce that.


Bye
 Sven

Index: Completion/Core/compinit
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/compinit,v
retrieving revision 1.15
diff -u -r1.15 compinit
--- Completion/Core/compinit	2001/02/13 03:16:55	1.15
+++ Completion/Core/compinit	2001/02/16 14:42:52
@@ -249,6 +249,7 @@
 	  cmd="${i%%\=*}"
 	  svc="${i#*\=}"
           func="$_comps[${(k)_services[(R)$svc]:-$svc}]"
+          (( $+_services[$svc] )) && svc=$_services[$svc]
 	  [[ -z "$func" ]] &&
 	    func="${_patcomps[(K)$svc][1]:-${_postpatcomps[(K)$svc][1]}}"
           if [[ -n "$func" ]]; then

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2001-02-16 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16 14:56 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-14 13:43 4.0.1-pre-1 Sven Wischnowsky
2001-02-15  6:30 ` 4.0.1-pre-1 Andrej Borsenkow
2001-02-14 12:35 4.0.1-pre-1 Peter Stephenson
2001-02-14 12:55 ` 4.0.1-pre-1 Andrej Borsenkow
2001-02-14 17:32 ` 4.0.1-pre-1 Bart Schaefer
2001-02-17  0:53   ` 4.0.1-pre-1 Peter Stephenson
2001-02-18  1:43     ` 4.0.1-pre-1 Bart Schaefer
2001-02-19  6:15       ` 4.0.1-pre-1 Andrej Borsenkow
2001-03-06  7:57   ` 4.0.1-pre-1 Andrej Borsenkow
2001-03-06  8:44 ` 4.0.1-pre-1 Alexandre Duret-Lutz
2001-03-06 10:31   ` 4.0.1-pre-1 Peter Stephenson
2001-03-06 14:24     ` 4.0.1-pre-1 Alexandre Duret-Lutz

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=200102161456.PAA28318@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).