From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: [***SPAM***] Continuous preview
Date: Tue, 27 Aug 2013 15:04:53 +0200 [thread overview]
Message-ID: <20130827130453.GC4204@homerow> (raw)
In-Reply-To: <521C9173.6030907@mmnetz.de>
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
On 2013–08–27 "H. Özoguz" wrote:
> For LaTex there exists a tool, named "latexmk", which allows a
> "preview continuous mode", that is to update the compiled pdf
> automatically. It is really very helpful!
I don't know latexmk, but updating the pdf is a feature of the pdf
reader, not of context. If you want to re-run the compilation when
the file has changed, you can use the mechanisms your operating
system provides. Every OS has a mechanism to watch files. Here is a
Linux example
while true do
inotifywait --event modify somefile.tex; context --batchmode somefile.tex
done
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- 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:[~2013-08-27 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 11:45 "H. Özoguz"
2013-08-27 13:04 ` Marco Patzer [this message]
2013-08-27 13:16 ` Marco Patzer
2013-08-27 19:12 ` Thangalin
2013-08-27 19:25 ` Romain Diss
2013-08-27 20:15 ` continuous preview (in TeXstudio) Ernst van der Storm
2013-08-27 19:21 ` [***SPAM***] Continuous preview Aditya Mahajan
2013-08-29 16:05 ` john Culleton
2013-08-28 7:10 "H. Özoguz"
2013-08-29 18:36 ` 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=20130827130453.GC4204@homerow \
--to=lists@homerow.info \
--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).