ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Kip Warner <kip@thevertigo.com>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Including command output
Date: Mon, 05 Mar 2012 19:11:19 -0800	[thread overview]
Message-ID: <1331003479.17258.62.camel@kip-laptop> (raw)
In-Reply-To: <alpine.LNX.2.02.1203052203280.15921@ybpnyubfg.ybpnyqbznva>


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

On Mon, 2012-03-05 at 22:05 -0500, Aditya Mahajan wrote:
> The attached file works at my end.

It works at my end as well, but just not as part of my book.

> No. It is defining \BazaarVersion once and then reusing the result. Add 
> \loggingall to your file to see what is happening.

It still bails. This is what I see with \loggingall placed in the
environment file.

...
{vertical mode: \tracingstats}
{\tracingpages}
{\tracingoutput}
{\tracinglostchars}
{\tracingmacros}
{\tracingparagraphs}
{\tracingrestores}
{\showboxbreadth}
{\showboxdepth}
{\tracinggroups}
{\tracingifs}
{\tracingscantokens}
{\tracingnesting}
{\tracingassigns}
{into \tracingassigns=2}
{\errorstopmode}

{\tracingonline}
{changing \tracingonline=1}
! TeX capacity exceeded, sorry [text input levels=127].
\BazaarRevision ...ltof"bzr revno | tr -d '\\n'")}
                                                  \BazaarRevision 
l.4 }
     
\BazaarRevision ...ltof"bzr revno | tr -d '\\n'")}
                                                  \BazaarRevision 
l.4 }
     
\BazaarRevision ...ltof"bzr revno | tr -d '\\n'")}
                                                  \BazaarRevision 
l.4 }
     
...
l.60 
     
!  ==> Fatal error occurred, no output PDF file produced!
mtx-context     | fatal error: return code: 

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 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:[~2012-03-06  3:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  3:07 Kip Warner
2012-03-05  4:20 ` Aditya Mahajan
2012-03-06  1:32   ` Kip Warner
2012-03-06  3:05     ` Aditya Mahajan
2012-03-06  3:11       ` Kip Warner [this message]
2012-03-06  3:15         ` Aditya Mahajan
2012-03-06  3:36           ` Kip Warner
2012-03-06  3:38             ` Aditya Mahajan
2012-03-06  3:41               ` Kip Warner
2012-03-06  3:50                 ` Aditya Mahajan
2012-03-06  3:56                   ` Kip Warner
2012-03-06  5:04                     ` Aditya Mahajan
2012-03-06  5:37                       ` Kip Warner

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=1331003479.17258.62.camel@kip-laptop \
    --to=kip@thevertigo.com \
    --cc=adityam@umich.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).