Unknown render command: :selection-style about pdf-tools

[cyrilarnould]

Oh interesting! I did not realise there were cases where people where using lisp code from one repository (melpa) and epdfinfo from another repository (melpa-stable)

I generally prefer melpa over melpa-stable as in some cases, packages take longer than major emacs releases to generate a new stable release and sometimes that includes great new features.

The problem with the binary for me is that the integrated autogen rebuild flow didn't work on Windows. I guess I could have looked deeper into making it work but it was much easier to just get the prebuilt binary from MSYS2.

[barslmn]

I removed the elpa-pdf-tools-server package with apt and installed epdfinfo with pdf-tools-install command from emacs. Which solved the issue for me.

[seokbeomKim]

Thanks @barslmn. Your workaround works well.

[cyrilarnould]

I had the same problem using MSYS2's mingw-w64-emacs-pdf-tools-server release, I think I figured it out. You're using the melpa version of the emacs package, but I guess you're using a (prebuilt?) binary for the epdfinfo executable which is built from tag 1.0.0.

So you have two options I guess:

• Switch to the melpa-stable release of the emacs package (unfortunately, there's no highlighting at all in that version as far as I can tell)
• (re)build the epdfinfo executable yourself from the latest sources. This resolved the issue for me.

For users who rely on prebuilt binaries it would be nice if there were a new release of pdf-tools soon.

[vedang]

Oh interesting! I did not realise there were cases where people where using lisp code from one repository (melpa) and epdfinfo from another repository (melpa-stable)

I have 3 days in the next week cut out for pdf-tools work. At the end of the days, I will make a stable release so that the new changes propagate to melpa-stable as well.

[barslmn]

I am having the same problem on doomemacs.
emacs: 28.2
pdf-tools package: 1.0.0
pdfinfo/poppler: 22.12
epdfinfo (debian apt): 1.0.0-1