public inbox for
 help / color / mirror / Atom feed
From: Syd Polk <>
To: Mike Fahlbusch <>
Cc:, Left Spin <>
Subject: Re: Debugging SourceNavigator
Date: Wed, 12 Dec 2001 22:52:00 -0000	[thread overview]
Message-ID: <> (raw)
Message-ID: <20011212225200.pwqq24y3HdfCjaK166l20qEuw89eokQ-B0IvssY6rHY@z> (raw)
In-Reply-To: <>

Mike Fahlbusch wrote:
> At 01:19 AM 12/13/01 +0000, you wrote:
> Here is my wish list:
> - HTML help files included with binary

They should be there, actually. They should end up in share/doc/html or
some such place.

> - list of array variables in menu Symbols-View-Variables
> - goto line doesn't seem to work (if patch isn't currently included with d/l)
> - iconise all windows command in Window menu
> - Goto sel in top level Search menu instead of its own Search-Goto-Goto
> menu.  This to make the goto command easier to get to.
> - multiple bookmarks (at least 10), with its own bookmarks menu, instead of
> just the one bookamark in the Search-Goto menu.
> - a version of SN with compiled executable tcl/tk files instead of the
> interpreted format for improved execution speed (if not already done).

Unlikely. Tcl/Tk is much faster now than it used to be. Most of the
slowdowns are in questionable coding practices in the tcl code or the
extensions that were written for SN. We did not have time to fix them

> - and last but not least, reduced memory usage if possible

Difficult at best. SN has a lot of info sitting around.
> >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr
> >tcl/tk], but now I'm at a loss on how you debug the running application.

There is no good way to step SN through a debugger. I would investigate
setting the SN_DEBUG variable and using the logging. I have also spent
time actually in gdb with the C code for the Tcl interpreter figuring
out problems.

> >I'm having trouble following the state variables of the megawidgets, and
> >I'd really like to be able to set break points in the tcl/tk code and
> >examine objects.

One thing you can do is launch the console, load the SN part, and then
selectively replace the pieces you need. tk is a dynamic coding
environment, and you should be able to take advantage of that.

> >Any help would be appreciated. My goal is to provide fixes to the source,
> >and add an optional new editor keybindings configuration file (wordstar to
> >start with).

Good luck to you.

  reply	other threads:[~2001-12-12 22:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 14:01 Left Spin
2001-11-24 14:40 ` Mike Fahlbusch
2001-11-26  0:23   ` Syd Polk [this message]
2001-11-29 23:46     ` Mike Clarkson
2001-12-14 11:14       ` Mike Clarkson
2001-12-12 22:52     ` Syd Polk
2001-12-12 18:03   ` Mike Fahlbusch
2001-12-12 17:19 ` Left Spin
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25 18:28 Left Spin
2001-12-12 18:06 ` Left Spin
2001-11-23 14:19 Left Spin
2001-11-27 17:10 ` Mike Clarkson
2001-12-14  9:25   ` Mike Clarkson
2001-12-12 17:18 ` Left Spin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).