Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 0/4] Improve "show style", use style in "help" and "apropos".
Date: Tue, 18 Jun 2019 20:58:00 -0000	[thread overview]
Message-ID: <1560891478.8865.5.camel@skynet.be> (raw)
In-Reply-To: <1560891176.8865.3.camel@skynet.be>

On Tue, 2019-06-18 at 22:52 +0200, Philippe Waroquiers wrote:
> On Tue, 2019-06-18 at 14:46 -0600, Tom Tromey wrote:
> > > > > > > "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:
> > > > 
> > > > (gdb) | with pagination off -- apropos -v breakpoint | less
> > 
> > Philippe> Effectively, 'pagination off' and event worse 'style enabled off'
> > Philippe> make it significantly more difficult to see where apropos -v 
> > Philippe> starts the doc of a new command.
> > 
> > Maybe this command should still use styling?  I wonder.
> 
> Wondering ...
> 
> At shell level, coloring seems to be disabled when piped.
> E.g.  
>   $ ls -l
>   .... files with some colors
>   $ ls -l | cat
>   .... same output, but no colors
>   $

ls has an option to control coloring.
   ls -l --color=always|cat
will still be colored.

So, we might add an option -style [on|off] to the GDB pipe_command,
if we believe it should output styling sequence.

Philippe


  reply	other threads:[~2019-06-18 20:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 13:19 Philippe Waroquiers
2019-05-31 13:19 ` [RFA 1/4] Add highlight style, title style, fputs_highlighted. Improve 'show style' Philippe Waroquiers
2019-05-31 20:10   ` Tom Tromey
2019-06-01  8:47     ` Philippe Waroquiers
2019-06-03 14:21       ` Tom Tromey
2019-05-31 13:19 ` [RFA 4/4] Document in NEWS and gdb.texinfo the "help", "apropos" and "show style" changes Philippe Waroquiers
2019-05-31 13:46   ` Eli Zaretskii
2019-05-31 13:19 ` [RFA 2/4] Improve usability and/or readibility of help and apropos output Philippe Waroquiers
2019-05-31 20:22   ` Tom Tromey
2019-05-31 13:19 ` [RFA 3/4] Update tests following changes to "help" and "apropos" Philippe Waroquiers
2019-05-31 20:34   ` Tom Tromey
2019-05-31 20:35 ` [RFA 0/4] Improve "show style", use style in " Tom Tromey
2019-06-18 13:09 ` Pedro Alves
2019-06-18 16:04   ` Tom Tromey
2019-06-18 20:11   ` Philippe Waroquiers
2019-06-18 20:46     ` Tom Tromey
2019-06-18 20:53       ` Philippe Waroquiers
2019-06-18 20:58         ` Philippe Waroquiers [this message]
2019-06-18 22:40           ` Pedro Alves
2019-06-19  0:25             ` Philippe Waroquiers
2019-06-19 19:44               ` Tom Tromey
2019-06-19 19:26             ` Tom Tromey
2019-06-19 22:56               ` Pedro Alves
2019-06-20 14:21                 ` Tom Tromey

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=1560891478.8865.5.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tom@tromey.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox