ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Linux upgrade
Date: Fri, 23 Jun 2006 11:54:26 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0606231149140.3668@nqvgln> (raw)
In-Reply-To: <200606231017.17609.john@wexfordpress.com>

On Fri, 23 Jun 2006, John R. Culleton wrote:

> On Thursday 22 June 2006 09:37 pm, Aditya Mahajan wrote:
>> Hi John,
>>   Others will be able to tell you better on how to upgrade on Linux (I
>> myself use windows) but
>>
>>> standard /usr/share/texmf tree. No joy. I get messages telling me to use
>>> the texmfstart command instead. This is as I recall a Windows thingie.
>>
>> you need texmfstart on linux also. Does everything work fine if you
>> use texmfstart?
>>
> Not yet. I am unsure what texmfstart is supposed to do. It is a
> Ruby script. Does it replace texexec or does it manage texexec?

texmfstart is a ruby script which manages texexec and other context 
script. Basically, instead of calling any script directly, call it 
using texmfstart. So,

texexec filename

becomes

texmfstart texexec filename

texutil

becomes

texmfstart texutil

(though most of the functionality has been replaced by ctxtools) and 
so on. texmfstart makes sure that the script at the right path is 
called and also speeds up things a little when calling different 
utilities. It also provides some useful things like ifchanged and 
iftoughed. There is a texmfstart manual (bit out of date). Simply 
typing texmfstart on the shell lists the available switches.

Aditya

  reply	other threads:[~2006-06-23 15:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 23:18 John R. Culleton
2006-06-23  1:37 ` Aditya Mahajan
2006-06-23 14:17   ` John R. Culleton
2006-06-23 15:54     ` Aditya Mahajan [this message]
2006-06-23 17:19       ` Hans Hagen
2006-07-05 14:25         ` Aditya Mahajan
2006-06-23  8:44 ` Taco Hoekwater
2006-07-05 23:56   ` gnwiii
2006-07-11 10:23     ` Taco Hoekwater
2006-06-23  9:39 ` luigi scarso
2006-06-23 16:34 ` Peter Münster
2006-06-23 22:00   ` John R. Culleton
2006-06-23 22:48   ` John R. Culleton
2006-06-24  7:46     ` Peter Münster

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=Pine.WNT.4.63.0606231149140.3668@nqvgln \
    --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).