ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Can I use mkii and mkiv side by side?
Date: Wed, 21 Jan 2015 14:31:33 +0100	[thread overview]
Message-ID: <46F8597C-745D-4888-B96F-773E17456D10@web.de> (raw)
In-Reply-To: <905EC570-3995-4D7C-91DB-179C8F01B7DB@gmail.com>


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

Hi Otared,

actually, just setting the PATH variable will work, but you have to set it
with the proper command!

The Standard TexShop engines use the tcsh shell and not bash !!

either change the first line to 
#!/bin/tcsh

or set the path bash style
export PATH=/Volumes/OK/context-minimal/tex/texmf-osx-64/bin:$PATH

I put the standard PATH behind the minimals path so that it is searched first!

regards
	Keith

> Am 21.01.2015 um 13:48 schrieb Otared Kavian <otared@gmail.com>:
> 
> Hi Keith,
> 
> Thanks for your attention. 
> Indeed I use the latest TeXShop (version 3.49) but regarding the content my mkii.engine file if I remove the line 
> 
> source /Volumes/OK/context-minimal/tex/setuptex
> 
> then I cannot typeset with my standalone installation of Context: I tried to use a set path such as
> 
> set path = ($path /Volumes/OK/context-minimal/tex/texmf-osx-64/bin)
> 
> but I get an error message telling me:
> 
> /Users/kavian/Library/TeXShop/Engines/mkii.engine: line 3: syntax error near unexpected token `('
> /Users/kavian/Library/TeXShop/Engines/mkii.engine: line 3: `set path = ($path /Volumes/OK/context-minimal/tex/texmf-osx-64/bin)’
> 
> So at this point I have to keep the instruction to source the setuptex file in order to typeset either with mkii or mkiv, using the standalone Context. 
> 
> Best regards: OK
> 


[-- Attachment #1.2: Type: text/html, Size: 2757 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:[~2015-01-21 13:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 23:36 Gerben Wierda
2015-01-21 11:08 ` Otared Kavian
2015-01-21 11:55   ` Keith Schultz
2015-01-21 12:48     ` Otared Kavian
2015-01-21 13:31       ` Keith J. Schultz [this message]
2015-01-21 22:01         ` Otared Kavian
2015-01-26 16:19     ` Gerben Wierda
2015-01-26 16:29       ` Wolfgang Schuster
2015-01-26 18:51       ` Keith Schultz
2015-01-26 21:49         ` Gerben Wierda
2015-01-27 12:06           ` Keith J. Schultz
2015-02-23 21:33             ` Gerben Wierda
2015-02-23 21:37               ` Aditya Mahajan
2015-01-21 11:29 ` Keith J. Schultz

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=46F8597C-745D-4888-B96F-773E17456D10@web.de \
    --to=keithjschultz@web.de \
    --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).