zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: completers using zstat don't work with zmodload -F zsh/stat
Date: Wed, 27 Jul 2011 11:18:29 -0700	[thread overview]
Message-ID: <110727111829.ZM22827@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3STCr48Cv+vSVXK+nAcpUv_UbzBwQ_4dt+CKzeRqpqqig@mail.gmail.com>

On Jul 27,  6:44pm, Mikael Magnusson wrote:
} Subject: Re: completers using zstat don't work with zmodload -F zsh/stat
}
} # alias zstat='builtin stat'
} # rm $fpath[3].zwc*
} removed `/usr/local/share/zsh/4.3.12-dev-1/functions.zwc'
} removed `/usr/local/share/zsh/4.3.12-dev-1/functions.zwc.old'
} # for a ($fpath) {[ -w $a:r -a $a/_*(N[1]) ] && zrecompile -p -U -z
} $a.zwc $a/_*}
} re-compiling /usr/local/share/zsh/4.3.12-dev-1/functions.zwc: succeeded
} 
} % umount <tab>
} _canonical_paths_add_paths:6: no such builtin: stat

This must be happening because _canonical_paths_add_paths isn't actually
defined until _canonical_paths is executed, so the -U option to zcompile
doesn't have a chance to come into effect.

This is going to be a problem with any completion source file that has
multiple embedded function definitions.

It MIGHT help to both use "zcompile -a" and also change _canonical_paths
from using

    _canonical_paths_add_paths () {
      ...
    }

to using the load-once paradigm

    (( $+functions[__canonical_paths_add_paths] )) ||
    _canonical_paths_add_paths () {
      ...
    }

but I'm not confident of that.


  reply	other threads:[~2011-07-27 18:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 19:09 Mikael Magnusson
2011-07-27  8:20 ` Bart Schaefer
2011-07-27  9:04   ` Mikael Magnusson
2011-07-27 16:38     ` Bart Schaefer
2011-07-27 16:44       ` Mikael Magnusson
2011-07-27 18:18         ` Bart Schaefer [this message]
2011-07-27 18:24           ` Mikael Magnusson
2011-07-27 19:32             ` 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=110727111829.ZM22827@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).