WIBNIF there was a Developers Toolkit (like there is in Zen Cart) where you could type in the name of a symbol (TWiki variable or function or template name, for example) and get feedback on where it is defined?

-- Contributors: CrawfordCurrie - 15 Feb 2007

Discussion

I personally been using a shell script, gr for decades that does a grep in the whole distribution (defined by climbing up to / from the current dir until we encounter a .gr file) and outputs the matches in a syntax similar to C compiler error messages, so I can run it as a compilation command in IDEs (like emacs) and then use the IDE "show next error" to go to each match You can find my latest version of this script at http://hg.colas.nahaboo.net/unix-utils/gr/raw-file/4e22958ec48c/gr

I could not live without this trusted friend

# gr _newLinkFormat
lib/TWiki/Render.pm:83:sub _newLinkFormat {
lib/TWiki/Render.pm:602:    my $ans = $this->_newLinkFormat;

-- ColasNahaboo - 31 Jan 2008

I meant TWiki Variables, not variables in code. I can find variables in code no problem: find /home/twiki/420/lib -name '*.pm' -exec grep -Hn '_newLinkFormat' \{\} \; (like you I run this in the compilation command of Emacs)

-- CrawfordCurrie - 31 Jan 2008

Isn't here somewhere buried in TDO a script that scans the sourcecode for plugins to check what variables are published? Or I dreamed it?

-- RafaelAlvarez - 31 Jan 2008