From: Hongwen Qiu <qiuhongwen@gmail.com>
To: Ntg-context <ntg-context@ntg.nl>
Subject: Re: Strange problem related to \usemodule
Date: Mon, 10 Oct 2011 15:26:27 +0800 [thread overview]
Message-ID: <1318231590.3135.31.camel@wind.river> (raw)
It seems that if I copied all of the module files under the current
directory, it works perfectly.
And of course mtxrun --locate t-vim.tex gives the correct location just
as indicated by my previously attached log file.
And there's only one environment variable corresponding to TeX settings:
$ env |grep -i TEX
PATH=/ifs2/S2PH/qiuhw/opt/context-1008/tex/texmf-linux-64/bin:.... (It's
very long)
Actually not only the modules under tex/texmf-modules not work on the
"Remote", but also modules under tex/texmf-local don't work either.
On Mon, 2011-10-10 at 12:57 +0800, Hongwen Qiu wrote:
> Hi,
>
> I have access to three machines both running GNU/Linux x86-64, I call
> them "Laptop", "Desktop" and "Remote" respectively here on.
>
> The "Laptop" has full access to the internet, so I always install and
> upgrade my ConTeXt Standalone on it when I'm home.
>
> At workplace, I can surfer the internet with the "Desktop" while the
> RSYNC port is blocked.
>
> I only can access the "Remote" through ssh from the "Desktop" without
> root privilege and can not access the internet.
>
> So, I always copied the ConTeXt standalone from my "Laptop" onto my
> "Desktop", and from my "Desktop" onto "Remote" if necessary. Then, I'll
> delete the cache before I set the PATH to the appropriate location and
> run context --make and mtxrun --generate.
>
> So the ConTeXt standalones are almost identical on both my "Desktop" and
> "Remote". And the following minimal example just works fine on my
> "Desktop" but failed on the "Remote",
> =========== Minimal Example ============================
> \usemodule[vim]
>
> \definevimtyping[RUBY][syntax=ruby]
>
> \starttext
>
> \startRUBY
> puts "Hello"
> \stopRUBY
>
> \stoptext
> =========================================================
> Actually, on "Remote", whatever module I use, it will prompt the
> Undefined Control Sequence error regarding the first command I used from
> that module with the module loaded correctly. Attached is the error log
> accompany the above minimal example.
>
> So, what can be the problem with my "Remote".
>
> TIA. for any help.
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2011-10-10 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 7:26 Hongwen Qiu [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-10 4:57 Hongwen Qiu
2011-10-10 12:09 ` Hans Hagen
2011-10-11 1:39 ` Hongwen Qiu
2011-10-11 3:09 ` Aditya Mahajan
2011-10-11 3:40 ` Hongwen Qiu
2011-10-11 7:26 ` Hans Hagen
2011-10-11 8:30 ` Hongwen Qiu
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=1318231590.3135.31.camel@wind.river \
--to=qiuhongwen@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).