Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -nx-except-gdbtkinit option
Date: Wed, 30 Nov 2005 01:38:00 -0000	[thread overview]
Message-ID: <438C4BD3.9060803@st.com> (raw)
In-Reply-To: <20051118153306.GA9846@nevyn.them.org>

Daniel Jacobowitz wrote:
>>>Would it make sense to not inhibit its loading under -nx?  After all,
>>>we don't inhibit loading ~/.inputrc under -nx, right?  Why should the
>>>toolkit be different?
>>
>>That would work fine for me. I don't know why it is any different, but 
>>it is different and I didn't feel comfortable changing the default, let 
>>alone removing the functionality altogether. This is probably a 
>>discussion for the Insight list. I think I'll test the water.
> 
> I like this suggestion better anyway.  If Insight is compiled in, have
> it read its configuration.

But the Insight guys didn't. However, they have accepted my patch here: 
http://sources.redhat.com/ml/insight/2005-q4/msg00037.html.

This solves the problem entirely in Insight by having an environment 
variable override the -nx option.

I don't know how this is for other people, but it solves the problem for me.

Please disregard my -nx-except-gdbtkinit patch from now on (not that you 
weren't going to anyway).

Thanks

Andrew Stubbs


  reply	other threads:[~2005-11-29 12:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 17:34 Andrew STUBBS
2005-11-16 22:43 ` Eli Zaretskii
2005-11-17 19:20   ` Andrew STUBBS
2005-11-17 19:49     ` Eli Zaretskii
2005-11-17 23:44       ` Daniel Jacobowitz
2005-11-18  2:52         ` Andrew STUBBS
2005-11-18 12:33         ` Andrew STUBBS
2005-11-18 12:50           ` Eli Zaretskii
2005-11-18 12:59             ` Andrew STUBBS
2005-11-18 16:33               ` Daniel Jacobowitz
2005-11-30  1:38                 ` Andrew STUBBS [this message]
2005-11-18  0:08       ` Andrew STUBBS

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=438C4BD3.9060803@st.com \
    --to=andrew.stubbs@st.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.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