Control: clone -1 -2 Control: retitle -2 zathura: move away from calling /usr/bin/synctex Control: severity -2 wishlist Control: tags -2 = upstream fixed-upstream Control: reassign -1 texlive-binaries 2014.20140528.34243-1
On 2014-05-30 12:24:25, José Salavert Torres wrote: > Package: zathura > Version: 0.2.7-1 > Followup-For: Bug #749856 > > Dear Maintainer, > > Sorry, a proper look at the console output reveals that it seems a bug in the > SyncTeX command line utility version 1.2 which was recently updated in the > new texlive version. > > Can you redirect this bug to the correct package? Doing so now. I assume that the texlive-binaries version you are talking about is 2014.20140528.34243-1. Is this correct? But anyway, zathura should probably use something different than calling /usr/bin/synctex for its SyncTeX support. I've implemented SyncTex support upstream with synctex_parser now [1]. If nothing breaks with the new code, it will be in the next zathura release. [1] https://git.pwmt.org/?p=zathura.git;a=shortlog;h=refs/heads/feature/better-synctex Context for the texlive-binaries maintainer: zathura calls "synctex edit -o $page:$x:$y:$file $file -x 'gvim --servername synctex --remote +%{line} %{input}'" (as configured by José) to perform SyncTeX backward synchronization. But if the value inserted into %{input} is too long, the patch to the input file is cut off and vim tries to open a file that does not exist. Cheers -- Sebastian Ramacher
signature.asc
Description: Digital signature
