zsh-workers
 help / color / mirror / code / Atom feed
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: Mon, 22 Apr 2013 02:30:36 -0500	[thread overview]
Message-ID: <CAMP44s38PiN+VqYgdpD1FegLWQQtPuFa=oReAidynTBPALC5XQ@mail.gmail.com> (raw)
In-Reply-To: <130421235936.ZM6922@torch.brasslantern.com>

On Mon, Apr 22, 2013 at 1:59 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Apr 21,  3:59pm, Felipe Contreras wrote:
> }
> } Anyway, I'm going to label this as a bug the zsh developers are
> } unwilling to fix, and I'm going to work around it by avoiding more
> } than one _description with actual descriptions.
>
> Please don't consider anything I say as speaking for "the zsh developers"
> as a group.  I'm just answering your questions.
>
> On the other hand, if you actually want to encourage someone to work on
> this for you, I think you're going about it the wrong way.

Why should I care? It's not _my_ project the one with bug. It's not my
project the one that ends up in videos showing obviously wrong
behavior.

If it was, I would fix it, regardless of the attitude of some guy on
some mailing list. My users would thank me for it.

> } And BTW, the fact that you have part of the code nobody understands,
> } has touched, or is willing to touch in a decade should be a concern to
> } you.
>
> It is, in fact; but it's not something I'm really in a position to do
> anything about.  I already give zsh as much time as I can (in fact more
> than I probably ought to), and thankfully most of the people I try to
> help out have a better attitude about it than you apparently do.

Perhaps, but that doesn't change the facts, and the direction zsh
development is heading to; oblivion.

If you don't care about that happening, by all means, ignore all the warnings.

> Enjoy your day.  If any further messages from you manage to spark useful
> discussion, you probably should not expect me to Cc you as a courtesy,
> because I have no evidence that I'll get any courtesy in return.

Any reasonable person would click 'reply-to-all', which would keep me
in Cc, if your MUA is not braindead. And clicking 'reply-to-all'
consistently is the reasonable thing to do, because properly
configured mailing lists (unlike this one) require this.

Cheers.

-- 
Felipe Contreras


      reply	other threads:[~2013-04-22  7:30 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
2013-04-22  6:59         ` Bart Schaefer
2013-04-22  7:30           ` Felipe Contreras [this message]

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='CAMP44s38PiN+VqYgdpD1FegLWQQtPuFa=oReAidynTBPALC5XQ@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).