From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: PDF-Toc text is wrong for new \start… commands
Date: Tue, 16 Jul 2013 14:14:59 +0200 [thread overview]
Message-ID: <20130716121459.GE12367@homerow> (raw)
In-Reply-To: <A29D7F89-8006-4933-AE65-0C052CD71692@kram.io>
[-- Attachment #1.1: Type: text/plain, Size: 745 bytes --]
On 2013–07–16 Steffen Kram wrote:
> A similar problem occurs, when using references:
It might be a parser issue. ConTeXt uses different parsers for
different commands. Most commands happily accept values without
trailing comma. The commands using a different parser require a
trailing comma. I recall this applied to \definepalet, \usepath and
a few others.
The issue occasionally pops up on the mailing list, since it's
inconsistent and non-intuitive behaviour.
http://www.ntg.nl/pipermail/ntg-context/2012/067585.html
https://gist.github.com/phi-gamma/2941284#file-features-wiki-L258
Personally I don't use that syntax any more. It doesn't work
reliably and fails occasionally with particular commands.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-07-16 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 8:10 Steffen Kram
2013-07-16 8:52 ` Steffen Kram
2013-07-16 12:14 ` Marco Patzer [this message]
2013-07-16 9:33 ` Gareth Jones
2013-07-16 12:36 ` luigi scarso
2013-07-16 18:11 PDF-Toc text is wrong for new \start? commands Andres Conrado
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=20130716121459.GE12367@homerow \
--to=homerow@lavabit.com \
--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).