ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [t-vim] Line numbers
Date: Wed, 23 Feb 2011 10:21:15 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1102231017040.18794@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20110223111955.217ff55c@glyph>

On Wed, 23 Feb 2011, Marco wrote:

> I stumbled over one thing: When set directory=tmp the temporary files are sent
> to the tmp directory except the md5 hashes of external file code, these are
> put in the working dir.

The md5 hashes are in the same directory as the file. So, in case you are 
including a file from the current directory, the md5 hash will also be 
there. So, the easiest solution is to move (or perhaps simlink) the file 
to the temporary directory. Then you can include the file tmp/t.tex and 
the md5 hash will be created in the tmp directory.

> Is it possible to convince the context script to remove the temporary stuff
> when called with the --purgeall option?

I will look into that. I guess that the easiest way out is that, instead 
of using .vimout extension, I use .tmp extension. Then, all the temporary 
files will be removed by --purgeall.

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
___________________________________________________________________________________


  reply	other threads:[~2011-02-23 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19 14:56 Marco
2011-02-22  1:10 ` Aditya Mahajan
2011-02-22  9:15   ` Marco
2011-02-22 19:26     ` Aditya Mahajan
2011-02-23 10:19       ` Marco
2011-02-23 15:21         ` Aditya Mahajan [this message]
2011-02-23 15:43           ` Marco
2011-02-23 16:16             ` Aditya Mahajan
2011-02-23 16:54               ` Marco
2011-02-23 17:49                 ` Aditya Mahajan
2011-02-23 18:27                   ` Marco
2011-02-23 19:39                     ` Aditya Mahajan
2011-02-25 12:08                 ` Hans Hagen
2011-02-26 23:24                 ` Aditya Mahajan
2011-02-27 17:20                   ` Marco
2011-02-27 17:41                     ` 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.01.1102231017040.18794@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).