others. After some debugging, our conclusion
> was that different versions of the library/application were used, or
> different approaches. We found a way to generate the stuff in the pdf
> to make it work for the failing viewers we had. Hans did then not
> replace this with the old approa
ill depend on the viewers. We noticed a few weeks ago
that synctex (pdf -> editor) was not working in a few viewers (okular)
while it was working in others. After some debugging, our conclusion
was that different versions of the library/application were used, or
different approaches. We found
I guess one person's bug is another person's feature. :-)
> - Mikael S and i spend some time with editor/viewer combinations on linux in
> order to find ways around the different synctex libs that they use
> - as a result we could make most work ok
Are these recent changes? And should
recent change?
it's more a feature
- Mikael S and i spend some time with editor/viewer combinations on
linux in order to find ways around the different synctex libs that they use
- as a result we could make most work ok
- we assume that synctex is set up in the document with
\setupsynctex
verted, part by part, the bad
code. Only a few of them are left (but don't tell Hans!). I also got a
feeling that Wolfgang, checking all the code, since long did see this
through.
Thus, in the latest upload, for example, you might get SyncTeX working
again, but you might need to add \setupsyncte
ps!
Gavin
> On Oct 15, 2022, at 12:00 PM, Alan Bowen via ntg-context
> wrote:
>
> At the top of a single source file, I have the lines:
> % !TEX root = prd_Aestimatio-0301.tex % the root file
> % !TEX TS-program = ConTeXt2021
> % !TEX useAlternatePat
At the top of a single source file, I have the lines:
% !TEX root = prd_Aestimatio-0301.tex % the root file
% !TEX TS-program = ConTeXt2021
% !TEX useAlternatePath
% !TEX useConTeXtSyncParser
\setupsynctex[state=start, method=max]
Syncing works well enough—though I can see no difference
ivial and without a
>> minimum code.
>>
>> In the current state of ConTeXt development, which engine do you
>> recommend to use *definitively*? ConTeXt MkIV or LMTX?
>>
>> I use macOS 10.15.7, on which I have MacTeX-2022, ConTeXt Standalone and
>> ConTeXt LMT
I have MacTeX-2022, ConTeXt Standalone and
> ConTeXt LMTX. My editor is TeXShop 4.72 (the last one), even if Synctex
> doesn't work too well: source to PDF is almost OK, but PDF to source is
> still very inaccurate, not to mention that to activate the direct and
> reverse search you have to write
ource is still very inaccurate, not to mention that to activate the
direct and reverse search you have to write such a thing as
%! TEX TS-program = ConTeXt2021
%! TEX useAlternatePath
%! TEX useConTeXtSyncParser
\setupsynctex [state=start, method=min]
\starttext
...
\stoptext
I also have the l
useAlternatePath
%! TEX useConTeXtSyncParser
\setupsynctex [state=start, method=min]
\starttext
...
\stoptext
I also have the latest TeXworks on board, but I don't understand how to set
it up. If you think that for ConTeXt is better than TeXShop and you want to
teach me how to set it up, thank you
te=>\ctikzset{ inductor=cute}]
>>
>> \processaction
>> [\currentmoduleparameter{diode}]
>> [full=>\ctikzset{ diode=full},
>> empty=>\ctikzset{ diode=empty}]
>>
>> \processaction
>> [\currentmoduleparameter{logic}]
>> [european=>\ctikzset{ l
@circuit@mos@arrowstrue,
> false=>\pgf@circuit@mos@arrowsfalse]
>
> \protect
>
> \ctikzset{tripoles/op amp/font/.initial=\switchtobodyfont[small]}
>
> \aliased\let\stopcircuitikz\relax
>
> \permanent\protected\def\startcircuitikz#1\stopcircuitikz
> {\starttikz
this path is wrong then the editor just does nothing.
4) These two lines at the top of each source file you want to sync to/from:
% !TEX useAlternatePath
% !TEX useConTeXtSyncParser
5) Either --synctex="1" on the command line in the .engine file or
\setupsynctex [state=start, method=max
On 5/16/2021 5:30 PM, Nicola wrote:
It works just fine. Add this line at the top of your document:
% !TEX useOldSyncParser
I also have:
\setupsynctex[state=start,method=min]
I am not sure whether method=min is necessary.
normally not ...
Richard Koch, however, has been incredible, IMO
Hi Hans and Nicola,
Thank you for your attention and your answers.
As a matter of fact I am aware that when using ConTeXt with TeXShop one has to
add on the first line
% !TEX useOldSyncParser
and then setup synctex with
\setupsynctex[state=start,method=min]
(or method=max, or just ignoring
On 2021-05-16, Hans Hagen wrote:
> On 5/16/2021 2:52 PM, Otared Kavian wrote:
>> Hi Hans,
>>
>> I have been noticing for some time that \setupsynctex does not work
>> properly, at least in TeXShop on MacOS. A « filename.synctex » file
>> is created but on most o
On 5/16/2021 2:52 PM, Otared Kavian wrote:
Hi Hans,
I have been noticing for some time that \setupsynctex does not work properly,
at least in TeXShop on MacOS.
A « filename.synctex » file is created but on most occasions it does not
contain many lines, and one cannot go from the PDF file
On 5/16/2021 2:52 PM, Otared Kavian wrote:
Hi Hans,
I have been noticing for some time that \setupsynctex does not work properly,
at least in TeXShop on MacOS.
A « filename.synctex » file is created but on most occasions it does not
contain many lines, and one cannot go from the PDF file
Hi Hans,
I have been noticing for some time that \setupsynctex does not work properly,
at least in TeXShop on MacOS.
A « filename.synctex » file is created but on most occasions it does not
contain many lines, and one cannot go from the PDF file to the right location
in the source file.
Has
Hi Hans,
It seems that
\setupsynctex[state=start]
does not have any effect in LMTX version 2020.09.20 23:02, while it works fine
with mkiv version 2020.06.25 10:55.
Best regards: Otared
___
If your question
ce (no multipass data
> file is produced)
> mtx-context | --runs process at most this many times
> mtx-context | --forcedruns process this many times (permits for
> optimization trial runs)
> mtx-context |
> mtx-context | --batchmode
ever initializes synctex (for
production runs)
mtx-context | --synctex run with synctex enabled (better use
\setupsynctex[state=start]
mtx-context |
mtx-context | --nodates omit runtime dates in pdf file
(optional value: a number (this 1970 offset time) or string &
On 7/22/2020 9:03 AM, Aradenatorix Veckhôm Avecælus wrote:
I think so. In fact, I have this doubt, can you use synctex with
ConTeXt or do you have something that works like it?
You have to enable it:
\setupsynctex[state=start]
because it adds quite some overhead.
Hans
imposition which reshuffles pages in
ways that can interfere
you can try to add
\setupsynctex[state=stop]
at the top of that file
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat
On 12/17/2019 10:04 AM, Otared Kavian wrote:
Hi Hans,
Last week I sent you a PDF showing a strange behaviour of \startitemize and
\quotation in LMTX. I finally could nail down the origin of the problem: it
seems that if the command
\setupsynctex[state=start]
is present twice
On 12/17/2019 10:04 AM, Otared Kavian wrote:
Hi Hans,
Last week I sent you a PDF showing a strange behaviour of \startitemize and
\quotation in LMTX. I finally could nail down the origin of the problem: it
seems that if the command
\setupsynctex[state=start]
is present twice
Hi Hans,
Last week I sent you a PDF showing a strange behaviour of \startitemize and
\quotation in LMTX. I finally could nail down the origin of the problem: it
seems that if the command
\setupsynctex[state=start]
is present twice at the beginning of the document
, in order to use synctex in TeXShop and ConTeXt, you have
to add the following two lines at the top of your source file:
% !TEX useOldSyncParser
\setupsynctex[state=start,method=min] % or method=max
Then you typeset your file and you can get the usual synctex behaviour
(however, for some unknown
--autopdf to the context call
also --synctex is replaced by
\setupsynctex[state=start]
This always uses the default context-version, which path' is saved
the environment-variables of windows. How can I switch (and control)
between different context-versions or pathes for compiling without
call
also --synctex is replaced by
\setupsynctex[state=start]
This always uses the default context-version, which path' is saved the
environment-variables of windows. How can I switch (and control) between
different context-versions or pathes for compiling without changing the
environment variab
t' in shell (terminal) the
> context from TeX Live will be used. Note the above 'export' commands.
> The first prepend the path to ConTeXt Standalone binaries, the next on
> prepends TeX Live binaries, so TeX Live binaries will be used if you run
> 'context' in terminal/shell.
>
the path to ConTeXt Standalone binaries, the next on
prepends TeX Live binaries, so TeX Live binaries will be used if you run
'context' in terminal/shell.
> I then tested the vladimir.tex file
>
> \setupsynctex[state=start]
>
> \startusableMPgraphic{NumberHead}
> draw outlinet
nux/context
[aragorn@fab ~]$
I then tested the vladimir.tex file
\setupsynctex[state=start]
\startusableMPgraphic{NumberHead}
draw outlinetext.f
("\bf\namedheadnumber{chapter}")
(withcolor "blue")
ysized 50pt ;
\stopusableMPgraphic
\unexpanded\def\processMPheadnum
text/metapost/context/base/mpiv/metafun.mpiv'
>> > using method 'default'
>> > metapost> initializing number mode 'scaled'
>> >
>> > lua error > lua error on line 10 in file
>> /home/aragorn/vladimir.tex:
>> >
>> >
ext/tex/context/base/mkiv/node-nut.lua:190: attempt
> to
> > call a nil value (global 'getid')
> > stack traceback:
> > ...ext/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:190: in
> > upvalue 'getexpansion'
> > ...ext/tex/texmf-context/tex/conte
ue 'getexpansion'
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-mps.lua:343: in
> function <...ext/tex/texmf-context/tex/context/base/mkiv/font-mps.lua:338>
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-mps.lua:437: in
> local 'boxtomp'
> ...
ext/tex/context/base/mkiv/font-mps.lua:437: in
local 'boxtomp'
...ext/tex/texmf-context/tex/context/base/mkiv/mlib-pps.lua:1894: in
function <...ext/tex/texmf-context/tex/context/base/mkiv/mlib-pps.lua:1891>
(...tail calls...)
1
2 \setupsynctex[state=start]
3
4 \start
8-08-23 10:48:42 +0200]:
>
> > Hi,
> > Thanks for your help but ...
>
> I checked again and it is fine. May be I was too unspecific. First, I
> changed a bit your example to this one:
>
> [test.tex]
> 8< ---
8< ----
\setupsynctex[state=start]
\startusableMPgraphic{NumberHead}
draw outlinetext.f
("\bf\namedheadnumber{chapter}")
(withcolor "lightgray")
ysized 50pt ;
\stopusableMPgraphic
\unexpanded\def\processMPheadnumber#1%
{\useMPgraphic{NumberHead}}
\setuphead%
[chapter]%
[co
internal code but uses its own logic
- there is no gain in zipping
- we have relative small synctex files because we use a different logic
the way to enable synctex is in the document (see workflows.pdf):
\setupsynctex[state=start]
it's a bit pitty that pdf viewers have hard coded syntex file
f-osx-64/bin)
> mtxrun --script context --autogenerate --file-line-error "$1”
>
> and
> \setupsynctex[state=start, method=max]
> in the source file, the requisite filename.synctex auxiliary file is produced
> on processing.
>
> But I am still not getting any linkag
--file-line-error "$1”
and
\setupsynctex[state=start, method=max]
in the source file, the requisite *filename*.synctex auxiliary file is
produced on processing.
But I am still not getting any linkage between the source file and the
preview file, that is, clicking on one does not have any e
file, even it were part of an \input file. For instance after typesetting the
file:
%%% begin synctex-example.tex
\setupsynctex[state=start,method=max]
\starttext
\input knuth.tex
\hairline
\input ward.tex
\stoptext
%%% end synctex-example.tex
I could click on the sentence « The separation of any
. For instance after typesetting the
file:
%%% begin synctex-example.tex
\setupsynctex[state=start,method=max]
\starttext
\input knuth.tex
\hairline
\input ward.tex
\stoptext
%%% end synctex-example.tex
I could click on the sentence « The separation of any of these » in the PDF
file and the file
4. Jun 2017, at 18:55, Hans Hagen <pra...@wxs.nl
>>>> <mailto:pra...@wxs.nl>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> For those using synctex, an alternative method is:
>>>>
>>>> \setupsynctex[state=start]
>>&g
> On 11. Jul 2017, at 17:09, Hans Hagen <pra...@wxs.nl> wrote:
>
> On 7/11/2017 4:36 PM, Thomas Floeren wrote:
>>> On 4. Jun 2017, at 18:55, Hans Hagen <pra...@wxs.nl> wrote:
>>>
>>> Hi,
>>>
>>> For those using syn
On 7/11/2017 4:36 PM, Thomas Floeren wrote:
On 4. Jun 2017, at 18:55, Hans Hagen <pra...@wxs.nl> wrote:
Hi,
For those using synctex, an alternative method is:
\setupsynctex[state=start]
It is tuned for use in a more complex setup where one wants access to source
files (with c
> On 4. Jun 2017, at 18:55, Hans Hagen <pra...@wxs.nl> wrote:
>
> Hi,
>
> For those using synctex, an alternative method is:
>
> \setupsynctex[state=start]
>
> It is tuned for use in a more complex setup where one wants access to source
> files (with cont
Hi,
For those using synctex, an alternative method is:
\setupsynctex[state=start]
It is tuned for use in a more complex setup where one wants access to
source files (with content) and not to e.g. styles in a tex tree. It
also works reasonable well with (also included) xml files. Personally I
50 matches
Mail list logo
