zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: #compdef -k menu-select glitch in 3.1.9
Date: Tue, 6 Jun 2000 05:16:26 +0000	[thread overview]
Message-ID: <1000606051626.ZM194@candle.brasslantern.com> (raw)
In-Reply-To: <1000606045656.ZM65@candle.brasslantern.com>

On Jun 6,  4:56am, Bart Schaefer wrote:
} Subject: #compdef -k menu-select glitch in 3.1.9
}
} If I explicitly invoke `zle -C _widget .menu-select _widget' then I do get
} menu-select behavior, but for some reason it doesn't work at compinit time.

I found out what's happening: this is partly pilot error on my part, and
partly bad behavior from compinit.

I have two files in my $fpath both named _widget with different #compdef
tags.  compinit processes both of them, in $fpath order, which means that
the #compdef that wins doesn't match the function that gets autoloaded.  I
expected it to only process the one that would actually be autoloaded.

Should we stick a `(( $+functions[$_i_file] )) && continue' or equivalent
into the `for _i_file in ...' loop in compinit?

The other puzzler, with the beeping, still remains.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-06-06  5:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-06  4:56 Bart Schaefer
2000-06-06  5:16 ` Bart Schaefer [this message]
2000-06-06  9:48 Sven Wischnowsky
2000-06-06 17:52 ` 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=1000606051626.ZM194@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).