From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texexec/context error messages [MkIV] [vim]
Date: Sun, 23 May 2010 13:24:28 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1005231228540.11301@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20100523180742.GA27623@urvas>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 749 bytes --]
On Sun, 23 May 2010, Rogutės Sparnuotos wrote:
> And, the initial reason for these questions: has anyone figured out an
> appropriate 'errorformat' for the 'vim' editor, for use with MkIV? The one
> at http://www.vim.org/scripts/script.php?script_id=1925 seems to be
> working with MkII only...
Hans, does LuaTeX support -file-line-error flag like pdftex? If so, how do
I pass that (context --passon=-file-line-error) does not seem to work.
Rogutes, if you want to match
system : module * not found
Add
\%+Asystem\ %#:\ module\ %m\ not\ found,
to the error format (it will not jump to the line containing
\usemodule[...] because that information is not available in the log
file).
Aditya
[-- 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 prev parent reply other threads:[~2010-05-23 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 18:07 Rogutės Sparnuotos
2010-05-23 17:24 ` Aditya Mahajan [this message]
2010-05-25 0:00 ` texexec/context error messages [MkIV] Rogutės Sparnuotos
2010-05-25 6:40 ` Taco Hoekwater
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.1005231228540.11301@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).