Re: TeXshow

[Taco Hoekwater <taco@elvenkind.com>]

Giuseppe Bilotta wrote:
> 
> Well, I find TeXShow a good source of information for quick references;
> I'd like to point a couple of facts, though:
> 
> 1) the tws files seem a little outdated to me; maybe they need to be
> regenerated ... and generally speaking, how do you create the tws files
> relative to formats not already provided? [esp. the experimental ones]

I think Hans has a perl script that creates the tws files from the
same setup files that define the commands in the manual (setupb & 
mult-con/mult-com).

As a side note: I'd be very happy with a version that uses the
internal macro names. ConTeXt internals are a mixture of dutch 
and english. While writing modules, I want the module to work in 
every language, so I quite often need the internal name of the command 
instead of the interface specific one. Example: \blank is internally 
defined as \blanko (dutch), but \setupbodyfont is defined as 
\setupbodyfont (english).

> 2) is there a way to call TeXShow from the command line in such a way
> that it reuses exisisting windows (if present)?

No. I'm not even sure Tk allows that kind of trickery.

> 3) the kind of information displayed by TeXShow is extremely compat---
> I would dare to say too compact: in some cases it's difficult to say
> which parameter does what---ok, TeXShow is intended for quick-reference,
> so the user should already know what does what, but still ... I prefere
> browsing the commands using it, rather than the interactive [or printable]
> reference manual.

Agree. Some sort of comment field within the \startsetup \stopsetup
would be
very helpful.

TeXshow also has a number of speed issues ;)

-- 
groeten,

Taco