ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: synctex
Date: Sun, 13 Sep 2009 12:45:00 +0200	[thread overview]
Message-ID: <4AACCD2C.7050206@wxs.nl> (raw)
In-Reply-To: <659945E1-A5C8-4955-9CAE-998189DFE611@googlemail.com>

Wolfgang Schuster wrote:
> 
> Am 12.09.2009 um 13:22 schrieb Hans Hagen:
> 
>> Vyatcheslav Yatskovsky wrote:
>>> Hi,
>>> I have a discussion with Jonathan Kew  about mark IV option in TeXWorks.
>>> We need to to pass the argument "-synctex=1" to the actual *tex 
>>> invocation, so that the engine creates a .synctex.gz file alongside 
>>> the ..pdf output; this enables texworks to jump back and forth 
>>> between source and preview locations.
>>> How this can be done?
>>
>> \synctex=1
>>
>> as it's not something that you want to have on by default
> 
> is a parameter for the context command (context --synctex filename) not 
> a option?

this had been considered but i then fear that editors will be set up by 
default to use that switch which is not what i've in mind; in that case 
the editor should have a config option either of not to enable that flag

so .. i haven't made up my mind yet

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-09-13 10:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1252749604.19174.ntg-context@ntg.nl>
2009-09-12 11:08 ` synctex Vyatcheslav Yatskovsky
2009-09-12 11:22   ` synctex Hans Hagen
2009-09-12 14:55     ` synctex Wolfgang Schuster
2009-09-13 10:45       ` Hans Hagen [this message]
2009-09-13  0:18     ` synctex Hartmut Henkel
2009-09-13  7:14       ` synctex Mojca Miklavec
2009-09-13 11:01       ` synctex Hans Hagen
2017-06-04 16:55 synctex Hans Hagen
2017-07-11 14:36 ` synctex Thomas Floeren
2017-07-11 15:09   ` synctex Hans Hagen
2017-07-11 21:06     ` synctex Thomas Floeren
2017-07-19  9:05       ` synctex Thomas Floeren
  -- strict thread matches above, loose matches on Subject: below --
2014-06-03  9:44 SyncTeX Trond Thorbjørnsen
2014-06-03 10:03 ` SyncTeX Mojca Miklavec
2014-06-03 14:09   ` SyncTeX Trond Thorbjørnsen
2008-08-22  9:25 synctex Patrick Gundlach

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=4AACCD2C.7050206@wxs.nl \
    --to=pragma@wxs.nl \
    --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).