git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Ben Clifford <benc@hawaga.org.uk>, git@vger.kernel.org
Subject: Re: latest stg/git commandline completions code
Date: Tue, 25 Oct 2005 19:05:26 +0200	[thread overview]
Message-ID: <200510251905.27768.blaisorblade@yahoo.it> (raw)
In-Reply-To: <b0943d9e0510250924g3f5d9281r@mail.gmail.com>

On Tuesday 25 October 2005 18:24, Catalin Marinas wrote:
> On 25/10/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
> > The best idea seems to write a Python script sourcing the Stgit source
> > (stgit/main.py to get commands, and then loading each class and iterating
> > over the "options" module member).

> I can add a function in stgit/main.py which would list the options.
> The tla-completion generates a file listing a command with its option
> on every line:

>   push -a -all -n --number -t --to --reverse --undo -h --help
>   ...

> Since I don't know much about the bash completion, let me know of the
> format you'd prefer.
Ok, I'll look into that. Probably it'll be around "opts_push="-a --all -n 
--number...", i.e. this one works fine, through name indirection, i.e. you 
say "expand the var which name is given by this expr".

> > Btw, what do you think about speeding up completions by reimplementing
> > things like "stg applied" or "stg unapplied" via cat (as noted in the
> > comments at the beginning of the script)? Tab completions can easily
> > livelock a shell on a busy system, so it's worthy speeding the thing up.

> In general, it is better to use the stg commands but the repository
> structure won't probably change for a long time
Ok.
> and it's OK to 
> optimise (if the speed improvement is visible).
I believe it is, yes.
> Anyway, these 
> particular commands are pretty fast (they behave like cat) but there
> are others which are slower (usually the commands involving calls to
> the GIT tool).

They _would_ behave like cat, except that Python is slow enough. Half a second 
on a (almost) idle system means seconds and seconds on a busy system, and 
it's pretty frequent that when I don't wait enough for an op. to complete I 
get a traceback from the import statements, which haven't been completed. 

And let's leave Gentoo's emerge alone - I'd say imports can take up to a 
minute.
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it

  reply	other threads:[~2005-10-25 17:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.60.0510251222510.8565@mundungus.clifford.ac>
2005-10-25 14:42 ` latest stg/git commandline completions code Blaisorblade
2005-10-25 15:18   ` Catalin Marinas
2005-10-25 15:53     ` Blaisorblade
2005-10-25 16:24       ` Catalin Marinas
2005-10-25 17:05         ` Blaisorblade [this message]
2005-10-26 11:34           ` Catalin Marinas
2005-10-26 16:14             ` Blaisorblade
2005-11-08 10:16   ` Ben Clifford
2005-11-09 22:23     ` Petr Baudis
2005-11-10  1:59       ` Ben Clifford
2005-11-10  9:40         ` Petr Baudis
2005-11-16  3:35           ` Ben Clifford
2005-11-10  2:03       ` Ben Clifford
2005-11-10  6:57       ` Ben Clifford

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=200510251905.27768.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=benc@hawaga.org.uk \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.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.
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).