From: "Jianning Dong" <jnd.dong@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: The problem of updating context manually using cont-tmf.zip
Date: Wed, 17 Sep 2008 16:23:18 +0800 [thread overview]
Message-ID: <e4cf04830809170123g7a958d16vfcc9023ad70d7ab9@mail.gmail.com> (raw)
In-Reply-To: <F595DD5A-7705-42C4-9C0E-CA5DDDF5C954@uni-bonn.de>
[-- Attachment #1.1: Type: text/plain, Size: 497 bytes --]
Now I'm using ctxtools to update automatically on another machine,
but the error occurs:
$context --version
Should I create the cache path /home/ben? [yes|no] [no] yes
fatal error: there is no valid (writable) cache path defined
I'm sure that /home/ben is a writable directory, so I think it's a bug.
Both ctxtools and my hand cannot handle the updating job correctly.
Perhaps the only way for me to use newer ConTeXt is installing the
ConTeXt minimal.
--
Hello world!
Every day is a new day.
[-- Attachment #1.2: Type: text/html, Size: 584 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-09-17 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 6:49 Jianning Dong
2008-09-17 7:11 ` Thomas A. Schmitz
2008-09-17 7:20 ` Jianning Dong
2008-09-17 8:08 ` Thomas A. Schmitz
2008-09-17 13:53 ` Aditya Mahajan
2008-09-17 14:17 ` Jianning Dong
2008-09-17 8:23 ` Jianning Dong [this message]
2008-09-17 8:39 ` Hans Hagen
2008-09-17 13:02 ` Jianning Dong
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=e4cf04830809170123g7a958d16vfcc9023ad70d7ab9@mail.gmail.com \
--to=jnd.dong@gmail.com \
--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).