bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hightlighting in bash


From: Micah Cowan
Subject: Re: Hightlighting in bash
Date: Thu, 10 Mar 2011 12:49:27 -0800
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8

(03/10/2011 12:07 PM), Chet Ramey wrote:
> On 3/10/11 2:42 PM, Philip Prindeville wrote:
> 
>> My request is simple.  Using termcap/ncurses info (which you need anyway
>> for the readline stuff), it would be nice to have the option of running
>> commands in a pseudo-tty and then bracketing the output from STDERR with
>> <highlight on>...<highlight off>.
>>
>> Of course, that also implies that your writes to wherever STDERR eventually
>> goes are atomic and won't be interspersed with output from STDOUT.  I'll
>> let someone more intimate with the particulars of stdio and tty drivers and
>> line disciplines figure that bit out.
>>
>> This would be nice because it would allow one to quickly identify and
>> isolate potentially detrimental error messages from mundane but profuse
>> output that logs commands being invoked, etc.
> 
> This doesn't seem like it has to be done in bash.  A small program that
> allocated and opened a pty, ran bash in the pty (or an arbitrary command
> and arguments specified on the command line), and managed input and output
> would be acceptable.
> 
> There look to be a few packages out there that could be adapted for this.
> Even a pty sniffing program would do the trick.

When both stdout and stderr are the same tty, how do you expect to use
this method to detect which text should be hilighted and which shouldn't?

-- 
Micah J. Cowan
http://micah.cowan.name/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]