From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: "Pádraig Brady" <P@draigbrady.com>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 08/11] cal: allow day highlight testing
Date: Mon, 29 Apr 2013 11:58:07 +0200 [thread overview]
Message-ID: <20130429095807.GA22791@x2.net.home> (raw)
In-Reply-To: <CAG27Bk0iSZDx=mJ_WM1sA5ins7g5zCqnTdVGLyogSZ4E9d57OA@mail.gmail.com>
On Mon, Apr 29, 2013 at 09:59:15AM +0100, Sami Kerola wrote:
> On 29 April 2013 01:24, Pádraig Brady <P@draigbrady.com> wrote:
> > On 04/28/2013 06:11 PM, Sami Kerola wrote:
> >> Requires similar trick as done with more to by pass check whether a
> >> session is or isn't interactive.
> >
> > I wonder should we have an option or env variable to force highlighting?
> > I've wanted a couple of times to pipe output like:
> > cal --color=always | ansi2html.sh
yep, coreutils way:
--color[=WHEN]
where WHEN is 'auto', 'never' or 'always'.
Sami, see lib/colors.c. It would be nice to have WHEN evaluation
(conversion to some enum value) on one place and use the code
in dmesg --color[=WHEN] too.
> Your proposal makes totally sense. Karel, please wait a moment (till
> tomorrow) that I have a change to rewrite this change to be more
> useful. I'll send new patch to the list, and update my git sometime
> off-work-hour.
Maybe we can use more colors in the cal(1) output. What about a
weekend days, month name, week days line etc. ?
I personally believe that there is still a lot of places where we can
improve command line usability and readability. (See for example
"dmesg -H" in the latest release.)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2013-04-29 9:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 17:10 [PATCH 00/11] pull: cal(1) spring clean up Sami Kerola
2013-04-28 17:10 ` [PATCH 01/11] cal: fix preprocessor directive indendation Sami Kerola
2013-04-28 17:10 ` [PATCH 02/11] cal: convert function like definitions to functions Sami Kerola
2013-04-28 17:28 ` Dave Reisner
2013-04-28 20:20 ` Sami Kerola
2013-04-29 15:21 ` Thomas Bächler
2013-04-29 20:21 ` Sami Kerola
2013-04-28 17:10 ` [PATCH 03/11] cal: clean up use of constants Sami Kerola
2013-04-29 15:51 ` Thomas Bächler
2013-04-29 21:05 ` Sami Kerola
2013-04-28 17:11 ` [PATCH 04/11] tests: add calendar reformation check Sami Kerola
2013-04-28 17:11 ` [PATCH 05/11] cal: simplify calendar reformat calculations Sami Kerola
2013-04-28 17:11 ` [PATCH 06/11] cal: remove unnecessary initializations Sami Kerola
2013-04-28 17:11 ` [PATCH 07/11] cal: de-duplicate julian specific functions Sami Kerola
2013-04-28 17:11 ` [PATCH 08/11] cal: allow day highlight testing Sami Kerola
2013-04-29 0:24 ` Pádraig Brady
2013-04-29 8:59 ` Sami Kerola
2013-04-29 9:58 ` Karel Zak [this message]
2013-04-28 17:11 ` [PATCH 09/11] tests: add cal day highlight corner cases Sami Kerola
2013-04-28 17:11 ` [PATCH 10/11] cal: trim three month display trailing white spaces Sami Kerola
2013-04-29 0:32 ` Pádraig Brady
2013-04-29 9:11 ` Sami Kerola
2013-04-29 13:40 ` Pádraig Brady
2013-04-29 18:01 ` Sami Kerola
2013-05-01 0:54 ` Pádraig Brady
2013-04-28 17:11 ` [PATCH 11/11] cal: move global variables to local scope Sami Kerola
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=20130429095807.GA22791@x2.net.home \
--to=kzak@redhat.com \
--cc=P@draigbrady.com \
--cc=kerolasa@gmail.com \
--cc=util-linux@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox