From: Aditya Mahajan <adityam@umich.edu>
To: vim.unix@gmail.com, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Undefined \continueifinputfile on presentation
Date: Wed, 14 Aug 2013 15:24:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.03.1308141521390.32040@hzvpu.rqh> (raw)
In-Reply-To: <CAM4mttTPhaBqz4igAvNdDP2rYA2Zoxenfam5bir+HfnLbuR3dA@mail.gmail.com>
On Wed, 14 Aug 2013, Pau wrote:
> sorry for these newbie questions... but how to enable write18?
See the wiki.
http://wiki.contextgarden.net/write18
> Why a document that used to compile perfectly over many years cannot
> be compiled now, if nothing was changed?
MkII has been frozen for couple of years now, and there has been no
fundamental change in MkII for a while. I don't know why compiling the
document is taking 10 minutes for you.
Aditya
___________________________________________________________________________________
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-08-14 19:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 23:29 Pau
2013-08-13 23:37 ` Aditya Mahajan
2013-08-13 23:42 ` Pau
2013-08-13 23:51 ` Aditya Mahajan
2013-08-13 23:56 ` Hans Hagen
2013-08-14 0:07 ` Pau
2013-08-14 0:33 ` Aditya Mahajan
2013-08-14 2:12 ` Pau
2013-08-14 2:38 ` Aditya Mahajan
2013-08-14 4:41 ` Pau
2013-08-14 4:48 ` Aditya Mahajan
2013-08-14 6:06 ` Pau
2013-08-14 15:24 ` Aditya Mahajan
2013-08-14 16:42 ` Pau
2013-08-14 16:54 ` Aditya Mahajan
2013-08-14 17:04 ` Pau
2013-08-14 17:38 ` Aditya Mahajan
2013-08-14 19:17 ` Pau
2013-08-14 19:24 ` Aditya Mahajan [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=alpine.LNX.2.03.1308141521390.32040@hzvpu.rqh \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
--cc=vim.unix@gmail.com \
/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).