From: Johannes Graumann <johannes_graumann@web.de>
To: ntg-context@ntg.nl
Subject: Re: DEB of Context 2008-01-28 anybody?
Date: Wed, 13 Feb 2008 16:48:35 +0100 [thread overview]
Message-ID: <fov3gf$djk$1@ger.gmane.org> (raw)
In-Reply-To: <6faad9f00802130729mb5a0214nd972bfba52e550bc@mail.gmail.com>
Mojca Miklavec wrote:
> but running setuptex means: [dot] setuptex. Else it has no effect.
>
> Here's the whole procedure once more:
>
> rsync -av
> rsync://contextgarden.net/minimals/setup/osx-intel/first-setup.sh .
> ./first-setup.sh
> # then, you might need to skip a bunch of currently broken greek patterns)
> cd tex
> # note the dot !!!
> . setuptex
> # generate luatex format - only because its autogeneration
> # is broken at the moment
> texexec --make --lua en
This did it and made everything in this gigantoine thread work ... thanks!
How do I do a upgrade, rather than a fresh install?
Running "./first-setup.sh" again?
Thanks!
Joh
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-02-13 15:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 16:35 Johannes Graumann
2008-02-06 22:52 ` Joel C. Salomon
2008-02-09 11:48 ` Johannes Graumann
2008-02-09 14:49 ` Wolfgang Schuster
2008-02-09 15:09 ` Johannes Graumann
2008-02-09 15:15 ` Wolfgang Schuster
2008-02-09 15:21 ` Johannes Graumann
2008-02-09 19:44 ` Johannes Graumann
2008-02-09 20:06 ` Mojca Miklavec
2008-02-09 20:57 ` Johannes Graumann
2008-02-10 14:48 ` Mojca Miklavec
2008-02-10 15:03 ` Hans Hagen
2008-02-11 10:35 ` Johannes Graumann
2008-02-11 10:47 ` Hans Hagen
2008-02-11 11:23 ` Johannes Graumann
2008-02-11 20:00 ` Johannes Graumann
2008-02-11 20:15 ` Hans Hagen
2008-02-11 20:57 ` Johannes Graumann
2008-02-11 21:06 ` Hans Hagen
2008-02-11 21:15 ` Johannes Graumann
2008-02-11 22:24 ` Hans Hagen
2008-02-12 7:45 ` Johannes Graumann
2008-02-12 8:00 ` Hans Hagen
2008-02-12 19:38 ` Johannes Graumann
2008-02-12 20:59 ` Hans Hagen
2008-02-12 21:21 ` Johannes Graumann
2008-02-12 21:32 ` Hans Hagen
2008-02-12 21:45 ` Johannes Graumann
2008-02-12 22:09 ` Hans Hagen
2008-02-13 8:01 ` Johannes Graumann
2008-02-13 8:13 ` Hans Hagen
2008-02-13 8:50 ` Johannes Graumann
2008-02-13 9:02 ` Hans Hagen
2008-02-13 8:16 ` Taco Hoekwater
2008-02-13 8:40 ` luigi scarso
2008-02-13 11:21 ` Johannes Graumann
2008-02-13 11:40 ` Taco Hoekwater
2008-02-13 11:53 ` Mojca Miklavec
2008-02-13 14:32 ` Johannes Graumann
2008-02-13 14:43 ` Johannes Graumann
2008-02-13 14:53 ` Mojca Miklavec
2008-02-13 14:59 ` Johannes Graumann
2008-02-13 15:29 ` Mojca Miklavec
2008-02-13 15:48 ` Johannes Graumann [this message]
2008-02-13 16:00 ` Mojca Miklavec
2008-02-09 17:21 ` Aditya Mahajan
2008-02-09 18:32 ` Johannes Graumann
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='fov3gf$djk$1@ger.gmane.org' \
--to=johannes_graumann@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).