zsh-workers
 help / color / mirror / code / Atom feed
From: Nikolai Weibull <now@bitwi.se>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: "Benjamin R. Haskell" <zsh@benizi.com>,
	Brett Simmers <swtaarrs@gmail.com>,
	zsh-workers@zsh.org
Subject: Re: Git completion slowness
Date: Fri, 10 Dec 2010 12:37:37 +0100	[thread overview]
Message-ID: <AANLkTi=RiNxd=f4yezvHFd6sVGs-9PvSsM=S=c0p1Ybj@mail.gmail.com> (raw)
In-Reply-To: <87k4jhsx78.fsf@ft.bewatermyfriend.org>

On Fri, Dec 10, 2010 at 12:07, Frank Terbeck <ft@bewatermyfriend.org> wrote:

> We've heard people complaining about _git performance on IRC for a while
> now. I have started to rewrite the _git file related completions some
> time ago, but have since been swamped at work. So that has slowed down
> to a halt.
>
> I'll attach the code to this mail though; maybe it'll be useful to
> someone (search for "Git file listing helpers" to find the helper
> functions). It doesn't have a helper for pathspecs yet, which the
> git-checkout completion (and others) may need.
>
> Also, it's something I experimented with for only a short while. The
> completions did work for me in my limited set of use-cases - they are
> probably not perfect, yet. But they scaled well even on huge
> repositories with many *many* files (like the linux kernel's git
> repository).

> Cc:ing Nikolai, too.

I’ve been rewriting _git for a while now.  I’ve updated all the Main
Porcelain Commands.  I’m currently stuck on something as unimportant
as git-config, but I want to get everything right and I’m doing it all
in man page order.  I’ll hopefully have a delayed Christmas gift for
you all at the beginning of 2011.  I’ll take a look at your changes
and integrate them if they are still applicable.

My main problem right now is that I’m working off of the Debian Zsh
Git repository where I don’t have write permissions.  I’d like to set
up a Zsh Git repository at GitHub so that I can more easily distribute
my changes, but I haven’t had time to look into setting this up.
Perhaps someone can explain how you set up a CVS-to-Git mirror on
GitHub?

I’ll also try to set up zstyles to the effect of allowing you to
disable potentially costly completions.


  parent reply	other threads:[~2010-12-10 11:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 22:06 Brett Simmers
2010-12-09 22:18 ` Benjamin R. Haskell
2010-12-10  0:10   ` Brett Simmers
     [not found]   ` <87k4jhsx78.fsf@ft.bewatermyfriend.org>
2010-12-10 11:37     ` Nikolai Weibull [this message]
2010-12-10 11:49       ` Frank Terbeck
2010-12-10 12:09         ` Nikolai Weibull
2010-12-10 11:54       ` Thomas Gstädtner
2010-12-10 12:11         ` Nikolai Weibull
2010-12-10 12:48   ` Oliver Kiddle
2010-12-10 14:00     ` Nikolai Weibull
2010-12-10 11:29 ` Nikolai Weibull

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='AANLkTi=RiNxd=f4yezvHFd6sVGs-9PvSsM=S=c0p1Ybj@mail.gmail.com' \
    --to=now@bitwi.se \
    --cc=ft@bewatermyfriend.org \
    --cc=swtaarrs@gmail.com \
    --cc=zsh-workers@zsh.org \
    --cc=zsh@benizi.com \
    /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).