This is the mail archive of the
mailing list for the GDB project.
Re: The concept of 'one single line' help gives strange effects ...
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 05 Jun 2019 05:40:22 +0300
- Subject: Re: The concept of 'one single line' help gives strange effects ...
- References: <firstname.lastname@example.org>
> From: Philippe Waroquiers <email@example.com>
> Date: Wed, 05 Jun 2019 00:28:16 +0200
> In a recent HEAD gdb, do the following:
> (gdb) |apropos .|cat > apropos1.out
> (gdb) |apropos -v .|grep -e ' -- ' | sed -e 's/\.$//' > apropos1bis.out
> (gdb) !diff apropos1.out apropos1bis.out|more
> This will (mostly) show the difference between the 'truncated' first line
> of help, as produced by 'help <some class>' or 'apropos REGEXP'
> and the first 'full line' of the help, as output by
> 'apropos -v REGEXP' or by 'help command'.
> The 'truncated' first line is produced by cli-decode.c:print_doc_line.
> This stops printing characters of the first line when encountering a .
> or a , character.
> This has not been taken into account in all help strings, giving
> sometimes cumbersome one line help.
I think those cases where this produces unpleasant results should be