From: David Arnold <darnold@northcoast.com>
Cc: pragma@wxs.nl
Subject: Searching
Date: Thu, 02 Sep 1999 13:01:39 -0700 [thread overview]
Message-ID: <3.0.5.32.19990902130139.00b38100@mail.northcoast.com> (raw)
Hans,
This from the Miktex site:
Improving the edit/view/edit cycle
Use TeX's --src option to enrich the DVI file with source file information.
Benefits
You will be able to synchronize the DVI previewer with the text
editor while you are editing the TeX source file.
You will be able to synchronize the text editor with the DVI
previewer while you are viewing the DVI file.
Details
The command
latex --src mydoc.tex
will enrich the DVI file mydoc.dvi with source file information, i.e.
mydoc.dvi will contain references to mydoc.tex.
I'd like to try to implement this, but I am not sure to insert the switch
--src in light of I am using texexec. The best situation for me would be
able to put something on the first line of master.tex that texexec would
interpret.
Any ideas?
next reply other threads:[~1999-09-02 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-02 20:01 David Arnold [this message]
1999-09-02 20:32 ` Searching Tobias Burnus
1999-09-02 21:59 ` Searching 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=3.0.5.32.19990902130139.00b38100@mail.northcoast.com \
--to=darnold@northcoast.com \
--cc=pragma@wxs.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).