From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH 2/3] Completion/Unix/Command/_git: fix shortlog completer
Date: Thu, 25 Apr 2013 23:18:42 +0530 [thread overview]
Message-ID: <CALkWK0nRVKVdJyep31niA1We-X4wrhjst-iA+is7tfY4ViLROQ@mail.gmail.com> (raw)
In-Reply-To: <87mwsm3ho5.fsf@ft.bewatermyfriend.org>
Frank Terbeck wrote:
> I stumbled across a message on the git development mailing list, in
> which Ramkumar basically falls for Felipe's ramblings. And since I'm not
> interested in shouting matches with that guy I'll just leave him be. In
> related news, I just pushed this commit to the central repository as
> well, because Ramkumar - on the git mailing list - stated that he'll
> drop working on this particular completion immediately.
Hey, you can talk to me about it. I don't know the entire history of
things, but I've seen a few emails in which Felipe causes some
unpleasantness on the list (so yes, I'm roughly aware of his strengths
and weaknesses). I'm just an unbiased observer, and want to work
towards the common good.
Now, I'm a shell-scripting beginner and do not have the expertise to
fully evaluate zsh's completer versus git.git's completer. From my
untrained eyes, zsh's completer looks more complete and comprehensive
but git.git's completer looks terse and less intimidating. There is
definitely a noticeable difference in speed: git.git's completer is
much faster, and there's no doubt about that.
I want to work on the completer without fundamentally difficult
problems (because I can't fix those fundamentally difficult problems).
Speed seems to be a big pain point in zsh's completer, and that seems
to be a very difficult problem to solve (I saw a few list emails about
it). However, it looks like we can gradually make git.git's completer
more comprehensive.
That's all I really have. Can you help me out, and tell me more?
I would really like for us all to work on one completer.
next prev parent reply other threads:[~2013-04-25 17:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 12:56 [PATCH 0/3] Completion/Unix/Command/_git: misc fixes Ramkumar Ramachandra
2013-04-20 12:56 ` [PATCH 1/3] Completion/Unix/Command/_git: add a couple of browsers Ramkumar Ramachandra
2013-04-20 12:56 ` [PATCH 2/3] Completion/Unix/Command/_git: fix shortlog completer Ramkumar Ramachandra
2013-04-20 13:03 ` Nikolai Weibull
2013-04-20 15:05 ` Frank Terbeck
2013-04-20 17:13 ` Ramkumar Ramachandra
2013-04-20 17:35 ` Bart Schaefer
2013-04-20 17:50 ` Ramkumar Ramachandra
2013-04-25 12:42 ` Frank Terbeck
2013-04-25 13:11 ` Nikolai Weibull
2013-04-25 18:12 ` Ramkumar Ramachandra
2013-04-25 17:48 ` Ramkumar Ramachandra [this message]
2013-04-25 19:06 ` Frank Terbeck
2013-04-27 8:56 ` Nikolai Weibull
2013-04-27 9:01 ` Nikolai Weibull
2013-04-28 14:30 ` Nikolai Weibull
2013-05-11 16:55 ` Nikolai Weibull
2013-05-12 17:48 ` Peter Stephenson
2013-04-27 10:22 ` Ramkumar Ramachandra
2013-04-27 11:27 ` Frank Terbeck
2013-04-20 12:56 ` [PATCH 3/3] Completion/Unix/Command/_git: branch.*.pushremote, remote.pushdefault Ramkumar Ramachandra
2013-04-21 10:16 ` [PATCH 0/3] Completion/Unix/Command/_git: misc fixes Frank Terbeck
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=CALkWK0nRVKVdJyep31niA1We-X4wrhjst-iA+is7tfY4ViLROQ@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=ft@bewatermyfriend.org \
--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).