zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: ANSI bg colour outside of prompt area
Date: Sun, 22 Feb 2015 21:34:31 -0800	[thread overview]
Message-ID: <54EABBE7.1060808@eastlink.ca> (raw)
In-Reply-To: <CABx2=D-GYcJHTZKY1=NtKtFVAcLxt3JohvayYw-aTY_qa9grMg@mail.gmail.com>

On 02/22/2015 08:03 PM, Kurtis Rader wrote:
> Ray, You're missing the point. Every feature has costs as well as benefits.
> The costs are not limited to writing the original patch to the source code.
> Every new feature makes future changes more difficult. Every new feature
> requires additional verbiage to the documentation and thus a potential
> source of confusion. Every new feature makes it more likely that someone
> will be surprised by the behavior of the program. Every new feature
> increases the cost of supporting the program. Etcetera.

I couldn't agree more.  There is always a 'price'--several prices, some 
of them up-front and obvious, but always some lurking in the dark 
waiting to ambush you.
>
> The value of the proposed feature has to be considerably larger than those
> costs.

Of course.  I argue for it, but the devs will decide if the 'price' is 
worth the minimal utility.  I'd suspect that the price would be very 
low, but it's not my call.  I mostly like it as a bash compatibility 
thing--maybe this is important to bashers, who knows. One for sure.  
It's not worth any trouble.
> I love zsh. I also hate a lot of the "features" that have been added
> which benefit a very tiny percentage of its users at the expense of
> everyone else. Including the people trying to help new zsh users and keep
> the project alive and the preferable choice from the alternatives. There
> are a million features that could be added to zsh which would make someone
> happy. Implementing all those features would kill zsh.

Again, I couldn't agree more.  We see Bart and Peter and others 
wrestling with this kind of stuff every day, it's an intractable mess.  
Nope, even if it were my call, I'd only do this BG color thing if it 
were dead simple, absolutely clear and predictable and reliable, and of 
real worth to bashers.


  reply	other threads:[~2015-02-23  5:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 13:23 junkcommander0
2015-02-22 16:52 ` Ray Andrews
2015-02-22 19:10 ` Bart Schaefer
2015-02-22 20:07   ` junkcommander0
2015-02-22 21:55   ` ZyX
2015-02-23  1:22     ` Bart Schaefer
2015-02-23  1:55       ` Vincent Lefevre
2015-02-23 12:34       ` ZyX
2015-02-22 23:10   ` Ray Andrews
2015-02-23  0:10     ` ZyX
2015-02-23  0:28       ` Kurtis Rader
2015-02-23  1:14         ` Bart Schaefer
2015-02-23  1:44           ` Kurtis Rader
2015-02-23  2:04             ` Vincent Lefevre
2015-02-23  2:18               ` Kurtis Rader
2015-02-23  3:41             ` Ray Andrews
2015-02-23  4:03               ` Kurtis Rader
2015-02-23  5:34                 ` Ray Andrews [this message]
2015-02-23  4:14               ` Kurtis Rader
2015-02-23  5:49                 ` Bart Schaefer
2015-02-23  9:46               ` Vincent Lefevre
2015-02-23 16:36                 ` Bart Schaefer
2015-02-23 16:51                   ` Ray Andrews
2015-02-24  2:53                     ` Bart Schaefer
2015-02-24  3:49                       ` junkcommander0
2015-02-24  4:33                         ` Ray Andrews
2015-02-24  4:25                       ` Ray Andrews
2015-02-24  8:36                   ` Vincent Lefevre
2015-02-23  5:27             ` Bart Schaefer
2015-02-23  1:51           ` Vincent Lefevre
2015-02-23  0:55       ` Ray Andrews
2015-02-23  1:36       ` Vincent Lefevre

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=54EABBE7.1060808@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@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).