On Thu, Mar 10, 2011 at 11:53:22AM -0800, Micah Cowan wrote:
>
> It wouldn't be difficult to write as a separate program, which is really
> how this should be handled. You could redirect a pipeline's STDOUT and
> STDERR to individual named pipes (FIFOs), and have a separate program
> read from bot
On Fri, Mar 11, 2011 at 3:42 AM, Philip Prindeville <
philipp_s...@redfish-solutions.com> wrote:
> Hi.
>
> First off, this isn't a bug report so much as a feature request.
>
> I do a lot of cross-compilation of linux and various packages for embedded
> distros.
>
> Version bumps are always perilou
On 3/10/11 5:03 PM, Philip Prindeville wrote:
> On 3/10/11 12:50 PM, Micah Cowan wrote:
>> (03/10/2011 12:28 PM), Micah Cowan wrote:
>>> (03/10/2011 11:53 AM), Micah Cowan wrote:
(03/10/2011 11:42 AM), Philip Prindeville wrote:
> My request is simple. Using termcap/ncurses info (which you
(03/10/2011 02:03 PM), Philip Prindeville wrote:
> A lot of programs don't behave properly (or perhaps, "don't behave the
> same") when they detect that stdout isn't a terminal. But I think
> someone else mentioned this already.
Yeah. You could always run the program under another program that fo
On 3/10/11 12:50 PM, Micah Cowan wrote:
(03/10/2011 12:28 PM), Micah Cowan wrote:
(03/10/2011 11:53 AM), Micah Cowan wrote:
(03/10/2011 11:42 AM), Philip Prindeville wrote:
My request is simple. Using termcap/ncurses info (which you need anyway
for the readline stuff), it would be nice to hav
(03/10/2011 12:55 PM), Chet Ramey wrote:
> On 3/10/11 3:49 PM, Micah Cowan wrote:
>> (03/10/2011 12:07 PM), Chet Ramey wrote:
>>> 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 sp
On 3/10/11 3:49 PM, Micah Cowan wrote:
> (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
On Thu, Mar 10, 2011 at 12:49:27PM -0800, Micah Cowan wrote:
> 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?
Arrange so that's not the case. Most likely by running something like
magicthing ma
(03/10/2011 12:28 PM), Micah Cowan wrote:
> (03/10/2011 11:53 AM), Micah Cowan wrote:
>> (03/10/2011 11:42 AM), 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
>>> comm
(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 outp
On 3/10/11 3:28 PM, Micah Cowan wrote:
>>> It wouldn't be difficult to write as a separate program, which is really
>>> how this should be handled. You could redirect a pipeline's STDOUT and
>>> STDERR to individual named pipes (FIFOs), and have a separate program
>>> read from both pipes, inserti
(03/10/2011 12:27 PM), Philip Prindeville wrote:
> On 3/10/11 11:53 AM, Micah Cowan wrote:
>> (03/10/2011 11:42 AM), 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
>>>
(03/10/2011 11:53 AM), Micah Cowan wrote:
> (03/10/2011 11:42 AM), 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 out
On 3/10/11 11:53 AM, Micah Cowan wrote:
(03/10/2011 11:42 AM), 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 S
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
>
>
> Of course, that
On Thu, Mar 10, 2011 at 11:42:25AM -0800, Philip Prindeville wrote:
> My request is simple.
HAH! Lies
> 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
(03/10/2011 11:42 AM), 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
>
This doesn't strik
17 matches
Mail list logo
