Setup SyncTeX with Textadept and Okular

Question

My question is very simple: can I setup Textadept and Okular in order to get forward and backward search?

Textadept jumps to Okular with Ctrl+R and compiles my ConTeXt file with Ctrl+Shift+R. That is nice, but it is not enough to me.

I have this line in my init.lua yet:

textadept.run.compile_commands.tex = 'mtxrun --autogenerate --script context --autopdf --purge --synctex "%f"'

But seems to me, after Internet searching, that is difficult to achieve my goal.

Just below I have quoted an Aditya's advice about this request, but I have no clue how to handle it yet.

You need to know two commands to setup forward and inverse search: (i) Call textadept to open a specific file at a specific line-number and (ii) Call okular to jump to a specific synctex location. The first is needed for inverse search and the second is needed for forward search.

In relation to my code above, it is worth to note that "synctex=1", "synctex=-1", or simply "synctex", are interchangeable in ConTeXt.

Hans Hagen's statement here says that we have relative small SyncTEX files in ConTeXt because it doesn't use SyncTEX's internal code. Instead, it uses its own logic. However, I have tested SyncTEX in the past with TexWorks and had no problem running forward and inverse search.

Textadept's help page omites SincTEX at all.

My first update:

First things first. I work in a Plasma desktop with context-minimals in /opt/context-minimals/setuptex path.

I use ConTeXt because many reasons. Among other things I can make use of my otf fonts within my /home/username/.font folder.

In order to do that, I added this line into my ~/.bashrc file: source /opt/context-minimals/setuptex. If not, ConTeXt compile my pdf with a fallout font like Latin Modern.

Then, in my home there is a texadept.sh file with this lines inside:

#!/bin/bash source /opt/context-minimals/setuptex

/home/edu/Software/textadept_10.0_beta_2.x86_64/textadept

The second line is due to I only could download the portable version.

Well. Therefore, behind my icon for launching Textadept we have the comand "bash /home/username/textadept.sh". That does the trick in order to compile with Textadept using my personal fonts in ~/.fonts, and not with Latin Modern or whatever.

The unsuccessful command I have written in Okular is "/home/username/Software/textadept_10.0_beta_2.x86_64/textadept" "%f" -e textadept.editing.goto_line(%l-1)

Neither when I switch to "bash /home/edu/textadept.sh" "%f" -e textadept.editing.goto_line(%l-1)

For the moment that is my update.

Answer 1

As you identify, Okular should not be the problem. See an example for kile. What is needed is passing to a single instance of the editor at least the line number you wish to go back to. The recent documentation at first glance seems confusing on the first point (-F is NOT needed, see below) Single Instance:

"Textadept is a single-instance application. This means that after starting Textadept, running textadept file.ext on Linux or BSD (ta file.ext on Mac OSX) from the command line or opening a file with Textadept from a file manager (e.g. Windows) opens file.ext in the original Textadept instance. Passing a -f or --force switch to Textadept overrides this behavior and opens the file in a new instance:... Without the force switch, the original Textadept instance opens files, regardless of the number of instances open. The terminal versions of Textadept do not support single instance."

My answer based on further testing is that I can inverse-search a given line in Textadept from SumatraPDF OR Okular

My simple windows command was using latest available build however it should work with any recent version, just make sure your path to textadept is correctly qualified. NOTE for my builds there was a need to add the -1 at the end since SumatraPDF and Okular count from base 1 but the unmodified textadept seems to count base 0, so you need to subtract with -1

Various builds and add-ins may change that up or down so you may get different results between ConTeX and pdfLaTeX (if I find them I will come back to edit) SumatraPDF and Okular use the same following placeholders: •%f - the file name •%l - (lowercase L) the line of the file to be reached

If your textadept is on your environment path you can simply enter

textadept "%f" -e textadept.editing.goto_line(%l-1)

Depending on the environment your running in, the quotes around %f may not be needed. Equally if you use a portable version or textadept is not on your main path you may need a "quoted path" for either of the two common windows program files locations.

"drive:\path to file\textadept.exe" "%f" -e textadept.editing.goto_line(%l-1)

OR on Linux

/home/YourName/Software/textadept_version/textadept "%f" -e textadept.editing.goto_line(%l-1)

The quotes around %f may not be needed if your filenames do not have spaces so try with and without. Your drive or path will differ and it will not work (no error message is shown) unless you get it exact here is a pictorial to help with all else