From: "George N. White III" <aa056@chebucto.ns.ca>
Subject: Re: Re: problems with embedded spaces in file paths (Win32)
Date: Thu, 18 Sep 2003 22:18:56 -0300 (ADT) [thread overview]
Message-ID: <Pine.LNX.4.58.0309182203250.2612@cerberus.cwmannwn.nowhere> (raw)
In-Reply-To: <Pine.OSF.4.58.0309172258060.14380@sirppi.helsinki.fi>
On Wed, 17 Sep 2003, Mari Voipio wrote:
> It does not seem to bother TeXLive ConTeXt that the .tex files are in a
> path with couple of spaces (like c:\Documents and Settings\Mari\My
> Documents\ConTeXt\test.tex) as long as TeXLive itself is installed
> somewhere without spaces.
This morning I uninstalled the Sept. 5 rc and installed today's (Sept. 18)
rc in C:\TeXLive on a Win98 system with HOME=c:\home to avoid all cases
where spaces get into file paths. Again, kpathsea run via the command
line found my texexec.ini, but the irun generated texexec.exe failed to
find it. This time I modified "sub found_ini_file" in texexec.pl to
replace the "/" with "\" in $kpsewhich. This is rather odd, as in most
cases not involving a command line you can use "/" in file paths. There
are probably other places were backtick is used that will require the same
change, and they are only to be used for "$dosish" systems.
It is past my bedtime, so I'll have to cut this short. Weather
permitting, I'll be out of the office until October, but I'll try to post
some reasonable patches at the earliest opportunity.
--
George N. White III <aa056@chebucto.ns.ca>
prev parent reply other threads:[~2003-09-19 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2003-09-17 20:09 ` Mari Voipio
2003-09-17 21:16 ` George N. White III
2003-09-19 1:18 ` George N. White III [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=Pine.LNX.4.58.0309182203250.2612@cerberus.cwmannwn.nowhere \
--to=aa056@chebucto.ns.ca \
--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).