From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: zle messes up 'words' variable?
Date: Thu, 5 May 2011 23:14:07 +0300 [thread overview]
Message-ID: <BANLkTimTEx_Qu=J_XpJmmsG7rQdkeBFFFg@mail.gmail.com> (raw)
In-Reply-To: <110505123837.ZM19654@torch.brasslantern.com>
On Thu, May 5, 2011 at 10:38 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On May 5, 7:40pm, Felipe Contreras wrote:
> }
> } I asked the question very clearly[1], and nobody seems to be
> } interested in fixing the slowness issue *now*, and trying to improve
> } the performance of the more correct approach *later*.
>
> I don't think there's any useful distinction. "Now" is still relative
> to how soon a new version is installable,
I don't care when the new version will be installable. I can use the
the latest zsh completion on my current system.
> and the level of effort
> required to gut the existing code and produce a faster "seems to work
> but is less correct" version appears comparable to the effort of making
> performance improvements on the correct version.
Perhaps, but that's not how I develop; first make it usable, then
improve it (without breaking it).
> Nikolai put a lot of effort into the current version and as we're all
> volunteers here I can't fault him for not wanting to expend effort on
> gutting it. In the same way that the bash variant is good enough for
> you, what he's contributed is presently working the way he prefers. If
> no one else is available to produce an alternative, well, that happens
> sometimes with a volunteer work force.
That's not the case, I volunteered myself to do that, but what's the
point if he is going to reject the patches?
> If you're not willing to volunteer either, it's not helpful to drive by
> with throwaway denigrations of what "you guys want."
Again, I did volunteer, didn't you see the link on the mail you just replied?
> [1] http://article.gmane.org/gmane.comp.shells.zsh.devel/22480
--
Felipe Contreras
next prev parent reply other threads:[~2011-05-05 20:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 8:26 Felipe Contreras
2011-04-27 9:02 ` Jérémie Roquet
2011-04-27 9:11 ` Felipe Contreras
2011-04-27 9:51 ` Felipe Contreras
2011-04-27 15:06 ` Bart Schaefer
2011-04-28 20:19 ` Felipe Contreras
2011-04-29 3:31 ` Bart Schaefer
2011-05-02 18:11 ` Felipe Contreras
2011-05-03 1:42 ` Bart Schaefer
2011-05-03 8:05 ` Felipe Contreras
2011-05-03 14:39 ` Bart Schaefer
2011-05-03 15:04 ` Bart Schaefer
2011-05-03 17:41 ` Felipe Contreras
2011-05-04 0:39 ` Bart Schaefer
2011-05-05 14:39 ` Felipe Contreras
2011-05-05 16:24 ` Bart Schaefer
2011-05-05 16:40 ` Felipe Contreras
2011-05-05 19:38 ` Bart Schaefer
2011-05-05 20:14 ` Felipe Contreras [this message]
2011-05-05 21:12 ` Nikolai Weibull
2011-05-03 17:36 ` Felipe Contreras
2011-05-04 0:56 ` Bart Schaefer
2011-05-05 14:48 ` Felipe Contreras
2011-05-05 15:50 ` Bart Schaefer
2011-05-05 15:55 ` Felipe Contreras
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='BANLkTimTEx_Qu=J_XpJmmsG7rQdkeBFFFg@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=schaefer@brasslantern.com \
--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).