Re: [patch+7.5] auto-load: User conveniences suggested by Doug Evans

Pedro Alves
2012-09-10T13:06:44Z

On 09/10/2012 12:47 PM, Jan Kratochvil wrote:
> On Mon, 10 Sep 2012 13:29:19 +0200, Pedro Alves wrote:
>> On 09/09/2012 10:01 AM, Jan Kratochvil wrote:
>>> For more information about this security protection see
>>> the "Auto-loading safe path" section in the GDB manual or run from the shell:
>>> info "(gdb)Auto-loading safe path"
>>> warning: File "/home/jkratoch/redhat/gdb-clean/gdb/gdb-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
>>
>> I honestly don't understand why "for example, run..." would be worse
>> than "or run...", while "or" to my ears implies that the information that
>> you get in the pointed section of the manual might be different (alternative)
>> from what you get from that info command. But that's maybe just language
>> barrier, or just me. I'm happy enough with this version. Thanks.
>
> I understand "for example" would be slightly better there but it IMO is not
> worth an extra line.

If that's the issue, "e.g.," is shorter, and moving the "the" to the
previous line still leaves us at 78 columns:

For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"

vs the 77 columns:

For more information about this security protection see
the "Auto-loading safe path" section in the GDB manual or run from the shell:
info "(gdb)Auto-loading safe path"

Not suggesting this one, but a little re-flowing can bring it down to 73 columns,
at the expense of breaking the section name in two lines:

For more information about this security protection see the "Auto-loading
safe path" section in the GDB manual. For example, run from the shell:
info "(gdb)Auto-loading safe path"

Anyway, just for completeness. Thanks.

>
> I believe the output should not be too long to be read by anyone.
> I understand the warning in 7.5 has proven to be too short, though.
>
> For example the initial GDB licensing information (without -q) is too long,
> I do not see it required by GNU Coding Standards; but the initial text is
> offtopic here.

--
Pedro Alves