Radovan Garabík

> when can we expect `devel` to be merged into master and a new release? Well, I wanted to do it sooner but real life issues prevented it...I've made a...

> @garabik -- the release doesn't seem to have been tagged correctly. I can see that "master" now has the 1.12 bits but if you look at https://github.com/garabik/grc/releases you'll see...

This was actually intended, so that you could write: regexp=fox colours=blue and have the `fox` coloured without bothering with the parentheses - the first (actually zeroth) colour stands for group...

Can you send me the details of your OS? tty size should not be ignored, only the changes _during_ the execution of grc. What does `grc resize` say? In particular,...

I see. `ps` ignores tty size if its output is not a terminal - try `ps aux|cat` to see the effect. I am (slowly) working on tty emulation, hopefully that...

On Mon, Jul 27, 2015 at 09:33:42PM -0700, Efreak wrote: > Any chance of getting support for [`pv`](http://www.ivarch.com/programs/pv.shtml)? That's not a bad idea; unfortunately pv's stderr will be block buffered...

Just an observation (writing it down for future reference): `ping` from `iputils` is line buffered and works well with `grc`. OTOH, `ping` from `inetutils` is block buffered, and works really...

Yes, you are supposed to change the first line of /usr/(local/)/bin/grc and /usr/(local/)/bin/grcat from python3 to python. Unfortunately, it is kind of difficult to do automatically, but at least I'll...

Though I cannot reproduce it exactly (I guess it depends on the terminal), I have seen similar behaviours - `less` manpage says: Warning: when the -r option is used, less...

> > Just to clarify, './du' and '/usr/bin/du' (and also '\du') are standard ways to bypass aliases, at least on sh-compatible shells, so those forms shouldn't actually be matched by...