cont-en.tws

cont-en.tws

[Patrick Gundlach]

Hi,

is the cont-en.tws (and the other tws-files) generated 
automatically? Will they be existant in future versions of 
context? Will the syntax change? I ask, because I am thinking of 
making a helper mode for my favourite editor (emacs) that will 
offer the currently known commands and present the possible 
options.

Viele Grüße,

  Patrick Gundlach

- I TeX, therefore I am -

Re: cont-en.tws

[Taco Hoekwater]

Patrick Gundlach wrote:
> 
> Hi,
> 
> is the cont-en.tws (and the other tws-files) generated
> automatically? Will they be existant in future versions of
> context? Will the syntax change? I ask, because I am thinking of
> making a helper mode for my favourite editor (emacs) that will
> offer the currently known commands and present the possible
> options.

IIRC, Hans explained some time ago that they are 'semi-automatic':
the actual TWS files are automatically generated from the 'normal'
context files that are used for the various documentation manuals 
(the input files that create the syntax description blocks). 

It is very unlikely that there will be downward-incompatible changes
to the TWS files, I think. However, there has been some talk about
extending the \startsetup with explanatory comments, so it is likely
that there will be an backward-compatible extension to the tws format 
somewhere in the future.

-- 
groeten,

Taco

Re: cont-en.tws

[Hans Hagen]

At 04:16 PM 9/14/2001 +0200, Taco Hoekwater wrote:
>Patrick Gundlach wrote:
> >
> > Hi,
> >
> > is the cont-en.tws (and the other tws-files) generated
> > automatically? Will they be existant in future versions of
> > context? Will the syntax change? I ask, because I am thinking of
> > making a helper mode for my favourite editor (emacs) that will
> > offer the currently known commands and present the possible
> > options.
>
>IIRC, Hans explained some time ago that they are 'semi-automatic':
>the actual TWS files are automatically generated from the 'normal'
>context files that are used for the various documentation manuals
>(the input files that create the syntax description blocks).
>
>It is very unlikely that there will be downward-incompatible changes
>to the TWS files, I think. However, there has been some talk about
>extending the \startsetup with explanatory comments, so it is likely
>that there will be an backward-compatible extension to the tws format
>somewhere in the future.

indeed

i can add to that generating a tws is not that complicated:

   texexec --once setupd.tex

will give you the one for the current interface. Setupd.tex takes the info 
from setupb.tex and conferts is.

In the future we may move to xml for setupb [time ....].

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

cont-en.tws

[Patrick Gundlach]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 412 bytes --]

Goodnight,

> will give you the one for the current interface. Setupd.tex takes the
> info from setupb.tex and conferts is.
>
> In the future we may move to xml for setupb [time ....].

I guess, setupb is not being generated automatically, right?

There is nothing wrong with defining something like setupd.tex, that 
outputs setupb in another way I would like to have?

-- 
Viele Grüße, 

    Patrick Gundlach

Re: cont-en.tws

[Hans Hagen]

At 11:05 PM 9/14/2001 +0200, Patrick Gundlach wrote:

>I guess, setupb is not being generated automatically, right?

right

>There is nothing wrong with defining something like setupd.tex, that
>outputs setupb in another way I would like to have?

right

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: cont-en.tws

[Ed L Cashin]

Patrick Gundlach <gundlach@irb.cs.uni-dortmund.de> writes:

...
> I am thinking of 
> making a helper mode for my favourite editor (emacs) that will 
> offer the currently known commands and present the possible 
> options.

Berend de Boer has written a context mode for emacs, by the way. 

-- 
--Ed Cashin                   PGP public key:
  ecashin@terry.uga.edu       http://www.terry.uga.edu/~ecashin/pgp/

Re: cont-en.tws

[Berend de Boer]

Ed L Cashin <ecashin@terry.uga.edu> writes:

> Berend de Boer has written a context mode for emacs, by the way. 

It's add:

        http://www.pobox.com/~berend/emacs

-- 
Groetjes,

Berend. (-:

Re: cont-en.tws

[Patrick Gundlach]

Hi, its me again.

two questions:

1) is it possible to typeset a quick reference such as the one on 
   the context on demand homepage? (setup-qr)?

2) it seems that there is no way to distinguish optional 
parameters? for example the \blackrule(s) in setupb.tex are 
written like this:

\startsetup
  \command
    [\y!blackrule]
  \type
    [\c!opt!\c!vars!]
  \inheritvariables
    [\y!setupblackrules]
    []
\stopsetup

\startsetup
  \command
    [\y!blackrules]
  \type
    [\c!vars!]
  \inheritvariables
    [\y!setupblackrules]
    []
\stopsetup

but in cont-en.tws there is no difference between the two:

startsetup
com:blackrule:
typ:vars/:
ivr:setupblackrules::
stopsetup

startsetup
com:blackrules:
typ:vars/:
ivr:setupblackrules::
stopsetup

Viele Grüße,

  Patrick Gundlach

- I TeX, therefore I am -

Re: cont-en.tws

[Patrick Gundlach]

answering myself again :-)

> 1) is it possible to typeset a quick reference such as the one on
>    the context on demand homepage? (setup-qr)?

Ok, I've found it ...

-- 
Viele Grüße, 

    Patrick Gundlach