ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: safe way of writing arguments
Date: Tue, 08 Aug 2006 09:58:49 +0200	[thread overview]
Message-ID: <44D84439.5080409@wxs.nl> (raw)
In-Reply-To: <eb8c4m$scs$1@sea.gmane.org>

Jano Kula wrote:
> Hi!
>
> Is it safe to leave spare comma at the end of the key=value list or 
> other list of arguments?
>   
in most cases it is ok
> It is not nice, but when adding/commenting arguments in readable way 
> (one per line) it's faster and while experimenting with parameters one 
> doesn't have to care about the last comma adding or removing it back and 
> forth, for example:
>
> \setuplayout[
> grid=yes,
> %header=0mm,
> footer=7mm,
> %footerdistance=10mm,
> %cutspace=12mm,
> ]
>   
in this case a space after 12mm is not that problematic because layout 
are calculated in vertical mode and the 12 mm is used in assignments
> or
>
> \setuphead[
> chapter,
> section,
> %subsection,
> %subsubsection,
>   
hm, here it can be troublesome unless i catch an empty case (not sure); 
if you run into troubles with such cases report it to the list and we 
can see if we can catch it
> ][
> textstyle=\ss,
> numberstyle=\ss,
> ]
>   
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-08-08  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 21:43 Jano Kula
2006-08-08  7:58 ` Hans Hagen [this message]
2006-08-08 11:16   ` Jano Kula
2006-08-08 12:02     ` Hans Hagen

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=44D84439.5080409@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).