From: Kurtis Rader <krader@skepticism.us>
To: ZyX <kp-pav@yandex.ru>
Cc: Ray Andrews <rayandrews@eastlink.ca>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: ANSI bg colour outside of prompt area
Date: Sun, 22 Feb 2015 16:28:02 -0800 [thread overview]
Message-ID: <CABx2=D8SBRUkGt7yorvkQ0SsHkB00v5oJ8R7eghdhr3yHCaLSA@mail.gmail.com> (raw)
In-Reply-To: <4348921424650217@web10g.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On Sun, Feb 22, 2015 at 4:10 PM, ZyX <kp-pav@yandex.ru> wrote:
>
> It is the first time I saw any “bash convert” needing this feature. I think
> that if you create a poll you will see that almost everybody will vote for
> either “WTF are you talking about?”, “Who may need this behaviour?” or
> “Sure,
> this option is cool. Doesn’t mean I am going to ever use it though.”
>
Those were pretty much my thoughts as well. I have never once in the 30+
years I've been programming wanted to change the default background color
of an existing terminal session on the fly; i.e., outside of a particular
app. This is something you spend a few minutes every five years or so
deciding on your personal preference then set once and forget about it. If
you like different background colors to signify a particular purpose for a
given terminal you, again, figure out what those should be then create an
easy mechanism for invoking a terminal with the desired characteristics (be
it background color, width, height, or anything else).
> Thus I would say that implementing such option is a pure waste of time.
>
Agreed. Please do not implement this. There are already way too many zsh
options with very limited utility but which cause much confusion.
--
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank
next prev parent reply other threads:[~2015-02-23 0:28 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 [this message]
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
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='CABx2=D8SBRUkGt7yorvkQ0SsHkB00v5oJ8R7eghdhr3yHCaLSA@mail.gmail.com' \
--to=krader@skepticism.us \
--cc=kp-pav@yandex.ru \
--cc=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).