From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: making formats troubled
Date: Mon, 24 Sep 2007 18:21:40 +0200 [thread overview]
Message-ID: <46F7E414.9090304@wxs.nl> (raw)
In-Reply-To: <4042FC88-B2F7-4B17-A49A-3C9677D11796@science.uva.nl>
Hans van der Meer wrote:
> In This Way #12 of august 2007 I read on page 1:
>
> Since you update, make sure to remake the pdfTeX and XeTeX formats:
> texexec --make --all --pdftex
>
> I updated to 2007-09-10 and then an error with message:
>
> This is pdfTeX, Version 3.141592-1.40.5 (Web2C 7.5.6) (INITEX)
> \write18 enabled.
> (/usr/local/texlive/texmf-local/web2c/natural.tcx)
> entering extended mode
> ! I can't write on file `cont-en.log'.
> (Enter the null string to re-try, or <eof> to exit Default file
> extension is `.log')
>
> Where is it that the file cont-en.log will be written?
> And how can I change this location systematically (or can it be changed)
> to a place under my home directory?
> Maybe the problem is that I install my formats locally under a user name
> not being super user or system administrator (just a simple security
> precaution).
> Is the texexec script assuming here write rights need not in generally
> be granted to the script executing user? If so, can the script be adapted.
>
> By the way, cont-tfm.zip comes with script files not having a+x
> executing rights. It is a bit of nuisance to change these everytime an
> update comes along -- quite frequently thus. Is it possible to change this?
not now, i use zip to make the files and windows bits are not unix bits;
afaik, when a file is overwritten during unzip, the old bits are used;
concerning fmt paths ... you can set the variable texformats to some value
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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2007-09-24 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 15:40 Hans van der Meer
2007-09-24 15:47 ` Arthur Reutenauer
2007-09-24 16:21 ` Hans Hagen [this message]
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=46F7E414.9090304@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).