From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <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: Mon, 27 Aug 2012 18:02:00 -0000 [thread overview]
Message-ID: <503BB633.6050204@redhat.com> (raw)
In-Reply-To: <834nnsgn96.fsf@gnu.org>
On 08/24/2012 07:26 PM, Eli Zaretskii wrote:
>> Date: Fri, 24 Aug 2012 20:00:33 +0200
>> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>> Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org,
>> dje@google.com
>>
>> On Fri, 24 Aug 2012 19:55:45 +0200, Eli Zaretskii wrote:
>>> For more information about this security protection see the
>>> "Auto-loading safe path" section in the GDB manual
>>> ('info \"(gdb)Auto-loading safe path\"').
>>>
>>> I removed the reference to the shell because the above works in Emacs
>>> as well, and is also shorter.
>>
>> People type such commands into GDB, from what I know from IRC.
>
> We must draw a line somewhere. Otherwise, we will end up explaining
> how to start a shell etc.
I have to agree with Jan here. "info" is also a GDB command -- that
would surely leave users confused. :-(
If four lines is too much, then my previous suggestion, but merged
to three lines, still leaves us with 71 columns:
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\).
IMO, that's not too long, and is maximally informative.
WRT emacs, I honestly think that an emacs user is able to do the
"I don't need to run 'info' on shell -- I can do it right here
in the minibuffer" mental jump.
--
Pedro Alves
next prev parent reply other threads:[~2012-08-27 18:02 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
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 [this message]
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=503BB633.6050204@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