From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problem with t-filter/t-vim
Date: Tue, 19 Oct 2010 10:02:28 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1010190959280.25821@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <AANLkTin5G-H694S52NiwWZv4bnGQQ9V8DqNBiQZEknxz@mail.gmail.com>
On Tue, 19 Oct 2010, Chen Shen wrote:
> 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.
A grouping bug. Does it work with the latest version from the deb branch.
> 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.
That is by design. Currently, 2context.vim simply adds some markup, and
the resutant file is read using
\startlines
....
\stoplines
\start-stop-lines converts each line to a paragraph. You can try
\startsetups vim:setups
\setupwhitespace[none]
\stopsetups
\setupvimtyping[setups=vim:setups]
to see if it helps.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-10-19 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 7:57 Chen Shen
2010-10-19 14:02 ` Aditya Mahajan [this message]
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=alpine.LNX.2.01.1010190959280.25821@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).