ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Search path.
Date: Mon, 10 Sep 2012 10:56:40 -0400	[thread overview]
Message-ID: <F4298DFA-B243-4112-8231-44291E8C79AE@umich.edu> (raw)
In-Reply-To: <20120910131354.GE27079@rae.vm.bytemark.co.uk>


On 2012-09-10, at 9:13 AM, Pontus Lurcock <pont@talvi.net> wrote:

> On Mon 10 Sep 2012, Andre Caldas wrote:
> 
>>> Do you really need to use context mkii? As it's a new project,
>>> using context mkiv might be a better idea.
>> 
>> No, I don't. I want to use always the preferred solution. I want to
>> follow your guidelines and be enlightened... :-)
>> How did you know I was using one and not the other? I didn't know it
>> myself!!!
> 
> Probably from the name of the binary -- ‘texexec’ runs mkii,
> whereas ‘context’ gives you mkiv.


We also need to clarify this on the wiki, which talks about texexec in a few places. 

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
___________________________________________________________________________________

  reply	other threads:[~2012-09-10 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10  2:45 Andre Caldas
2012-09-10  7:09 ` Hans Hagen
2012-09-10 12:47   ` Andre Caldas
2012-09-10 13:13     ` Pontus Lurcock
2012-09-10 14:56       ` Aditya Mahajan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-06  4:33 Search Path Randall Skelton

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=F4298DFA-B243-4112-8231-44291E8C79AE@umich.edu \
    --to=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).