ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Fabrice POPINEAU <Fabrice.Popineau@supelec.fr>
Subject: Re: problems with embedded spaces in file paths (Win32)
Date: Mon, 15 Sep 2003 20:55:37 +0200	[thread overview]
Message-ID: <5.2.0.9.1.20030915205410.025f1110@server-1> (raw)
In-Reply-To: <Pine.GSO.3.95.iB1.0.1030915123533.20893B-100000@halifax.ch ebucto.ns.ca>

At 13:08 15/09/2003 -0300, you wrote:
>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.

can you check what happens when you add "" around the path? If i'm right, 
(i'll upload new binaries when some patch is done) the win binaries now accept

\input "some path"

(not sure if \input "some path"/somefile also works; can you test that?)

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

       reply	other threads:[~2003-09-15 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.3.95.iB1.0.1030915123533.20893B-100000@halifax.ch ebucto.ns.ca>
2003-09-15 18:55 ` Hans Hagen [this message]
2003-09-17  8:04   ` Fabrice Popineau
2003-09-15 16:08 George White
2003-09-15 21:28 ` Fabrice Popineau
2003-09-16 21:13   ` George N. White III
2003-09-17 17:17   ` George White

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=5.2.0.9.1.20030915205410.025f1110@server-1 \
    --to=pragma@wxs.nl \
    --cc=Fabrice.Popineau@supelec.fr \
    --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).