public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Bruce Stephens <bruce.stephens@messagingdirect.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight 5.0 and GDB 5.0
Date: Thu, 09 Nov 2000 07:38:00 -0000	[thread overview]
Message-ID: <3A0AC4A5.1041F4B3@cygnus.com> (raw)
In-Reply-To: <vbofzpuslb.fsf@erwin.isode.com>

Bruce Stephens wrote:
> 
> "Eray Ozkural (exa)" <erayo@cs.bilkent.edu.tr> writes:
> 
> > Bruce Stephens wrote:
> > > You might try explicitly undefining TK_USE_INPUT_METHODS in
> > > src/tk/generic/tk.h.  In at least some linux X servers, this is quite
> > > expensive.  (There was discussion of this a year or two ago on
> > > comp.lang.tcl.)
> >
> > Does this mean insight/sourcenav works very well on X servers
> > other than XFree86?
> 
> < http://www.deja.com/getdoc.xp?AN=528799292 > suggests it might work
> fine on XFree86, sometimes.
> 

Interesting.  Thanks.


> For what it's worth, both seem to work fine for me (XFree86 on i386
> GNU/Linux).
> 

I couldn't find anyone hit by this around here either.


> I don't know the details, but it appears that X server configuration
> and things may be critical---so some people might see a problem where
> others don't, even when using very similar systems.
> 

They don't seem to know what triggers it as well.

Maybe Eray should post his machine hardware and XFree86 configuration, but
this would be the wrong list anyway.  comp.lang.tcl  is the appropriate
forum.


> Try undefining TK_USE_INPUT_METHODS and rebuilding.  It's not going to
> affect usage of Insight, as far as I can see.
> 

It centainly worth a try.

I wouldn't rule out the video card driver theory, although it may be
triggered by the above.  In any way, undefining TK_USE_INPUT_METHODS
seems the first thing to try.



Thanks for the hint.

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  reply	other threads:[~2000-11-09  7:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-03 12:27 Michael Ernst
2000-11-03 13:15 ` Fernando Nasser
2000-11-08  3:03   ` Eray Ozkural (exa)
2000-11-08  3:11     ` Bruce Stephens
2000-11-08 23:29       ` Eray Ozkural (exa)
2000-11-09  5:59         ` Fernando Nasser
2000-11-09  6:29         ` Bruce Stephens
2000-11-09  7:38           ` Fernando Nasser [this message]
2000-11-11  2:18             ` Eray Ozkural (exa)
2000-11-11  5:24               ` Fernando Nasser
2000-11-11 10:53               ` bstell
2000-11-11 13:15                 ` Eray Ozkural
2000-11-09 13:26       ` Brian Stell
2000-11-10  7:32         ` Bruce Stephens
2000-11-08  7:38     ` Fernando Nasser
     [not found] <973984454.30568.ezmlm@sources.redhat.com>
2000-11-13 12:01 ` Jim Ingham
     [not found]   ` <20001114041709.A930@orion.exa.homeip.net>
2000-11-13 23:40     ` Eray Ozkural

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=3A0AC4A5.1041F4B3@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=bruce.stephens@messagingdirect.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).