ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Hans Hagen" <pragma@wxs.nl>, "\"H. Özoguz\"" <h.oezoguz@mmnetz.de>
Subject: Re: Synctex problems with context and texworks
Date: Mon, 12 Nov 2012 09:37:33 +0100	[thread overview]
Message-ID: <50A0B54D.7050708@elvenkind.com> (raw)
In-Reply-To: <50A0B3D1.7050600@wxs.nl>

On 11/12/2012 09:31 AM, Hans Hagen wrote:
> On 11/12/2012 8:53 AM, "H. Özoguz" wrote:
>> Hello there,
>>
>> sind yesterday the pdf-view with synctex had no problems. But today,
>> without any change (afaik), it does not work anymore. The arguments for
>> compiling with context.exe are
>>
>> --synctex
>> $fullname
>>
>> That is default. I deleted the .synctex.gz files manually, but it did
>> not help. What could be the problem?
>
> if you get a synctex.gz file then the problem is with texworks

The are no changes in the way context produces the filename paths?
Synctex is a bit fragile when it comes to filenames within the
<jobname>.synctex[.gz] file.

Best wishes,
Taco

___________________________________________________________________________________
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:[~2012-11-12  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  7:53 "H. Özoguz"
2012-11-12  8:31 ` Hans Hagen
2012-11-12  8:37   ` Taco Hoekwater [this message]
2012-11-12  8:58 ` Vladimir Lomov

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=50A0B54D.7050708@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=h.oezoguz@mmnetz.de \
    --cc=ntg-context@ntg.nl \
    --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).