ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with first setup of StandAlone ConTeXt
Date: Wed, 16 Dec 2015 17:48:04 +0100	[thread overview]
Message-ID: <38A1BD39-A517-4B86-B281-2C8D32EC11A7@gmail.com> (raw)
In-Reply-To: <7A687EF7-0675-4900-A7FB-9BA831E8B664@tufts.edu>

Hi Bruce,

You have three solutions in order to solve the TeXShop issue. Here they are: 

Solution 1: add the following line at the top of your source file:

%!TEX TS-program = mkiv

Note that in the above you should replace « mkiv » with whatever engine name known to your TeXShop installation (for instance « ContextSuite», or any other name you have, or (may God forgive both of us…) even « latex »…). When you typeset with ConTeXt, the TeXShop will use the chosen engine.

Solution 2: when your source file is open you should have at the top your window a small menu named « Program ». Click on that menu and among the programs (that is the engines) choose th eone you want.

Solution 3: open the TeXShop Preferences and in the « Typesetting » pane , on the upper left part of the resulting window choose the radio button « Command listed below » and type the name of your preferred engine.

Best regards: OK

> On 16 Dec 2015, at 17:34, Bruce Boghosian <bruce.boghosian@tufts.edu> wrote:
> 
> I see, thanks.  I did use --engines=luatex.  I was aware that Mark II had been superseded by Mark IV, but I hadn't realized that texexec was the same thing as Mark II.  OK, so I won't worry about that issue any more.
> 
> It seems that my only remaining problem is the aforementioned TeXShop issue.  I will keep working on it.
> 
> Best,
> Bruce
> 
> 
>> On Dec 16, 2015, at 11:25 AM, Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
>> 
>> On 16 December 2015 at 17:10, Bruce Boghosian wrote:
>>> 
>>> Also, FWIW, I note that de Boer's document, "LaTeX in proper ConTeXt"
>>> recommends compiling from the command line using texexec rather than
>>> context.  This does not work for me.  The command "texexec" exists, and I
>>> can run it, but it does not produce a .pdf file -- just a .tmp file.
>> 
>> That document is a very old one. Nowadays context is preferred to
>> texexec (also known as Mark II or MkII). If you installed context with
>> --engines=luatex you explicitly did not installed prerequisites for
>> Mark II (pdftex with fonts etc.).
>> 
>> Mojca
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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-12-16 16:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 16:37 Boghosian, Bruce
2015-12-15  9:06 ` Mojca Miklavec
2015-12-15 12:47   ` Bruce Boghosian
2015-12-15 13:47     ` Mojca Miklavec
2015-12-15 14:11       ` Bruce Boghosian
2015-12-15 14:47         ` Jan U. Hasecke
2015-12-15 14:54           ` Bruce Boghosian
2015-12-15 15:20             ` Mojca Miklavec
2015-12-15 17:17               ` Bruce Boghosian
2015-12-15 22:00                 ` Bruce Boghosian
2015-12-16  7:27                   ` Otared Kavian
2015-12-16 16:10                     ` Bruce Boghosian
2015-12-16 16:25                       ` Mojca Miklavec
2015-12-16 16:34                         ` Bruce Boghosian
2015-12-16 16:48                           ` Otared Kavian [this message]
2015-12-17 13:54                             ` Bruce Boghosian
2015-12-15 10:18 ` Hans Hagen
2015-12-15 10:29   ` Mojca Miklavec
2015-12-15 12:05     ` Hans Hagen
     [not found] <mailman.1.1450177201.3279.ntg-context@ntg.nl>
2015-12-15 12:26 ` Robert Blackstone

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=38A1BD39-A517-4B86-B281-2C8D32EC11A7@gmail.com \
    --to=otared@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).