FAP

Updated the code in my earlier comment, @Aneeqasif please have a look. :)

I fixed this in my own config through ```elisp (defun ace-isearch/jump-back-to-point () (setq ace-isearch--opoint (point)) (add-hook 'isearch-mode-hook 'ace-isearch/jump-back-to-point) (add-hook 'isearch-mode-end-hook (lambda () (unless isearch-mode-end-hook-quit (goto-char ace-isearch--opoint))) ``` What confuses me...

This currently fails with the following exceptiion (see below). But I'm pretty sure that I've tested this before, as I had the same suspicion, and it didn't have the expected...

Thank you for your quick reply. Somehow this totally breaks the setup and I can't really tell why this is happening.. Our setup involves a gradle plugin that provides preconfigured...

@ysb33r Thank you, just found time to test the 2.3.0 release. Sadly this doesn't fix our issue. The `ERROR: The following messages from AsciidoctorJ are treated as errors:` still gets...

No, the problem is that the `AsciidoctorRemoteExecutionException` I get with the java exec doesn't contain the specific error message anymore and it's nowhere on the stack. The exception you're catching...

Yes, something like that. We'd definitely need a way to tell why exactly the external process failed. > Also on option B above, we'll have an issue if the exception...

@jeremy-compostella Ready for review.

I'm having the same issue. With verified subset: ``` $ flatpak remote-modify --subset=verified flathub $ flatpak install flathub com.github.wwmm.easyeffects Looking for matches… com.github.wwmm.easyeffects permissions: ipc fallback-x11 wayland x11 dri file...

@wwmm Yes, I'm on Ubuntu. > One possible explanation would be the Flatpak package for Calf and LSP installing the libraries in a place where lilv does not search for...