ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: frame "thickness"
Date: Fri, 20 Oct 2006 14:35:22 +0200	[thread overview]
Message-ID: <4538C28A.6000204@wxs.nl> (raw)
In-Reply-To: <dbf589bfa45a1e7921ec9c01d437ac85@di.unito.it>

andrea valle wrote:
> So, command list is edited by hand?
> It is not possible to have something like doxygen to generate a command 
> list from source?
>   
even then it has to be defined i.e. edited ; maybe some day it will be 
possible to generate the \setup commands from the formal definition [the 
reverse] (and also add some checking) but i'll happily wait with that 
till i have a faster computer.

spreading the definitions across the source (i.e. splitting up 
cont-en.xml) is an option but we don't gain anything; actually, long ago 
those defs were all over the place
> Just for my curiousity.
> (It will be always updated, and won't require additional efforts).
>   
tex is not a regular programming language -) 

Hans 


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2006-10-20 12:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  0:05 andrea valle
2006-10-20  7:37 ` Hans Hagen
2006-10-20  8:34   ` andrea valle
2006-10-20  8:44     ` andrea valle
2006-10-20  8:57       ` Wolfgang Schuster
2006-10-20  9:38         ` Hans Hagen
2006-10-20 11:49           ` andrea valle
2006-10-20 12:35             ` Hans Hagen [this message]
2006-10-20 14:52         ` Aditya Mahajan
2006-10-20 22:14           ` andrea valle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4538C28A.6000204@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).