Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -nx-except-gdbtkinit option
Date: Fri, 18 Nov 2005 12:50:00 -0000	[thread overview]
Message-ID: <uek5e5fsq.fsf@gnu.org> (raw)
In-Reply-To: <437DB85D.3000505@st.com> (message from Andrew STUBBS on Fri, 18 Nov 2005 11:17:49 +0000)

> Date: Fri, 18 Nov 2005 11:17:49 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
> 
> .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.

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?

> I much prefer it the way I have done it.

Of course.  But you see, I don't like this new feature: I think it
will add to user's confusion.


  reply	other threads:[~2005-11-18 11:57 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 [this message]
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=uek5e5fsq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.stubbs@st.com \
    --cc=drow@false.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