From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Don't install gdb.PYTHONDIR if -nx
Date: Mon, 29 Nov 2010 21:38:00 -0000 [thread overview]
Message-ID: <m3sjyjstdg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20101129003949.502FC246199@ruffy.mtv.corp.google.com> (Doug Evans's message of "Sun, 28 Nov 2010 16:39:49 -0800 (PST)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I don't entirely like the patch, it's extending -nx into
Doug> new territory, e.g., -nx controlling whether certain commands
Doug> are available or not. It shouldn't matter, from the user's
Doug> perspective, whether the commands are implemented in python.
I agree. In particular I think it is reasonable to want to use python
commands from a batch script, but such a script is likely to use -nx.
Doug> However, the only other alternative I can think of is to
Doug> add a new option, and I'm guessing that's unacceptable.
I think it would be fine to add one.
Either way I think the documentation needs to be updated.
Jan pointed out that this is PR 12227.
Tom
next prev parent reply other threads:[~2010-11-29 21:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:40 Doug Evans
2010-11-29 21:38 ` Tom Tromey [this message]
2010-11-30 0:03 ` [RFA, doc RFA] " Doug Evans
2010-11-30 0:30 ` Jan Kratochvil
2010-11-30 3:54 ` Eli Zaretskii
2010-11-30 4:11 ` Doug Evans
2010-11-30 11:20 ` Eli Zaretskii
2010-11-30 15:29 ` Doug Evans
2010-11-30 18:59 ` Tom Tromey
2010-12-06 20:43 ` Doug Evans
2010-12-06 20:50 ` Eli Zaretskii
2010-12-06 20:58 ` Doug Evans
2010-12-06 21:15 ` Doug Evans
2010-12-06 21:15 ` Eli Zaretskii
2010-12-06 21:16 ` Doug Evans
2010-12-06 22:17 ` Doug Evans
2010-12-07 4:02 ` Eli Zaretskii
2010-12-07 1:38 ` Jan Kratochvil
2010-11-30 4:22 ` [RFA] " Daniel Jacobowitz
2010-11-30 5:16 ` Doug Evans
2010-11-30 18:19 ` Daniel Jacobowitz
2010-11-30 18:25 ` Doug Evans
2010-11-30 5:33 ` 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=m3sjyjstdg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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