From: Chen Shen <hashhsah@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: problem with t-filter/t-vim
Date: Tue, 19 Oct 2010 15:57:44 +0800 [thread overview]
Message-ID: <AANLkTin5G-H694S52NiwWZv4bnGQQ9V8DqNBiQZEknxz@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]
Hi Adityam,
I am using the t-filter/t-vim module, and got stuck with two problems with
it.
1. everything works fine if there is only one \definevimtyping declaration.
However, if i declare two of them, as in the following:
%%%%%%%
\definevimtyping[PythonCode][syntax=python]
\definevimtyping[CPPCode][syntax=cpp]
\startPythonCode
... % Code A
\stopPythonCode
\startPythonCode
... % Code B
\stopPythonCode
%%%%%%%
The counter for the temporary files is never incremented. So there is only
"jobname-externalfilter-PythonCode-0.tmp" in the directory.
Consequently, Code B appears twice in the produced PDF, while Code A never
appears.
2. Every line in the Python code becomes a new paragraph in ConTeXt. I
wonder if this could be changed.
I am using \setupwitespace[line], so the spacing between two lines of source
is too large.
I am using the dev/ branch in the github repository.
Thank you very much.
regards,
shenchen
[-- Attachment #1.2: Type: text/html, Size: 1260 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2010-10-19 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 7:57 Chen Shen [this message]
2010-10-19 14:02 ` 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=AANLkTin5G-H694S52NiwWZv4bnGQQ9V8DqNBiQZEknxz@mail.gmail.com \
--to=hashhsah@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).