From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16067 invoked by alias); 22 Apr 2013 07:30:47 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31324 Received: (qmail 27179 invoked from network); 22 Apr 2013 07:30:44 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW, T_DKIM_INVALID autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.180 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=g2p2iHRuMDOxjfFniBZqcCsFjYfNT8O96CeMhpoqS14=; b=YOA2XDnXeRpW5W22ToXRbIgGPbU/FpkZ+41Hy/nwS4CoxdV4IZFNIxKWpRg+1JHXYX /zLUAvqPV+CVBvgcsytY4R6xgYCjpzJbd0gmB7erbLCyzGJuyGQ5r+XcZpX+kEJXicwA wuRvdHuNjyct+fUmtFvP78OPe753vVfvP/AY8rM2vWLXIV8wN33uC6NeNtcACROrGvb/ BTkiWn7drKBaTgnGUSGgrFPal4eY88FCK++ZyWSY2UP7zfG8OO+KaqRK8rmTF9s+OK6F kFHt38ww5CBcija73xBqBd79wVW3JZcGBBxCqnyfkYlV+1M7wyiOwdLO9nWuIo3wapeR 2gmg== MIME-Version: 1.0 X-Received: by 10.152.3.137 with SMTP id c9mr12867539lac.5.1366615836789; Mon, 22 Apr 2013 00:30:36 -0700 (PDT) In-Reply-To: <130421235936.ZM6922@torch.brasslantern.com> References: <130420232740.ZM12405@torch.brasslantern.com> <130421112734.ZM6597@torch.brasslantern.com> <130421235936.ZM6922@torch.brasslantern.com> Date: Mon, 22 Apr 2013 02:30:36 -0500 Message-ID: Subject: Re: Alignment issue with multiple describes From: Felipe Contreras To: Bart Schaefer Cc: zsh-workers@zsh.org, Felipe Contreras Garza Content-Type: text/plain; charset=UTF-8 On Mon, Apr 22, 2013 at 1:59 AM, Bart Schaefer 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