From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org, Felipe Contreras Garza <felipe.contreras@gmail.com>
Subject: Re: Alignment issue with multiple describes
Date: Sun, 21 Apr 2013 17:00:29 -0500 [thread overview]
Message-ID: <CAMP44s0gEpezUyrrNT3BuqRZdyxzXHc4syY5rz5+girBQ2BzdA@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s119Oa-zjAQ9KhwpdNZ7KG-MbwHqgW0FAnc6gj34+vrqQ@mail.gmail.com>
On Sun, Apr 21, 2013 at 3:59 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Sun, Apr 21, 2013 at 1:27 PM, Bart Schaefer
> <schaefer@brasslantern.com> wrote:
>> On Apr 21, 3:31am, Felipe Contreras wrote:
>> [*] Unfortunately the person most familiar with this code has not been
>> active in zsh development for 12 years. On the other hand, it's been
>> 12 years and you're the first person ever to notice/mention this, so it
>> probably doesn't affect anyone's usage of the shell.
>
> It probably does, but nobody cares enough about subtle bugs in zsh.
> Specially since most completions don't use more than one _description,
> the git completion being one exception.
I was watching a video about zsh, and the bug is shown right there:
http://www.youtube.com/watch?v=R6hJ8Nqjgv8&t=22m29s
So you have one thousand watchers of this video alone seeing the bug
in full glory. Probably not the best way to show to newcomers that zsh
is polished.
--
Felipe Contreras
next prev parent reply other threads:[~2013-04-21 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 3:03 Felipe Contreras
2013-04-21 3:03 ` Felipe Contreras
2013-04-21 6:27 ` Bart Schaefer
2013-04-21 8:31 ` Felipe Contreras
2013-04-21 18:27 ` Bart Schaefer
2013-04-21 20:59 ` Felipe Contreras
2013-04-21 21:09 ` Mikael Magnusson
2013-04-21 22:00 ` Felipe Contreras [this message]
2013-04-22 6:59 ` Bart Schaefer
2013-04-22 7:30 ` 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=CAMP44s0gEpezUyrrNT3BuqRZdyxzXHc4syY5rz5+girBQ2BzdA@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).