From: Hans Hagen <pragma@wxs.nl>
Subject: Re: textools --fixtexmftrees : parse error !
Date: Tue, 02 Nov 2004 10:56:42 +0100 [thread overview]
Message-ID: <418759DA.6070907@wxs.nl> (raw)
In-Reply-To: <a06002000bdacff5f7f56@[62.134.72.100]>
Steffen Wolfrum wrote:
> /usr/local/teTeX/share/texmf.local/scripts/context/ruby/textools.rb --fixtexmftrees ~/Library/texmf
> -:1: parse error
> /usr/local/teTeX/share/texmf.local/scripts/context/ruby/textools.rb --fixtexmftrees ~/Library/texmf
> ^
what happens if you replace ~ with /home/yourname/
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
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-11-02 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 9:18 Steffen Wolfrum
2004-11-02 9:56 ` Hans Hagen [this message]
2004-11-02 12:00 Steffen Wolfrum
2004-11-02 12:32 Steffen Wolfrum
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=418759DA.6070907@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).