zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-users@sunsite.dk
Subject: Re: Colorize command output
Date: Mon, 21 Feb 2005 19:35:01 +0100	[thread overview]
Message-ID: <3967.1109010901@trentino.logica.co.uk> (raw)
In-Reply-To: <qb3k11po2sl4puu08gubtld0s5cv6s5vcd@4ax.com>

zzapper wrote:
> On Mon, 21 Feb 2005 17:16:43 +0100,  wrote:
> 
> >
> >To make conflicts stand out, I'd like to colorize the output of the svn 
> >command so that lines starting with C are displayed in red. My first 
> >shot at this was
> >
> >% svn status | sed -e 's/^C/\e[31mC\e[0m/g'

Escapes like \e are not expanded by sed. You can used the shell's $'...'
form of quoting to expand them, however.

    svn status | sed -e $'s/^C/\e[31m&\e[0m/g'

Note also, that you can use & in the replacement part of sed's s
command. That substitutes whatever was matched.

> I guess you could cheat by using grep as a colorizer
> 
> echo "fred" | grep --color '.' 

That's not quite the same. It highlights matching parts of a line so
lines not beginning with a C will be lost. I've attached below my old
hgrep script which highlights matches but outputs all lines. I find it
more useful than grep --color. It's meant for general cases, though, and
wouldn't be much use for colouring svn output.

Oliver

# hgrep - highlight grep

if (( ! $# )); then
  echo "Usage: $0:t [-e pattern...] [file...]" >&2
  return 1
fi

local -a regex
local htext=`echotc so` ntext=`echotc se`

while [[ "$1" = -e ]]; do
  regex=( $regex "$2" )
  shift 2
done

if (( ! $#regex )); then
  regex=( "$1" )
  shift
fi

regex=( "-e
s/${^regex[@]}/$htext&$ntext/g" )
sed ${(Ff)regex[@]} "$@"


      reply	other threads:[~2005-02-21 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 16:16 Ralph Pöllath
2005-02-21 16:34 ` zzapper
2005-02-21 18:35   ` Oliver Kiddle [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=3967.1109010901@trentino.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=zsh-users@sunsite.dk \
    /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).