From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: very strange error with \xypos and vim-typing
Date: Tue, 16 Feb 2010 23:50:36 +0100 [thread overview]
Message-ID: <4B7B213C.4050404@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1002161720490.14011@ybpnyubfg.ybpnyqbznva>
Am 16.02.10 23:21, schrieb Aditya Mahajan:
> I can reproduce the error...but I have no idea what is causing it.
It's caused by the \strut in (t-vim.tex):
\def\dodotypevimfile[#1]#2%
{\@@vsbefore
\bgroup
\initializevimtyping{#1}%
\runvimsyntax{#2}%
% The strut is needed for the output to be the same when not using
% numbering. Otherwise, multiple par's are ignored. We need to
figure out
% a mechanism to imitate this behaviour even while using line
numbering.
\ifconditional\vimtypinginline \else
\strut%else the first line is shifted to the left
\fi
\input #2-vimsyntax.tmp\relax%
\ifconditional\vimtypinginline \removeunwantedspaces \fi
\egroup
\@@vsafter}
Wolfgang
___________________________________________________________________________________
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 prev parent reply other threads:[~2010-02-16 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 10:43 Peter Münster
2010-02-08 19:59 ` Peter Münster
2010-02-16 9:19 ` Peter Münster
2010-02-16 10:06 ` Hans Hagen
2010-02-16 10:31 ` Peter Münster
2010-02-16 22:21 ` Aditya Mahajan
2010-02-16 22:50 ` Wolfgang Schuster [this message]
2010-02-16 22:54 ` Aditya Mahajan
2010-02-17 9:58 ` Hans Hagen
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=4B7B213C.4050404@googlemail.com \
--to=schuster.wolfgang@googlemail.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).