On 17/06/06, Etaoin Shrdlu <[EMAIL PROTECTED]> wrote:
On Saturday 17 June 2006 12:15, Mick wrote:
> I am getting confused here: why is module building related to setting
> grep's colour option?
There is probably some script that parses the output of grep, and,
with --color=always, this include
On Saturday 17 June 2006 13:48, Etaoin Shrdlu wrote:
> Using --color=auto, on the
> other hand, is the correct way to do the "right" thing, ie grep
> itself "knows" whether it should emit escape sequences to colorize the
> output (if it's really outputting to terminal) or not (if, for example,
> it
On Saturday 17 June 2006 12:15, Mick wrote:
> I am getting confused here: why is module building related to setting
> grep's colour option?
There is probably some script that parses the output of grep, and,
with --color=always, this includes terminal control characters and
escape sequences whi
On 16/06/06, Daniel Drake <[EMAIL PROTECTED]> wrote:
Justin R Findlay wrote:
> I finally figured out why linux wouldn't build its modules. Although I
> learned a lot about make it was because I had set
>
> GREP_OPTIONS="--color=always"
Using "--color=auto" would have circumvented this problem a
Justin R Findlay wrote:
I finally figured out why linux wouldn't build its modules. Although I
learned a lot about make it was because I had set
GREP_OPTIONS="--color=always"
Using "--color=auto" would have circumvented this problem and still
given you pretty colours when you run grep from t
I finally figured out why linux wouldn't build its modules. Although I
learned a lot about make it was because I had set
GREP_OPTIONS="--color=always"
in my /root/.bashrc which is sourced by shell invocations from make (and
odd shell scripts as well, like configure scripts). So, the lesson is,
6 matches
Mail list logo
