From: "Rogers, Michael K" <mroge02@emory.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using \stretched in macro fails
Date: Sat, 6 Apr 2013 14:45:25 +0000 [thread overview]
Message-ID: <1E5A50C784A8AD44B420EF5A1E9B2806D663A8D9@e14mbx23n.Enterprise.emory.net> (raw)
In-Reply-To: <1E5A50C784A8AD44B420EF5A1E9B2806D663A7DA@e14mbx23n.Enterprise.emory.net>
OK, it's not the macro. This fails (same error: ! This can't happen (add_disc_widths)):
\starttext
St. \stretched[width=]{Banac}
\stoptext
This works:
\starttext
St. \stretched[width=]{Bana}
\stoptext
Strange.
On Apr 6, 2013, at 10:26 AM, "Rogers, Michael K" <mroge02@emory.edu>
wrote:
> Hi,
>
> Below \stretched works by itself, but causes a fatal error when in the macro (\Name). I get the same result with all variants.
> Perhaps there's a better way?
>
> MWE:
>
> %%%%%%%%
> \def\Name{\stretched[width=]}
> %\def\Name#1{\stretched[width=]{#1}}
> %\define[1]\Name{\stretched[width=]{#1}}
>
> \starttext
>
> \stretched[width=]{Hi there!}
>
> St. \Name{Banach}
>
> \stoptext
> %%%%%%%%
>
> Here's part of the log:
>
> ConTeXt ver: 2013.04.05 22:00 MKIV beta fmt: 2013.4.6 int: english/english
> …
> ! This can't happen (add_disc_widths).
>
> system > tex > error on line 10 in file foo18453.tex: This can't happen ( ...
>
> 1 \def\Name{\stretched[width=]}
> 2 \def\Name#1{\stretched[width=]{#1}}
> 3 %\define[1]\Name{\stretched[width=]{#1}}
> 4
> 5 \starttext
> 6
> 7 \stretched[width=]{Hi there!}
> 8
> 9 St. \Name{Banach}
> 10 >>
> 11 \stoptext
> 12
> 13
>
> l.10
>
> ! ==> Fatal error occurred, no output PDF file produced!
> mtx-context | fatal error: return code: 1
>
> ________________________________
>
> This e-mail message (including any attachments) is for the sole use of
> the intended recipient(s) and may contain confidential and privileged
> information. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution
> or copying of this message (including any attachments) is strictly
> prohibited.
>
> If you have received this message in error, please contact
> the sender by reply e-mail message and destroy all copies of the
> original message (including attachments).
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-04-06 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 14:26 Rogers, Michael K
2013-04-06 14:45 ` Rogers, Michael K [this message]
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=1E5A50C784A8AD44B420EF5A1E9B2806D663A8D9@e14mbx23n.Enterprise.emory.net \
--to=mroge02@emory.edu \
--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).