From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/13250 Path: main.gmane.org!not-for-mail From: George White Newsgroups: gmane.comp.tex.context Subject: problems with embedded spaces in file paths (Win32) Date: Mon, 15 Sep 2003 13:08:44 -0300 (ADT) Sender: ntg-context-admin@ntg.nl Message-ID: Reply-To: ntg-context@ntg.nl NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: sea.gmane.org 1063650289 29809 80.91.224.253 (15 Sep 2003 18:24:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 15 Sep 2003 18:24:49 +0000 (UTC) Original-X-From: ntg-context-admin@ntg.nl Mon Sep 15 20:24:47 2003 Return-path: Original-Received: from ref.vet.uu.nl ([131.211.172.13] helo=ref.ntg.nl) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19yy1n-0004ol-00 for ; Mon, 15 Sep 2003 20:24:47 +0200 Original-Received: from ref.ntg.nl (localhost.localdomain [127.0.0.1]) by ref.ntg.nl (Postfix) with ESMTP id A3BFF10B6E; Mon, 15 Sep 2003 20:24:44 +0200 (MEST) Original-Received: from halifax.chebucto.ns.ca (chebucto.ns.Ca [192.75.95.75]) by ref.ntg.nl (Postfix) with ESMTP id BC1DD10ACC for ; Mon, 15 Sep 2003 18:08:57 +0200 (MEST) Original-Received: (from localhost user: 'aa056' uid#15055 fake: STDIN (aa056@halifax.chebucto.ns.ca)) by halifax.chebucto.ns.ca id ; Mon, 15 Sep 2003 13:08:44 -0300 Original-To: ntg-context@ntg.nl Errors-To: ntg-context-admin@ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.comp.tex.context:13250 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:13250 I don't normally use Win32, but I want to convert our 4AllTeX addicts to TeX Live 2003. In testing release candidates, I encountered a few problems with context and texexec. The most recent tests were with the Sept. 5 release candidate (using the "install" CD). 1. on Win32, kpsewhich often fails to find texexec.ini. I created a texexec.ini in texmf-var/context/config and verified that it is listed in the ls-R. My conjecture is that this failure occurs if and only if the final component of the nme of the current working directory contains an embedded space, e.g., "C:\My Documents". Texexec takes a very long time to run (searching the texmf trees on an unloved and unwanted PIII 300mhz), so I haven't done a lot of testing/debugging. I haven't encountered any other kpathsea failures. I can work around this by tweaking texexec.pl, but it would be comforting to have an explanation. 2. ConTeXt texexec uses $ENV{"HOME"} to set a value in filename.tmp, e.g., on unix: $ cat try.tex \starttext \input story \stoptext $ texexec try $ cat try.tmp % try.top \unprotect \setupsystem[\c!gebied={/user/gwhite/}] %---- set from $ENV{"HOME"} \setupsystem[\c!n=1] \setupsystem[inputfile=try.tex] \protect If, e.g. HOME="/x y", the formatted document gets an extra page containing "y//cont-err". On Win32, it seems common to have spaces in "%HOME%". In particular, for WinXP, a value appears to be constructed by the texexec.ini binary (created using irun) if %HOME% is not set. I can work around this by asking users to explicitly set HOME to something safe. -- George White 189 Parklea Dr., Head of St. Margarets Bay, Nova Scotia B3Z 2G6