From: Aditya Mahajan <adityam@umich.edu>
To: Kip Warner <kip@thevertigo.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Including command output
Date: Mon, 5 Mar 2012 22:05:22 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.02.1203052203280.15921@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <1330997549.17258.55.camel@kip-laptop>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1273 bytes --]
On Mon, 5 Mar 2012, Kip Warner wrote:
> On Sun, 2012-03-04 at 23:20 -0500, Aditya Mahajan wrote:
>> If you want to use the automagic way, you can define \BazaarRevision to
>> redefined \BazaarRevision, for example:
>>
>> \def\BazaarRevision
>> {\ctxlua{context.setevalue(
>> "BazaarRevision",
>> os.resultof"bzr revno | tr -d '\\n'")}%
>> \BazaarRevision}
>
> Hey Aditya. I tried the automagic method, but ConTeXt bails:
>
> ! 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.58
The attached file works at my end.
>
> Based on what I saw from htop, it looks like it running the command into
> the ground over and over again which is the exact opposite of what we
> are trying to do.
No. It is defining \BazaarVersion once and then reusing the result. Add
\loggingall to your file to see what is happening.
Aditya
[-- Attachment #2: Type: APPLICATION/x-tex, Size: 223 bytes --]
[-- Attachment #3: 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:[~2012-03-06 3:05 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 [this message]
2012-03-06 3:11 ` Kip Warner
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=alpine.LNX.2.02.1203052203280.15921@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=kip@thevertigo.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).