From: Mo DeJong <mdejong@cygnus.com>
To: James Ingham <jingham@cygnus.com>
Cc: tromey@cygnus.com, Insight List <insight@sourceware.cygnus.com>
Subject: Re: `dir'
Date: Fri, 07 Apr 2000 14:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10004071445480.17245-100000@abomination.cygnus.com> (raw)
In-Reply-To: <14574.20552.919557.271408@leda.cygnus.com>
Tom, keep those bug reports flying in. "fresh eyes" on a problem are
really good.
> Tom,
> > I hope I'm not being too annoying. I figure you'd probably rather I
> > report things.
>
> Yup, totally!
>
> >
> > I couldn't find a way to add a search directory (gdb "dir" command)
> > via the GUI.
The tk_chooseDirectory dialog is really really ugly but at least there is
a hook for it. We really need to take the nice dir selection widget from
libgui and put it into the Tcl/Tk core (replace the tk_chooseDirectory
impl with ours). It might be better to actually sit down and create a
new mega widget that works just like the Mac dir an file selection
widgets (because they are so much better than the Win or Unix ones).
Mo
> This one should be easy. I didn't do it before 'cause I didn't know
> there was a directory chooser in libgui. This is one of the silly
> omissions of Tk, it has a choose file and a save file, but no choose
> directory dialog. Actually, there is a choose directory in Tk8.3,
> though it is plug-ugly (except on the Mac, where it uses the very nice
> Navigation Services dialogs...) But I was poking my nose in libgui,
> and noted the tantelizing tclgetdir.c file...
>
> I will get to this at some point, since I agree it is annoying, but if
> some enterprising soul wants to try their hand first, cool!
>
> >
> > Invariably what happens (either with command-line or GUI) is that I
> > don't remember that I need to use "dir" until I move into a stack
> > frame where the source isn't found.
> >
> > I'd really like it if adding a directory via "dir" caused the source
> > window to update if appropriate. This would make Insight much nicer
> > than the command line (where I currently use "up ; down" to make it do
> > what I want -- lose).
>
> I am more likely to add the GUI, and have that do the right thing,
> than add another hook to the CL. Actually, it would be nice to just
> have a generic pre or post processing hook in ALL the commands
> executed by the gdb command interpreter, so you wouldn't have to go
> add the hooks into the C code to do this sort of thing. I guess we
> could add this to the console, but it might be cleaner to put it in
> the command interpreter. I will poke around a bit, it might already
> be there for all I know...
>
> >
> > Note that with Insight, the up/down trick currently doesn't work.
> > Once it can't find the file, it seems to get confused.
>
> Yes, I know about this one. This will take some work in the
> SrcTextWin code to fix, which is a bit contorted, to be polite...
>
> Jim
>
> --
> ++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
> Jim Ingham jingham@cygnus.com
> Cygnus Solutions, a Red Hat Company
>
prev parent reply other threads:[~2000-04-07 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 13:21 `dir' Tom Tromey
2000-04-07 14:14 ` `dir' James Ingham
2000-04-07 14:30 ` `dir' Tom Tromey
2000-04-07 14:45 ` `dir' James Ingham
2000-04-07 14:58 ` `dir' Tom Tromey
2000-04-07 14:54 ` Mo DeJong [this message]
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=Pine.LNX.4.10.10004071445480.17245-100000@abomination.cygnus.com \
--to=mdejong@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@cygnus.com \
--cc=tromey@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).