From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: synctex, TeXShop and \input files
Date: Fri, 29 Sep 2017 08:21:59 +0200 [thread overview]
Message-ID: <0031F1BC-A48D-4008-8EBF-EAEF44BDB2B1@gmail.com> (raw)
In-Reply-To: <27c2d3e2-8c12-1730-c0af-8d63e1dee140@wxs.nl>
Hi Hans,
Thanks for the hint. Indeed every input file has got a reference in synctex file produced by ConTeXt.
(I noticed also that during the typesetting ConTeXt creates another file with a suffix syncctx which is wiped out at the end of the processinng).
On the other hand after reading your hint I tried the same files with another application, TeXWorks, and there the syncing works perfectly.
Therefore it seems that this is a problem with TeXShop and I am going to report a bug with Richard Koch.
Best regards: OK
> On 28 Sep 2017, at 22:44, Hans Hagen <pragma@wxs.nl> wrote:
>
> On 9/28/2017 9:30 PM, Otared Kavian wrote:
>>> On 28 Sep 2017, at 19:12, Hans Hagen <pragma@wxs.nl <mailto:pragma@wxs.nl>> wrote:
>>>> […]
>>> files in the tex tree (styles and such) are not accessible (protected) as you don't want them to get messed up
>> Sure, but my problem is that I have a document with five or six chapters. Each chapter is included in files which are named for instance
>> chapter-1.tex
>> chapter-2.tex
>> and so on. Then my file main.tex contains the lines
>> \input chapter-1.tex
>> \input chapter-2.tex
>> and so on, in order to typeset the whole document. But now I don’t know how to sync the PDF file with the source files chapter-1.tex, chapter-2.tex, etc., in order to correct mistakes or mistypings when I discover them in the PDF file.
>> Clearly, the main file and these files are residing in the same directory.
>> Is there a way to tell context to look into the directory where the main file and my chapter files are?
>
> it works here .. you can look in the synctex file to see if the files get references
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2017-09-29 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 14:44 Otared Kavian
2017-09-28 17:12 ` Hans Hagen
2017-09-28 19:30 ` Otared Kavian
2017-09-28 20:44 ` Hans Hagen
2017-09-29 6:21 ` Otared Kavian [this message]
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=0031F1BC-A48D-4008-8EBF-EAEF44BDB2B1@gmail.com \
--to=otared@gmail.com \
--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).