Re: typical TCL docu nonsens

On 6/21/2024 1:17 PM, aotto1968 wrote:
snip

 the core problem is *not* the "autopath" is wrong because at the time I use it I
does not know it was wrong. The core problem is that is was *very* difficult to figure
out what was the "right" name. special the tcl_traceExec… does not help and more
important the package.n docu (package require…) does *not* spend a single word on
*how* to find a package.
 

I'm not sure if this would have helped in your case, but I've used this with some success. It outputs every package command issued and by using a search pattern to limit the output to the ifneeded commands, sometimes gets me what I need to know.
Being on windows, I use the console and the update calls get quicker output. If on linux, I suppose you could also pipe it through grep.
rename package package_orig
proc package {args} {
     if { [info exist ::packpat] } {
         if { [string match -nocase *${::packpat}* $args]} {
             puts "----package: $args" ; update idletasks
         }
     }
     tailcall package_orig {*}$args
}
console show ; update
set ::packpat "ifneeded*bwidget"
catch {package require foobar} ;# this won't be found, so it causes a big search