From: Hans Hagen <pragma@wxs.nl>
Subject: Re: new version
Date: Fri, 27 May 2005 20:41:07 +0200 [thread overview]
Message-ID: <429769C3.5010205@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0505272011000.12321@gaston.free.fr>
Peter Münster wrote:
> On Fri, 27 May 2005, Adam Lindsay wrote:
>
>
>>Hans Hagen said this at Fri, 27 May 2005 01:34:57 +0200:
>>
>>
>>>what does
>>>
>>> texmfstart newtexexec --make --all
>>>
>>>do?
>>
>>Interesting...
>>It builds the formats (not engine aware in terms of where it puts
>>the .fmt files--at least it uses different switches compared to what I'm
>>used to), but (old)texexec did that too.
>>
>>What's interesting is that it doesn't insist on rebuilding the format on
>>a normal (--pdf) run. (And it's fast: does it buffer the terminal output?)
>
>
> Hello,
> I have the same problem on Linux, but I don't have texmfstart...
> Are there other solutions or is texmfstart now needed to run texexec?
> Cheers, Peter
you do have texmfstart, just copy texmfstart.rb to texmfstart in one of your bin
paths (texmfstart is one of the core components of the context scripts, being
the only way i can guarantee upward compatibility when drastic changes take
place in the tds/distributions)
(there is a manual on the website)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-05-27 18:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 15:34 Hans Hagen
2005-05-25 18:42 ` Taco Hoekwater
2005-05-25 19:00 ` Hans Hagen
2005-05-25 19:25 ` Taco Hoekwater
2005-05-27 15:07 ` Taco Hoekwater
2005-05-27 18:17 ` Hans Hagen
2005-05-28 18:18 ` Stuart Jansen
2005-05-25 19:24 ` feature request:-) Idris Samawi Hamid
2005-05-25 20:06 ` Hans Hagen
2005-05-25 19:26 ` new version Idris Samawi Hamid
2005-05-25 20:07 ` Hans Hagen
2005-05-26 21:57 ` Adam Lindsay
2005-05-26 23:29 ` Hans Hagen
2005-05-27 14:49 ` Adam Lindsay
2005-05-27 18:22 ` Hans Hagen
2005-05-27 19:09 ` Adam Lindsay
2005-05-26 23:34 ` Hans Hagen
2005-05-27 13:27 ` Adam Lindsay
2005-05-27 13:45 ` Hans Hagen
2005-05-27 18:20 ` Peter Münster
2005-05-27 18:41 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-25 18:14 Hans Hagen
2020-06-10 8:02 Hans Hagen
2020-06-10 15:05 ` Alan Bowen
2008-04-10 22:24 Hans Hagen
2008-04-11 4:33 ` Aditya Mahajan
2008-04-11 7:39 ` Hans Hagen
2008-04-11 7:50 ` Wolfgang Schuster
2008-04-11 9:48 ` Hans Hagen
2004-01-13 16:41 Hans Hagen
2003-09-17 17:47 Steffen Wolfrum
2003-09-17 12:25 Steffen Wolfrum
2003-09-17 16:00 ` Hans Hagen
2003-09-17 10:50 Hans Hagen
2003-08-07 16:02 Hans Hagen
2002-07-26 22:53 Hans Hagen
2002-07-27 19:34 ` Jens-Uwe Morawski
2002-07-29 7:15 ` Hans Hagen
2002-07-29 9:09 ` Jens-Uwe Morawski
2002-07-29 9:33 ` Hans Hagen
2002-07-30 9:56 ` Jens-Uwe Morawski
2002-07-30 21:06 ` Hans Hagen
2002-07-31 8:29 ` Jens-Uwe Morawski
2000-09-21 16:33 Hans Hagen
2000-01-24 11:13 Hans Hagen
2000-01-24 11:42 ` Mr. Wang Lei
2000-01-24 12:24 ` Tobias Burnus
2000-01-24 15:45 ` Hans Hagen
2000-01-24 15:32 ` Hans Hagen
2000-01-24 11:44 ` Tobias Burnus
2000-01-24 15:47 ` Hans Hagen
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=429769C3.5010205@wxs.nl \
--to=pragma@wxs.nl \
--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).