From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org, dje@google.com
Subject: Re: [patch+7.5] auto-load: User conveniences suggested by Doug Evans
Date: Fri, 24 Aug 2012 15:28:00 -0000 [thread overview]
Message-ID: <50379D92.8070705@redhat.com> (raw)
In-Reply-To: <83boi0gvwx.fsf@gnu.org>
On 08/24/2012 04:19 PM, Eli Zaretskii wrote:
>> Date: Wed, 22 Aug 2012 16:46:27 +0100
>> From: Pedro Alves <palves@redhat.com>
>> CC: gdb-patches@sourceware.org, Doug Evans <dje@google.com>
>>
>> On 08/21/2012 03:43 PM, Jan Kratochvil wrote:
>>> +add \"set auto-load safe-path /\" line to \"%s\".\n\
>>> +For more information about this security protection run from the shell: \
>>> +info \"(gdb)Auto-loading safe path\"\n"),
>>> + filename_real, homeinit, homeinit);
>>
>> This may be cryptic, for instance, for Windows users who won't
>> have 'info' available in the shell.
>
> Why wouldn't they? A Windows port is available.
I mean "won't usually have" -- because they haven't installed it.
For instance, I believe people that use Windows hosted toolchains from
CodeSourcery or AdaCore won't usually have info installed, and won't ever
bother to install it.
My point is that the meat of the information here is the pointing
at a section in the manual, not some specific way to get at it.
>
>> How about something like:
>>
>> For more information about this security protection see the
>> "Auto-loading safe path" section in the GDB manual.
>>
>> ?
>
> If they don't have 'info', how will they read the manual?
Either online; a local html version that is installed along the
toolchain (common, and some vendors integrate this with the frontend
like, e.g., Eclipse); or a local pdf version (also common).
--
Pedro Alves
next prev parent reply other threads:[~2012-08-24 15:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 14:44 Jan Kratochvil
2012-08-21 17:50 ` Eli Zaretskii
2012-08-24 16:11 ` Jan Kratochvil
2012-08-24 18:15 ` Eli Zaretskii
2012-09-09 8:53 ` Jan Kratochvil
2012-09-09 17:26 ` Eli Zaretskii
2012-09-09 17:55 ` Jan Kratochvil
2012-09-09 18:09 ` Eli Zaretskii
2012-08-22 15:46 ` Pedro Alves
2012-08-24 15:13 ` Jan Kratochvil
2012-08-24 15:17 ` Pedro Alves
2012-08-24 15:19 ` Eli Zaretskii
2012-08-24 15:28 ` Pedro Alves [this message]
2012-08-24 15:31 ` Pedro Alves
2012-08-24 15:43 ` Jan Kratochvil
2012-08-24 17:56 ` Eli Zaretskii
2012-08-24 18:01 ` Jan Kratochvil
2012-08-24 18:26 ` Eli Zaretskii
2012-08-27 18:02 ` Pedro Alves
2012-08-27 18:12 ` Jan Kratochvil
2012-09-09 9:02 ` Jan Kratochvil
2012-09-10 11:29 ` Pedro Alves
2012-09-10 11:47 ` Jan Kratochvil
2012-09-10 13:06 ` Pedro Alves
2012-09-10 15:28 ` Jan Kratochvil
2012-09-17 18:29 ` [commit+7.5] " Jan Kratochvil
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=50379D92.8070705@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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