zathura issueshttps://git.pwmt.org/pwmt/zathura/-/issues2024-03-25T13:27:08+01:00https://git.pwmt.org/pwmt/zathura/-/issues/408Regression in 0.5.5: All open windows jump to the same location when PDF file...2024-03-25T13:27:08+01:00gi1242 gi1242Regression in 0.5.5: All open windows jump to the same location when PDF file is updated.First thanks so much for Zathura; I use it all the time.
The recent upgrade unfortunately introduced a regression that seriously affects my workflow: If you have multiple windows of Zathura open viewing the same document, then when the ...First thanks so much for Zathura; I use it all the time.
The recent upgrade unfortunately introduced a regression that seriously affects my workflow: If you have multiple windows of Zathura open viewing the same document, then when the document is updated *all* windows will jump to the same location.
That is, if you have two windows open showing `foo.pdf`, with one on page 3, one on page 5, and then update `foo.pdf`. Both windows will jump to the same page (either page 3 or page 5).
This is very inconvenient for me when editing LaTeX files; I often have multiple copies of the out PDF document open each showing a different portion of the document (e.g. one showing the location I'm editing, and one showing the location I'm referencing). When I make a small change to the LaTeX source and recompile the document, both documents show the exact same location.
I'm currently working around the issue by opening a second copy of the document in Okular / other PDF viewer. But it would be much nicer if I don't have to use a second viewer.
Thanks in advance,
GIhttps://git.pwmt.org/pwmt/zathura/-/issues/410$HOME/.local/share/zathura/history file doesn't get created anymore in the ne...2024-03-19T17:04:14+01:00Ghost User$HOME/.local/share/zathura/history file doesn't get created anymore in the new version 0.5.5That history file file was useful for creating dmenu/rofi scripts.
is it's removal intentional?
if yes then why?That history file file was useful for creating dmenu/rofi scripts.
is it's removal intentional?
if yes then why?https://git.pwmt.org/pwmt/zathura/-/issues/409Wrong alpha for highlight-fg2024-03-09T23:18:40+01:00Jannis WeisbrodtWrong alpha for highlight-fg```
set highlight-color rgba(0,0,0,0.2)
set highlight-fg rgb(255,255,255)
```
Try following a link. The opacity of the link number is not 1 as expected, but rather 0.2.```
set highlight-color rgba(0,0,0,0.2)
set highlight-fg rgb(255,255,255)
```
Try following a link. The opacity of the link number is not 1 as expected, but rather 0.2.https://git.pwmt.org/pwmt/zathura/-/issues/407Zathura 0.5.4 does not build against the latest Girara 0.4.32024-03-04T10:30:33+01:00Robin CandauZathura 0.5.4 does not build against the latest Girara 0.4.3Hi,
Zathura 0.5.4 does not build against the latest Girara 0.4.3 (but builds fine against Girara 0.4.2).
Here are the build logs: https://bpa.st/FRGA
I'm assuming a new Zathura release compatible with Girara 0.4.3 hasn't been tagged ...Hi,
Zathura 0.5.4 does not build against the latest Girara 0.4.3 (but builds fine against Girara 0.4.2).
Here are the build logs: https://bpa.st/FRGA
I'm assuming a new Zathura release compatible with Girara 0.4.3 hasn't been tagged yet. Is this planned already?
Thanks a lot for your wonderful work! :slight_smile:https://git.pwmt.org/pwmt/zathura/-/issues/389Braces in filenames prevent history entry creation when using `plain` backend2024-03-03T18:18:09+01:00Denis KasakBraces in filenames prevent history entry creation when using `plain` backendFiles with braces in their name fail to get added to history, possibly only with the `plain` backend, because braces are special characters in this format and do not get escaped when adding the entry.
The following error is printed when...Files with braces in their name fail to get added to history, possibly only with the `plain` backend, because braces are special characters in this format and do not get escaped when adding the entry.
The following error is printed when zathura is closed, after opening a file with braces in the name:
(org.pwmt.zathura:246459): GLib-CRITICAL **: 14:30:08.632: g_key_file_set_value: assertion 'group_name != NULL && g_key_file_is_group_name (group_name)' failedhttps://git.pwmt.org/pwmt/zathura/-/issues/397Segfault while calling exec2024-03-03T18:18:09+01:00LGSegfault while calling execHey,
Zathura v0.5.4 (built with [these build/packaging instructions](https://gitlab.archlinux.org/archlinux/packaging/packages/zathura/-/blob/main/PKGBUILD?ref_type=heads) on an Arch Linux system) running with the mupdf plugin crashes w...Hey,
Zathura v0.5.4 (built with [these build/packaging instructions](https://gitlab.archlinux.org/archlinux/packaging/packages/zathura/-/blob/main/PKGBUILD?ref_type=heads) on an Arch Linux system) running with the mupdf plugin crashes whenever I try to execute any external program with the `:exec` function with a segfault.
```
❯ zathura --version
zathura 0.5.4
girara 0.4.1 (runtime: 0.4.1)
(plugin) pdf-mupdf (0.4.1) (/usr/lib/zathura/libpdf-mupdf.so)
```
The backtrace with gdb is as follows:
```
Thread 1 "zathura" received signal SIGSEGV, Segmentation fault.
0x0000555555579166 in ?? ()
(gdb) bt
#0 0x0000555555579166 in ()
#1 0x00007ffff7e8b324 in girara_command_run () at /usr/lib/libgirara-gtk3.so.3
#2 0x00007ffff7e8b58e in girara_callback_inputbar_activate () at /usr/lib/libgirara-gtk3.so.3
#3 0x00007ffff71a66c0 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#4 0x00007ffff71d4a36 in () at /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff71c2a45 in g_signal_emitv () at /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff76b555e in () at /usr/lib/libgtk-3.so.0
#7 0x00007ffff76b6398 in () at /usr/lib/libgtk-3.so.0
#8 0x00007ffff76bb801 in () at /usr/lib/libgtk-3.so.0
#9 0x00007ffff76bbad0 in gtk_bindings_activate_event () at /usr/lib/libgtk-3.so.0
#10 0x00007ffff7757dfd in () at /usr/lib/libgtk-3.so.0
#11 0x00007ffff768c6cd in () at /usr/lib/libgtk-3.so.0
#12 0x00007ffff71a6626 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#13 0x00007ffff71d50ea in () at /usr/lib/libgobject-2.0.so.0
#14 0x00007ffff71c5335 in () at /usr/lib/libgobject-2.0.so.0
#15 0x00007ffff71c5c77 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#16 0x00007ffff71c5d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#17 0x00007ffff7954cf5 in () at /usr/lib/libgtk-3.so.0
#18 0x00007ffff7963fec in gtk_window_propagate_key_event () at /usr/lib/libgtk-3.so.0
#19 0x00007ffff79666d4 in () at /usr/lib/libgtk-3.so.0
#20 0x00007ffff7687829 in () at /usr/lib/libgtk-3.so.0
#21 0x00007ffff71c4d41 in () at /usr/lib/libgobject-2.0.so.0
#22 0x00007ffff71c5c77 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#23 0x00007ffff71c5d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#24 0x00007ffff7954cf5 in () at /usr/lib/libgtk-3.so.0
#25 0x00007ffff77eed4a in () at /usr/lib/libgtk-3.so.0
#26 0x00007ffff77ef7b7 in gtk_main_do_event () at /usr/lib/libgtk-3.so.0
#27 0x00007ffff7539b77 in () at /usr/lib/libgdk-3.so.0
#28 0x00007ffff75923e8 in () at /usr/lib/libgdk-3.so.0
#29 0x00007ffff709ff69 in () at /usr/lib/libglib-2.0.so.0
#30 0x00007ffff70fe367 in () at /usr/lib/libglib-2.0.so.0
#31 0x00007ffff709e162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#32 0x00007ffff77ed3c7 in gtk_main_iteration_do () at /usr/lib/libgtk-3.so.0
#33 0x00007ffff7e831d9 in () at /usr/lib/libgirara-gtk3.so.3
#34 0x00007ffff7e80adb in girara_callback_view_key_press_event () at /usr/lib/libgirara-gtk3.so.3
#35 0x00007ffff768c6cd in () at /usr/lib/libgtk-3.so.0
#36 0x00007ffff71a66c0 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#37 0x00007ffff71d4a36 in () at /usr/lib/libgobject-2.0.so.0
#38 0x00007ffff71c5335 in () at /usr/lib/libgobject-2.0.so.0
#39 0x00007ffff71c5c77 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#40 0x00007ffff71c5d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#41 0x00007ffff7954cf5 in () at /usr/lib/libgtk-3.so.0
#42 0x00007ffff7963fec in gtk_window_propagate_key_event () at /usr/lib/libgtk-3.so.0
#43 0x00007ffff79666d4 in () at /usr/lib/libgtk-3.so.0
#44 0x00007ffff7687829 in () at /usr/lib/libgtk-3.so.0
#45 0x00007ffff71c5b73 in () at /usr/lib/libgobject-2.0.so.0
#46 0x00007ffff71c5c77 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#47 0x00007ffff71c5d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#48 0x00007ffff7954cf5 in () at /usr/lib/libgtk-3.so.0
#49 0x00007ffff77eed4a in () at /usr/lib/libgtk-3.so.0
#50 0x00007ffff77ef7b7 in gtk_main_do_event () at /usr/lib/libgtk-3.so.0
#51 0x00007ffff7539b77 in () at /usr/lib/libgdk-3.so.0
#52 0x00007ffff75923e8 in () at /usr/lib/libgdk-3.so.0
#53 0x00007ffff709ff69 in () at /usr/lib/libglib-2.0.so.0
#54 0x00007ffff70fe367 in () at /usr/lib/libglib-2.0.so.0
#55 0x00007ffff70a0b97 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
#56 0x00007ffff77ed2df in gtk_main () at /usr/lib/libgtk-3.so.0
#57 0x0000555555560efd in main ()
```
I also tried installing the [zathura-git](https://aur.archlinux.org/packages/zathura-git) as well as the [girara-git](https://aur.archlinux.org/packages/girara-git) and [zathura-pdf-mupdf-git](https://aur.archlinux.org/packages/zathura-pdf-mupdf-git) AUR packages and got the same result albeit with a different backtrace:
```
Thread 1 "zathura" received signal SIGSEGV, Segmentation fault.
0x0000555555579166 in ?? ()
(gdb) bt
#0 0x0000555555579166 in ()
#1 0x00007ffff7e8b294 in girara_command_run () at /usr/lib/libgirara-gtk3.so.4
#2 0x00007ffff7e8b4fe in girara_callback_inputbar_activate () at /usr/lib/libgirara-gtk3.so.4
#3 0x00007ffff71a66c0 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#4 0x00007ffff71d4a36 in () at /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff71c2a45 in g_signal_emitv () at /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff76b555e in () at /usr/lib/libgtk-3.so.0
#7 0x00007ffff76b6398 in () at /usr/lib/libgtk-3.so.0
#8 0x00007ffff76bb801 in () at /usr/lib/libgtk-3.so.0
#9 0x00007ffff76bbad0 in gtk_bindings_activate_event () at /usr/lib/libgtk-3.so.0
#10 0x00007ffff7757dfd in () at /usr/lib/libgtk-3.so.0
#11 0x00007ffff768c6cd in () at /usr/lib/libgtk-3.so.0
#12 0x00007ffff71a6626 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#13 0x00007ffff71d50ea in () at /usr/lib/libgobject-2.0.so.0
#14 0x00007ffff71c5335 in () at /usr/lib/libgobject-2.0.so.0
#15 0x00007ffff71c5c77 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#16 0x00007ffff71c5d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#17 0x00007ffff7954cf5 in () at /usr/lib/libgtk-3.so.0
#18 0x00007ffff7963fec in gtk_window_propagate_key_event () at /usr/lib/libgtk-3.so.0
#19 0x00007ffff79666d4 in () at /usr/lib/libgtk-3.so.0
#20 0x00007ffff7687829 in () at /usr/lib/libgtk-3.so.0
#21 0x00007ffff71c5b73 in () at /usr/lib/libgobject-2.0.so.0
#22 0x00007ffff71c5c77 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#23 0x00007ffff71c5d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#24 0x00007ffff7954cf5 in () at /usr/lib/libgtk-3.so.0
#25 0x00007ffff77eed4a in () at /usr/lib/libgtk-3.so.0
#26 0x00007ffff77ef7b7 in gtk_main_do_event () at /usr/lib/libgtk-3.so.0
#27 0x00007ffff7539b77 in () at /usr/lib/libgdk-3.so.0
#28 0x00007ffff75923e8 in () at /usr/lib/libgdk-3.so.0
#29 0x00007ffff709ff69 in () at /usr/lib/libglib-2.0.so.0
#30 0x00007ffff70fe367 in () at /usr/lib/libglib-2.0.so.0
#31 0x00007ffff70a0b97 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#32 0x00007ffff77ed2df in gtk_main () at /usr/lib/libgtk-3.so.0
#33 0x0000555555560efd in main ()
```
I am running on an arch system with x11 and i3 as window manager, but if any further system information is required I will happily provide it.https://git.pwmt.org/pwmt/zathura/-/issues/400URL opening should be configurable instead of being hardcoded to xdg-open2024-03-03T15:10:18+01:00Vincent LefèvreURL opening should be configurable instead of being hardcoded to xdg-openURL opening is currently done via `link_launch` in `zathura/links.c`, which calls `girara_xdg_open_with_working_directory`. So this is hardcoded to `xdg-open`. This is a poor choice, because `xdg-open` and the associated `xdg-settings` c...URL opening is currently done via `link_launch` in `zathura/links.c`, which calls `girara_xdg_open_with_working_directory`. So this is hardcoded to `xdg-open`. This is a poor choice, because `xdg-open` and the associated `xdg-settings` command (to select the default browser) are known to have many issues, yielding a wrong browser to be launched (see the various [Debian bugs](https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=xdg-utils); and this may be the cause of #367, which was closed as assumed to be an issue with `xdg-open`).
So the command to open URLs should be configurable, either directly in zathura or via girara.https://git.pwmt.org/pwmt/zathura/-/issues/381background transparency alpha2024-03-03T13:07:52+01:00ask lowbackground transparency alphaGive an option to enjoy background transparency under the compositor level.
Example: picom, compton, xcompmgr, etc on X11.
sway, river, hyperland, etc through wayland.
Apply it only on document background. Not for text, images and...Give an option to enjoy background transparency under the compositor level.
Example: picom, compton, xcompmgr, etc on X11.
sway, river, hyperland, etc through wayland.
Apply it only on document background. Not for text, images and other graphical components.https://git.pwmt.org/pwmt/zathura/-/issues/393A language server for zathurarc2024-03-03T13:06:50+01:00Freed WuA language server for zathurarcHey, I write [a language server](https://github.com/Freed-Wu/zathura-language-server) to complete zathurarc's keyword and option.
A demo video is here <https://asciinema.org/a/628469>
![628469](https://github.com/Freed-Wu/zathura-langu...Hey, I write [a language server](https://github.com/Freed-Wu/zathura-language-server) to complete zathurarc's keyword and option.
A demo video is here <https://asciinema.org/a/628469>
![628469](https://github.com/Freed-Wu/zathura-language-server/assets/32936898/d564df57-5c21-46f4-9fea-8fa04dc9db7c)
And I also have some [vim plugin](https://github.com/Freed-Wu/zathurarc.vim) about zathurarc and [tree-sitter plugin](https://github.com/Freed-Wu/tree-sitter-zathurarc).
I believe it can help more people to edit zathurarc easier and save their time to `man zathurarc` :smile:
Can I host them in same organization with zathura to make more people know and try them? It can also get more bug reports to improve them and increase [bus factor](https://en.wikipedia.org/wiki/Bus_factor).
I send email to <mail@pwmt.org> but got no response. Sorry for disturbance.https://git.pwmt.org/pwmt/zathura/-/issues/243[Feature request] Touch zoom2024-02-16T22:44:31+01:00Scott Lawrence[Feature request] Touch zoomWhen using zathura on a touchscreen, I would expect a pinch movement (two fingers expanding or contracting) to cause the document to zoom. Instead, it selects a region (determined entirely by one of the two fingers).
I think zoom is bet...When using zathura on a touchscreen, I would expect a pinch movement (two fingers expanding or contracting) to cause the document to zoom. Instead, it selects a region (determined entirely by one of the two fingers).
I think zoom is better for a few reasons.
* I, personally, want to zoom much more than I want to select. (This is the real reason, obviously.)
* Firefox zooms with a pinch movement! That means it must be right.
* When a 2-in-1 laptop/tablet is folded, the keyboard is inaccessible. This makes selecting something mostly useless, because I'm in viewing mode, not writing mode. However, zooming is very useful --- and without keyboard interaction, there's currently no way to zoom (without unfolding the laptop to access the keyboard).https://git.pwmt.org/pwmt/zathura/-/issues/401[BUG] PDF get's pushed to right when switching windows when "Copied selected ...2024-01-24T05:37:32+01:00Imlijangba Imchen[BUG] PDF get's pushed to right when switching windows when "Copied selected text..." message is openAfter copying text in a PDF, switching windows without closing the "Copied selected text.." message pushes the PDF to the far right and can no longer be moved left or right. This happens with both the poppler and mupdf backends.
![issue...After copying text in a PDF, switching windows without closing the "Copied selected text.." message pushes the PDF to the far right and can no longer be moved left or right. This happens with both the poppler and mupdf backends.
![issue](/uploads/bbf7180fb4c2e685e016831d16f00c7d/issue.mp4)
**Steps to Reproduce:**
1. Open a PDF in Zathura.
2. Select and copy some text.
3. Without closing the “Copied selected text…” message, switch to another window.
**Expected Behavior**: The PDF should remain in its original position, and I should be able to move it left or right.
**Actual Behavior**: The PDF shifts to the far right of the screen and cannot be moved left or right.
**System Information:**
- Zathura 0.5.4
- Sway window manager 1.8.1
- Fedora 39https://git.pwmt.org/pwmt/zathura/-/issues/367links open in firefox despite default browser is chromium2024-01-22T12:49:57+01:00ask lowlinks open in firefox despite default browser is chromium```
$[~]$ xdg-settings get default-web-browser
chromium.desktop
```
Despite the above defaults, zathura still opens links in the firefox that I've already had installed for other reasons. How to open links in the default browser ?```
$[~]$ xdg-settings get default-web-browser
chromium.desktop
```
Despite the above defaults, zathura still opens links in the firefox that I've already had installed for other reasons. How to open links in the default browser ?https://git.pwmt.org/pwmt/zathura/-/issues/396selecting text displays the selected text in the status bar, which can insane...2024-01-13T19:20:13+01:00Vincent Lefèvreselecting text displays the selected text in the status bar, which can insanely increase the window widthWhen I select text in a PDF document, the whole selected text is displayed in the status bar, and the zathura window width is increased to make this text completely visible in the status bar. If much text is selected (several lines / par...When I select text in a PDF document, the whole selected text is displayed in the status bar, and the zathura window width is increased to make this text completely visible in the status bar. If much text is selected (several lines / paragraphs), this can give insane window widths (several times larger than the screen width), such as 30521 pixels, making the X server quite unresponsive.
I also reported this issue as [Debian bug 1060314](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060314).https://git.pwmt.org/pwmt/zathura/-/issues/395The autocomplete for `open` excludes nothing but pdf's2023-12-27T19:25:49+01:00Jasper ShoveltonThe autocomplete for `open` excludes nothing but pdf's- OS: Arch Linux
- Shell: zsh
- Zathura version: commit `fbbfbbd`
Tested on a clean build.
When tab is pressed after `open`, all directories and files are listed. However, if the contents of a file starts with `%PDF-`, it will be exclu...- OS: Arch Linux
- Shell: zsh
- Zathura version: commit `fbbfbbd`
Tested on a clean build.
When tab is pressed after `open`, all directories and files are listed. However, if the contents of a file starts with `%PDF-`, it will be excluded.
To reproduce:
1. `cd`
1. `echo "%PDF-" > foo`
2. `zathura`
3. `:open ` and press tab
4. `foo` will be excluded
If the first 5 characters of the contents of `foo` are changed in any way, the autocomplete will list it again.https://git.pwmt.org/pwmt/zathura/-/issues/394Selecting text resizes the window2023-12-23T21:56:14+01:00peachey2k2Selecting text resizes the windowWhenever I select a piece of text, it forcefully resizes the window vertically to fit that text in the bottom line where it says `Copied selected text to selection clipboard: {text}`. When it happens, the window can't be shrunken to a sm...Whenever I select a piece of text, it forcefully resizes the window vertically to fit that text in the bottom line where it says `Copied selected text to selection clipboard: {text}`. When it happens, the window can't be shrunken to a smaller size until I hit the escape key, which hides that bottom line. This happens even when the window is maximized and in fullscreen.
zathura --version output:
```
>> zathura --version
Gtk-Message: 15:09:09.790: Failed to load module "colorreload-gtk-module"
Gtk-Message: 15:09:09.791: Failed to load module "window-decorations-gtk-module"
zathura 0.5.4
girara 0.4.1 (runtime: 0.4.1)
(plugin) pdf-poppler (0.3.2) (/usr/lib/zathura/libpdf-poppler.so)
```
DE: Xfce 4.18
Video recording demonstrating the issue:
![](/uploads/4c2bd07da6ce9fddf352c97f7ac2ff7f/untitled.mp4)https://git.pwmt.org/pwmt/zathura/-/issues/390"warning: Failed to parse color string" with zathura 0.5.32023-12-10T13:47:47+01:00Robin Candau"warning: Failed to parse color string" with zathura 0.5.3Hello,
Zathura v0.5.3 (built with [these build/packaging instructions](https://gitlab.archlinux.org/archlinux/packaging/packages/zathura/-/blob/main/PKGBUILD?ref_type=heads) on an Arch Linux system) produces the following warning messag...Hello,
Zathura v0.5.3 (built with [these build/packaging instructions](https://gitlab.archlinux.org/archlinux/packaging/packages/zathura/-/blob/main/PKGBUILD?ref_type=heads) on an Arch Linux system) produces the following warning message at each usage:
```
warning: Failed to parse color string 'rgba(100%,%84,0%,0.9)'.
(org.pwmt.zathura:7247): Gtk-CRITICAL **: 18:19:17.954: gtk_event_controller_set_propagation_phase: assertion 'GTK_IS_EVENT_CONTROLLER (controller)' failed
```
Zathura v0.5.2 does not produce such warning.
Here is the output of `zathura --version` (thus including the warning):
```
$ zathura --version
warning: Failed to parse color string 'rgba(100%,%84,0%,0.9)'.
(org.pwmt.zathura:7247): Gtk-CRITICAL **: 18:19:17.954: gtk_event_controller_set_propagation_phase: assertion 'GTK_IS_EVENT_CONTROLLER (controller)' failed
zathura 0.5.3
girara 0.4.1 (runtime: 0.4.1)
(plugin) pdf-poppler (0.3.2) (/usr/lib/zathura/libpdf-poppler.so)
```
Build logs for the produced zathura v0.5.3 package are available [here](https://pkgbuild.com/~antiz/zathura-0.5.3-1-x86_64-build.log).
The resulted built packages for zathura v0.5.3 and girara v0.4.1 are also available [here](https://pkgbuild.com/~antiz/) and can be installed locally on an Arch based system for testing purposes if needed.
I remain available if you any additional information are required! :)https://git.pwmt.org/pwmt/zathura/-/issues/387zathura hangs after invoking `print`2023-12-08T18:42:55+01:00Jan Paluszathura hangs after invoking `print`Noticed today that `:print` started to hang `zathura` entirely. No print dialog is shown, no CPU is used, `zathura` can only be killed. After some debugging it turns out to be a problem with default sandbox that explicitly disallows `vms...Noticed today that `:print` started to hang `zathura` entirely. No print dialog is shown, no CPU is used, `zathura` can only be killed. After some debugging it turns out to be a problem with default sandbox that explicitly disallows `vmsplice`.
In my particular setup I'm connecting to network `CUPS` printer over secure connection using `GnuTLS` configured to make use of `AF_ALG` kernel crypto API through `libkcapi` which in turn makes use of `vmsplice`:
https://github.com/smuellerDD/libkcapi/blob/0e3e2032a97c51697a5134ca6eabbd5708e9498a/lib/kcapi-kernel-if.c#L324https://git.pwmt.org/pwmt/zathura/-/issues/375Add $DBUS variable for exec2023-12-08T18:42:54+01:00blankieblankie@nixnetmail.comAdd $DBUS variable for execI'm writing a shell script that is invoked with the `exec` command in zathura which opens a PDF or EPub (by asking the user with a GUI file selection dialog). It seems like zathura can be remotely controlled with D-Bus, but there doesn't...I'm writing a shell script that is invoked with the `exec` command in zathura which opens a PDF or EPub (by asking the user with a GUI file selection dialog). It seems like zathura can be remotely controlled with D-Bus, but there doesn't appear to be a way to pass in the dbus name to the shell script (nor could I make one from the predictable format, as `$PPID` is 1).https://git.pwmt.org/pwmt/zathura/-/issues/355[FR] Expose index of the current document through dbus_interface.c2023-12-08T18:42:53+01:00Rodrigo Morales[FR] Expose index of the current document through dbus_interface.cExpose table of contents through dbus
By calling the functions defined in [dbus-interface.c](https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/dbus-interface.c), I have been able to write Elisp functions (please see below) in ord...Expose table of contents through dbus
By calling the functions defined in [dbus-interface.c](https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/dbus-interface.c), I have been able to write Elisp functions (please see below) in order to be able to reuse Zathura instances when opening Org Mode links of the form `[[file:<<filename>>#<<page number>>` (i.e. the same Zathura instance will be used if it is already opening the desired document.)
```elisp
(defun my/dbus-zathura-use-instance-or-open-new (file link)
"Launch zathura to open FILE or Reuse a running instance.
LINK is provided by Org Mode when this function has been
specified in `org-file-apps'. This function is intended to be
used in `org-file-apps' and shouldn't be called on its own."
(let* ((process-alist (proced-process-attributes))
(pids (mapcar 'car (proced-filter process-alist '((comm . "zathura")))))
(pid
(catch 'found
(cl-loop for pid in pids
when (equal
(dbus-get-property
:session
(concat "org.pwmt.zathura.PID-" (number-to-string pid))
"/org/pwmt/zathura"
"org.pwmt.zathura"
"filename")
file)
do (throw 'found pid))))
(page-number
(or
(progn
;; FIXME: According to the docstring of org-file-apps, we
;; can access capture groups using (match-string n
;; link). However, when I tried it, the capture groups
;; didn't have the entire content. For this reason, I'm
;; running string-match with the same regex that I used
;; in org-file-apps, but (match-string n link) should
;; work as specified in the Org Mode documentation.
(string-match "\\.\\(pdf\\|djvu\\)::\\([0-9]+\\)\\'" link)
(match-string 2 link))
"1")))
(if pid
;; Jump to that page in the existing instance
(dbus-call-method
:session
(concat "org.pwmt.zathura.PID-" (number-to-string pid))
"/org/pwmt/zathura"
"org.pwmt.zathura"
"GotoPage"
(1- (string-to-number page-number)))
;; Open a new instance
(make-process
:name "zathura"
:buffer nil
:command `("zathura" "--page" ,page-number ,file)))))
```
```elisp
(setq org-file-apps
'((auto-mode . emacs)
(directory . emacs)
("\\.png\\'" . "mpv %s")
("\\.\\(pdf\\|djvu\\)" . my/dbus-zathura-use-instance-or-open-new)
("\\.\\(pdf\\|djvu\\)::\\([0-9]+\\)\\'" . my/dbus-zathura-use-instance-or-open-new)))
```
Now, I would like to create a function for Emacs which prompts for an item in the table of contents of the document and jumps to that specific page. Currently, [dbus-interface.c](https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/dbus-interface.c) expose the page number and the filename and it provides an interface for jumping to an specific page (interface which I used in my Elisp function shown above). However, the table of contents from the current document is not exposed. Therefore, I propose that the index of the document is exposed in some way.
This feature will not only benefit Emacs users but also users of any completion framework (e.g. rofi, dmenu, fzf, vim, etc), since such specialized completion frameworks have more features available (e.g. regex search, movement with operators, fuzzy finding) which, I believe, might require significant effort to incorporate in the zathura index viewer.https://git.pwmt.org/pwmt/zathura/-/issues/365[Feature Request] Sending a USR2 signal would cause :source2023-12-08T18:42:52+01:00Nima Askarian[Feature Request] Sending a USR2 signal would cause :sourceSending a USR2 or USR1 signal to zathura (`pkill -USR2 zathura`/`pkill -USR1 zathura`) would cause program to do `:source` command. I use pywal for color generation, and I open a lot of pdfs at a same time. It would be nice if I didn't n...Sending a USR2 or USR1 signal to zathura (`pkill -USR2 zathura`/`pkill -USR1 zathura`) would cause program to do `:source` command. I use pywal for color generation, and I open a lot of pdfs at a same time. It would be nice if I didn't need to hit my `:source` keymap every time, but instead send a USR2/USR1 signal inside my bash script.