zsh-users
 help / color / mirror / code / Atom feed
From: Steve Dondley <s@dondley.com>
To: zsh-users@zsh.org
Subject: Re: How do I go about finding reason for slow tab completion with taskwarrior "task" command?
Date: Sat, 8 Jul 2023 12:55:45 -0400	[thread overview]
Message-ID: <2F30F7D2-1BCC-4D54-A297-E80DA74DF414@dondley.com> (raw)
In-Reply-To: <F2E7F8B2-6031-4E2F-9639-F00485705FE6@dondley.com>

The problem had to do with a custom hook I wrote for taskwarrior. Not sure why the hook is getting fired but it has nothing to do with zsh.

But I’m still curious to know where the actual _task completion script is. How do I find the actual completion script for task command?



> On Jul 8, 2023, at 11:56 AM, Steve Dondley <s@dondley.com> wrote:
> 
> I’m using taskwarrior on latest version of Debian stable (bookworm).
> 
> It takes about 2 seconds for its “task” command to respond to tab completion, making it no better than typing things in directly for most commands.
> 
> Git completion works well with very little delay. So I have to assume it’s something related to taskwarrior.
> 
> The completion script can be found here: https://github.com/GothenburgBitFactory/taskwarrior/blob/develop/scripts/zsh/_task and I can see it on my machine at /usr/share/zsh/site-functions/_task
> 
> What’s a good method for determine what is slowing things down? I was thinking about commenting out various part of the script through trial and error. But if I rename the _task file and start a new zsh process, completion still works. So I’m not sure how to get that _task script reloaded easily.
> 
> Can someone head me in the right direction?  
> 
> 
> 
> 
> 
> 
> 
> 



  reply	other threads:[~2023-07-08 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 15:56 Steve Dondley
2023-07-08 16:55 ` Steve Dondley [this message]
2023-07-08 17:12 ` Lawrence Velázquez

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=2F30F7D2-1BCC-4D54-A297-E80DA74DF414@dondley.com \
    --to=s@dondley.com \
    --cc=zsh-users@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).