From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \synctex=1 ignored in mkiv
Date: Fri, 11 Mar 2011 19:12:31 +0100 [thread overview]
Message-ID: <AANLkTikpmHHqF2TATzsPMQhTSmZ9+oGga2Ln8n9oJFb7@mail.gmail.com> (raw)
In-Reply-To: <4D7A5C63.7010001@wxs.nl>
On Fri, Mar 11, 2011 at 18:31, Hans Hagen wrote:
> On 11-3-2011 3:38, Mojca Miklavec wrote:
>>
>> Dear Hans,
>>
>> subject says it all: when I use \synctex=1 in mkiv, I don't get any
>> ..synctex.gz file. The --synctex switch works however (which is exactly
>> the opposite of what used to be the case a while ago :).
>
> \synctex is a nop in mkiv, use a proper directive instead:
>
> \enabledirectives[system.synctex]
Thank you. What exactly was the reason to disable the old syntax? Why
not maybe defining it to give at least a warning (or even error)
printing out a message saying what to do. It is a bit weird to see the
code compile fine without ever noticing that something went wrong.
Is there any chance that a single command would be provided that would
work both in mkii and mkiv (in mkii it would call \synctex=1 and in
mkiv it would call \enabledirectives[system,synctex])?
Mojca
___________________________________________________________________________________
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:[~2011-03-11 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 14:38 Mojca Miklavec
2011-03-11 16:00 ` Li Yanrui (李延瑞)
2011-03-11 17:31 ` Hans Hagen
2011-03-11 18:12 ` Mojca Miklavec [this message]
2011-03-11 18:27 ` 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=AANLkTikpmHHqF2TATzsPMQhTSmZ9+oGga2Ln8n9oJFb7@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).