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: Fri, 18 Nov 2005 12:33:00 -0000 [thread overview]
Message-ID: <437DB85D.3000505@st.com> (raw)
In-Reply-To: <20051117194639.GA20312@nevyn.them.org>
Daniel Jacobowitz wrote:
> It sounds like there's no GDB command to process .gdbtkinit, which is a
> TCL file rather than a GDB CLI script file. Andrew, is that right? If
> so, have you considered adding such a command to Insight, instead?
Sorry, I think I understand what you are getting at now. Ignore my last
response to this question.
.gdbtkinit is not a TCL file. It's rather more like a Microsoft .ini
file (indeed on windows it is known as gdbtk.ini). Does that format have
a name? I don't know.
I suppose it wouldn't be impossible to screw around with the tcl to get
it to load on a command, although I don't know how right now. However,
would Insight then save the file again, as it should, as the end of the
session? Would this really make sense to a user?
Also, this file is used to define the initial state of the GUI (which
windows are open and where and what size, as well as with what icons and
fonts). It probably doesn't make sense to open this much after startup.
I much prefer it the way I have done it.
Andrew Stubbs
next prev parent reply other threads:[~2005-11-18 11:20 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 [this message]
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
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=437DB85D.3000505@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