ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <schultzk@uni-trier.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [***SPAM***] OT: Generating Command reference from source code
Date: Wed, 4 Dec 2013 09:59:06 +0100	[thread overview]
Message-ID: <51B70613-0052-48C8-97CE-EDFF16C0EEA4@uni-trier.de> (raw)
In-Reply-To: <529E6CE4.7040304@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1728 bytes --]

Hi Hans,


Am 04.12.2013 um 00:44 schrieb Hans Hagen <pragma@wxs.nl>:
[snip, snip]
> 
> 
> the problem with tex (and therefore context) is that we are dealing with quite some interaction between unpredictable user input, macro (expansions), tex-internals, resources like fonts, patterns and whatever, etc. and this is why you often need to play with mechanisms: small test files and see how it looks (tex is a visual tool)
> 
> it's often not as simple as "you feed it this" end "get back that"
	I would disagree with you on a philosophical level, but no need to go into that!
> 
> for documentation several methods are used:
> 
> - examples in the test suite
> - some explanation in the source
> - explanations on the wiki
> - dedicated manuals
> - articles by users (+examples)
> 
> although i sometimes run into impressive auto-documented documentation for languages or os commands, in practice i find myself looking for examples and/or experimenting and/or going into sources
> 
We could need some more dedicated manuals especially in the area of side effects of parameters and thier
interactions inside of context.

Most examples focus on just one or two parameters which is good as a starting point, yet many posts here
show the lack of examples for the interplay of parameters locally and globally. 

I do have a request: would it be possible to finish the section on overlays and stacks in the manual or at least
start on it. I need that information because I need to use stacks inside of frames and these are then stacked inside of
others. The examples I have found are for margins, pages and inside of tables, but are not helpful for the task for me
at hand. 

regards
	Keith.




[-- Attachment #1.2: Type: text/html, Size: 3232 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2013-12-04  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00b501cef072$f53c70c0$dfb55240$@tosovsky@email.cz>
2013-12-03 23:44 ` Hans Hagen
2013-12-04  8:59   ` Keith J. Schultz [this message]
2013-12-04 10:40     ` Hans Hagen
2013-12-04 17:56   ` Jan Tosovsky
     [not found]   ` <529f6ce2.02670e0a.2f60.46ffSMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-04 18:39     ` Wolfgang Schuster
2013-12-04 19:11       ` Jan Tosovsky
     [not found]       ` <529f7e7f.092d0f0a.7fb3.ffffd34aSMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-04 19:20         ` Wolfgang Schuster
2013-12-03 21:59 Jan Tosovsky

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=51B70613-0052-48C8-97CE-EDFF16C0EEA4@uni-trier.de \
    --to=schultzk@uni-trier.de \
    --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).