From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Trial patch for showing completion in progress
Date: Thu, 09 Sep 2004 14:40:27 +0200 [thread overview]
Message-ID: <4018.1094733627@trentino.logica.co.uk> (raw)
In-Reply-To: <200409091113.i89BDHcG013466@news01.csr.com>
Peter wrote:
> I often want to find out what completion is doing when it goes away for
> a while. Here's a simple patch that helps, though I think there's more
> that can be done. No documentation yet.
In most cases, if it takes a while it is filename completion trying to
look for files in the full path: the stuff which allows /u/l/b to
complete to /usr/local/bin.
> As defined, you set the show-completer style to true in any context
> where you want to show the status. It is examined when each element of
> the completer list is tried. The message is overwritten by any list
> output.
>
> Is there a better place for this? On the whole I think this point is OK.
It depends what you are trying to do. Are you trying to show the
completers or the zstyle context? _main_complete is not the only place
the context is changed so for showing the context, _description or
_setup would be a better place.
> Is there a way of doing this only if completion takes a certain time?
> E.g. store SECONDS as floating point and examine it at certain key
> points?
Why not just stick $SECONDS (as floating point) in PS4 and use
_complete_debug.
I'm not convinced we should be sticking debug stuff like this into
completion unless it really is proven to be useful. I normally prefer to
use a second tty for completion debug output instead of zle. And it
isn't hard to make temporary changes to _main_complete (or whatever) for
debugging.
> Is there a way of removing the zle -M output if the completion produced
> no output?
Either you have to replace compadd with a function or, depending on
where you produce the debug, you might be able to check
compstate[nmatches].
Oliver
next prev parent reply other threads:[~2004-09-09 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 11:13 Peter Stephenson
2004-09-09 12:40 ` Oliver Kiddle [this message]
2004-09-09 12:51 ` Peter Stephenson
2004-09-09 15:30 ` Bart Schaefer
2004-09-09 15:40 ` Peter Stephenson
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=4018.1094733627@trentino.logica.co.uk \
--to=okiddle@yahoo.co.uk \
--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).