ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Using context with cweave
Date: Fri, 31 Aug 2007 23:26:18 +0200	[thread overview]
Message-ID: <fe8d59da0708311426l2a7f8225i19c0fe57cf4236ff@mail.gmail.com> (raw)
In-Reply-To: <608bfe540708311017l4e6335c4qb91aaac5a4f51d60@mail.gmail.com>

Anothers step:
1) save you cweaved tex file as wc.tex
2) put this in test0001a.tex
%% tex0001a
\usemodule [cweb]
\def\ignoreCWEBinput{\relax}
\activateCWEB
\setupinteraction[state=start]
\starttext

\title {Contents} \processCWEBcontents wc \page
\title {Sections} \processCWEBsections wc \page
\title {Sources}  \processCWEBsource   wc \page
\title {Index}    \processCWEBindex    wc \page

\stoptext

3) texexec --pdf --batch test0001a

\def\ignoreCWEBinput{\relax}
avoid endless loop for now.

btw, it's no correct again.


-- 
luigi
----------------------------------------------------------------
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  : https://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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2007-08-31 21:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <608bfe540708271838h5e567c6cm1aa92a20a4d24536@mail.gmail.com>
     [not found] ` <fe8d59da0708271941s7b8241c3p8b3e5b5aaaf17509@mail.gmail.com>
     [not found]   ` <608bfe540708280432m178923a0w80c1c7f0063eea94@mail.gmail.com>
     [not found]     ` <fe8d59da0708280503y3e41fe80x6cc135331c95d43a@mail.gmail.com>
     [not found]       ` <608bfe540708280520w6152e7d6x9171e60748a08269@mail.gmail.com>
2007-08-30 19:17         ` Aditya Mahajan
2007-08-31 12:16           ` John Luciani
2007-08-31 14:31             ` Aditya Mahajan
2007-08-31 17:17               ` John Luciani
2007-08-31 17:52                 ` Aditya Mahajan
2007-08-31 19:07                   ` Hans Hagen
2007-08-31 19:48                     ` John Luciani
2007-08-31 20:10                       ` Hans Hagen
2007-08-31 20:47                         ` John Luciani
2007-08-31 19:50                   ` John Luciani
2007-08-31 21:26                 ` luigi scarso [this message]
2007-08-31 22:30                   ` luigi scarso
2007-08-31 23:01                     ` luigi scarso
2007-09-01  1:00                       ` luigi scarso
2007-09-02  0:48                         ` John Luciani

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=fe8d59da0708311426l2a7f8225i19c0fe57cf4236ff@mail.gmail.com \
    --to=luigi.scarso@gmail.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).