This is just a suggestion for vtcl that would be nice...I guess I will
try and get the code and implement it myself. I was actually implying
that the lookup could be used to take the user in the code to where it
occurs.
"J.R.Suckling" wrote:
>
> how about $ grep -n VarName *.tcl
I know I could do that, but I am talking about making a cross-reference
tool, for use in vtcl.
How can you obtain the name of the current file(s) you are working on
from within vtcl?
> don't say it, you use windows.
> sounds like a vtcl project, that
> opens files and runs [regexp ...]
> But make it a separate program.
>
> Eric Bresie wrote:
> >
> > > Sent: Thursday, March 30, 2000 8:00 AM
> > >
> > > The "variable" window and editor had no use and was removed. You don't
> > > need it.
> > >
> > > ...RickM...
> >
> > How about still have the variable window but how about instead of a variable
> > editor you have a variable/proc cross refererence window, indicating what
> > proc or line number the variable/proc is at? Maybe indicating where it is
> > defined and where it is referenced? (I am taking this from an old HPBasic
> > command that I always found useful). It might make removing uneeded
> > variables a little easier (I always seem to have that problem)
> >
> > Displaying line numbers might be nice also, making some of the references
> > easier to work with?
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/vtcl-user
