From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: updating context on Ubuntu 6.06
Date: Wed, 26 Jul 2006 16:17:00 +0100 [thread overview]
Message-ID: <E1G5l88-0002l7-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Wed, 26 Jul 2006 11:36:58 +0200." <44C737BA.9070702@elvenkind.com>
> >>1. (optional cleanup) Delete the old Context-installed files in
> >> ~/texmf/. This step is optional, but I do it so that I can track the
>
> I am not so sure that step is optional. Because if the preinstalled
> version had a cont-sys.tex or cont-usr.tex, then this step may be
> required to make sure you are not using an out-of-date version of
> these files.
Good point, thanks. I'll incorporate it into the eventual wiki page.
> A somehwat more flexible version is
>
> #!/bin/sh
> ruby `kpsewhich --format='texmfscripts' texmfstart.rb` $@
>
> (also notice the lack of quotes around $@)
According to the bash man entry:
@ Expands to the positional parameters, starting from one. When
the expansion occurs within double quotes, each parameter
expands to a separate word. That is, "$@" is equivalent to "$1"
"$2" ...
So if you ran texmfstart with
texmfstart --option="hi there"
then the $@ form would produce
texmfstart.rb --option=hi there
which would leave 'there' standing alone as a second argument.
Whereas the "$@" form would produce
texmfstart.rb "--option=hi there"
This second form is what you want, no?
> > $ texmfstart ctxtools --updatecontext
> > kpsewhich: option `--expand-var' requires an argument
>
> Do not worry about that until the rest of the install is correct, it
> may start working automagically.
It didn't work magically, but Jano Kula's suggestion about TEXMFLOCAL
made it work. I looked at the TEXMFLOCAL in the /etc/texmf/texmf.cnf
and did:
TEXMFLOCAL=/usr/local/share/texmf texmfstart ctxtools --updatecontext
That worked fine except now there's version clash. During the update
it said
CtxTools | updating /usr/local/share/texmf
and it downloaded the cont-tmf.zip there and unzipped it, remade the
formats, and put them under ~/.texmf-var. So now the formats are
based on the new context (2006.07.24) but for example,
$ texmfstart ctxtools --contextversion
CtxTools | context version: 2006.07.14 12:08 (/home/sanjoy/texmf/tex/context/base/context.tex)
CtxTools | context version: 2006.07.14 12:08 (/home/sanjoy/texmf/tex/context/base/cont-new.tex)
So texmfstart is finding the older source files in ~/texmf (from the
2006.07.14 update) although the formats themselves are newer. And
trying a simple file gives:
$ texexec t
...
ConTeXt ver: 2006.07.14 12:08 fmt: 2006.7.26 int: english mes: english
which worked fine, I guess since the two versions are sufficiently
compatible. To avoid this problem, is it possible to put the new
version in ~/texmf instead of in TEXMFLOCAL? Although in ~/texmf may
be wrong for others, so it's a difficult problem...
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
next prev parent reply other threads:[~2006-07-26 15:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 20:24 Sanjoy Mahajan
2006-07-26 8:36 ` Ralf Schmitt
2006-07-26 9:36 ` Taco Hoekwater
2006-07-26 10:36 ` Jano Kula
2006-07-26 11:20 ` Ralf Schmitt
2006-07-26 15:17 ` Sanjoy Mahajan [this message]
2006-07-26 16:13 ` Taco Hoekwater
2006-07-26 19:47 ` Sanjoy Mahajan
2006-07-26 20:34 ` Taco Hoekwater
2006-07-26 20:57 ` Hans Hagen
2006-07-26 21:01 ` Hans Hagen
2006-07-26 21:29 ` Switching Font Size in a Natural Table Neal Lester
2006-08-01 23:31 ` Mojca Miklavec
2006-07-26 22:10 ` updating context on Ubuntu 6.06 Sanjoy Mahajan
2006-07-27 8:05 ` Hans Hagen
2006-07-27 8:46 ` Taco Hoekwater
2006-07-27 8:04 ` Hans Hagen
2006-07-27 12:37 ` Sanjoy Mahajan
2006-07-26 21:02 ` Hans Hagen
2006-07-26 14:43 ` Sanjoy Mahajan
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=E1G5l88-0002l7-00@skye.ra.phy.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--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).