From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: Making a verbatim file for another language
Date: Fri, 29 Dec 2006 14:09:21 +0100 [thread overview]
Message-ID: <6faad9f00612290509n5694464er42ff74533b62d022@mail.gmail.com> (raw)
In-Reply-To: <FA2C5A3B-4742-4E47-89AF-40B559FBD64E@mac.com>
On 12/29/06, cormullion@mac.com wrote:
> OK, I think vim works OK here, so this is what I tried:
>
> ...
> \setupcolors[state=start]
>
> \usemodule[vimsyntax]
>
> \definetypeVIMfile [typeRUBY] [syntax=ruby]
>
> \typeRUBY[typeRUBY]{fibo.rb}
>
> \defineVIMtyping[RUBY][syntax=ruby]
>
> \startRUBY
> # This is a ruby program
>
> puts "Hello World"
> \stopRUBY
> ...
>
> Error message was this:
>
> system : no macros found in module vimsyntax
Weird! Do you have a file t-vimsyntax.tex in the same folder as the
file where you're running the sample? An alternative is to place the
file under [texmf]/tex/context/third/t-vimsyntax.tex and then run
"[sudo] mktexlsr".
But in any case you need to have 2context.vim in the same folder
(there is no support for an arbitrary path of the script yet).
> ! Undefined control sequence.
> l.15 \definetypeVIMfile
> [typeRUBY] [syntax=ruby]
>
> So it looks like it didn't really get started... The files t-
> vimsyntax.text and 2context.vim are rattling loose in the directory...
It has to be *t-vimsyntax.tex*, not *.text*, if that's the case. But
if I try to rename the file, I get "module vimsyntax not found", while
you get "no macros found in module vimsyntax".
While googling through the archive I've found the following message:
http://archive.contextgarden.net/message/20050215.182506.0838140e.en.html
Citing:
> tracefiles showed that ConTeXt was expecting a file
> name with six or less characters after t-; my module was called
> t-utfgreek, so ConTeXt was looking for t-utfgre and couldn't find it
Which version of TeX/ConTeXt are you using? (Perhaps Hans has changed
something in the meantime, to make that work again.) Are you using
Gerben's i-Installer? In that case and if you have a chance, can you
please test the new TeXLive-based distribution?
(I didn't know that 8-char was still a limitation nowadays.)
Mojca
next prev parent reply other threads:[~2006-12-29 13:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 9:24 cormullion
2006-12-25 10:38 ` Taco Hoekwater
2006-12-25 15:22 ` cormullion
2006-12-26 16:59 ` Henning Hraban Ramm
2006-12-26 18:47 ` Mojca Miklavec
2006-12-26 21:25 ` cormullion
2006-12-27 21:41 ` Aditya Mahajan
2006-12-28 8:15 ` cormullion
2006-12-28 17:09 ` Aditya Mahajan
2006-12-28 18:05 ` cormullion
2006-12-28 23:47 ` Mojca Miklavec
2006-12-29 8:46 ` cormullion
2006-12-29 13:09 ` Mojca Miklavec [this message]
2006-12-29 15:37 ` Aditya Mahajan
2006-12-29 15:42 ` cormullion
2006-12-29 15:59 ` Aditya Mahajan
2006-12-29 16:36 ` cormullion
2006-12-29 18:39 ` Mojca Miklavec
2006-12-30 9:22 ` Jarimatti Valkonen
2006-12-30 14:18 ` cormullion
2006-12-30 21:24 ` Jarimatti Valkonen
2006-12-31 11:51 ` cormullion
2006-12-31 13:40 ` Mojca Miklavec
2006-12-31 16:57 ` cormullion
2006-12-25 18:12 ` Mojca Miklavec
2006-12-25 19:37 ` Aditya Mahajan
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=6faad9f00612290509n5694464er42ff74533b62d022@mail.gmail.com \
--to=mojca.miklavec.lists@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).