From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Input path to include external files with vim module
Date: Tue, 19 Jun 2012 00:36:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1206190033310.1354@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20120618121748.14d007d1@homerow>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 741 bytes --]
On Mon, 18 Jun 2012, Marco wrote:
> does the vim module have a feature to specify the input path,
> similar to \usepath for context files or \setupexternalfigures
> [directory=…] for graphics?
Currently, it does not.
> I'm looking for a solution not to hard-code paths into my files.
> Example:
>
> \usemodule [vim]
> \definevimtyping [XML] [syntax=xml]
>
> \starttext
> \typeXMLfile{code/foo.xml} % what I do now
> %\typeXMLfile{foo.xml} % what is desired
> \stoptext
I'll see how easy it is to hook into the code for \usepath etc. It might
be best to add this feature to the filter module, but I'll have to come up
with another key as `directory` is already taken to specify output
directory.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 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:[~2012-06-19 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 10:17 Marco
2012-06-19 4:36 ` Aditya Mahajan [this message]
2012-06-20 17:33 ` Aditya Mahajan
2012-06-20 17:46 ` Hans Hagen
2012-06-20 19:46 ` Aditya Mahajan
2012-06-20 20:40 ` Marco
2012-06-20 20:58 ` 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=alpine.LNX.2.02.1206190033310.1354@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).