As you know, latex documents often have quite a substantial amount of page margin. I don't like that. The printing dialog offers the option to print the document scaled up (let's say 120%), but then the whole document is moved towards the bottom-right corner. How to center such enlarged pdf? I'd prefer a solution that does not involve preprocessing of the pdf in any way, because it is just one more step (and I am already doing it with pdfjam - looking for a better way).

I tried to open a PDF using the Evince command, but I received the following message:

GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Can someone help me understand more about this warning message?

Ever since I updated debian, evince has been slow to startup - it takes about half a minute. Once it is open, it works fine, its just slow to open. It never used to take that long - it just used to take a couple of seconds. How can I get it going fast again? $ uname -a Linux mypc 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux I noticed that evince is hanging at the following line for about half a minute: $ strace evince ... eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 11 write(11, "\1\0\0\0\0\0\0\0", 8) = 8 write(10, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x562f5b8ffac0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x562f5b909b30, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x562f5b8bd158, FUTEX_WAKE_PRIVATE, 1) = 1 poll([{fd=11, events=POLLIN}], 1, 25000) = 1 ([{fd=11, revents=POLLIN}]) read(11, "\1\0\0\0\0\0\0\0", 16) = 8 poll([{fd=11, events=POLLIN}], 1, 25000) = 0 (Timeout) # /dev/null 2>&1 && \ startx -- :0 vt1 # if using rxvt or urxvt immediately set the window to fullscreen if [[ $TERM == *"rxvt"* ]]; then # make the window with rxvt in the name the active window wmctrl -a rxvt # make the active window fullscreen wmctrl -r ":ACTIVE:" -b add,fullscreen fi **Edit: add some dbus information** $ ls -l ~/.dbus/session-bus/ total 28 -rw-r--r-- 1 me me 465 Nov 8 06:23 c984eb16cbd294a01d56c2ac523f7100-0 -rw-r--r-- 1 me me 465 Nov 6 14:11 c984eb16cbd294a01d56c2ac523f7100-1 -rw-r--r-- 1 me me 476 Apr 24 2017 c984eb16cbd294a01d56c2ac523f7100-10 -rw-r--r-- 1 me me 465 Jun 5 2017 c984eb16cbd294a01d56c2ac523f7100-100 -rw-r--r-- 1 me me 476 Apr 7 2017 c984eb16cbd294a01d56c2ac523f7100-11 -rw-r--r-- 1 me me 465 Nov 6 14:37 c984eb16cbd294a01d56c2ac523f7100-2 -rw-r--r-- 1 me me 463 May 6 2016 c984eb16cbd294a01d56c2ac523f7100-3 $ echo $DBUS_SESSION_BUS_ADDRESS # empty!

I have file ~/.config/evince/accels but it is empty. what is the syntax for disabling the idiotic default keyboard shortcuts? Can I perhaps "dump" the current shorcuts, and then edit? I constantly lose my position on page by accidentally pressing some key. I just want to keep PageDown and PageUp so that I can scroll the pages. I am using Evince 43 on Debian

I use evince as PDF viewer and I noticed an annoying issue: spell check language list is filled with useless english variants; (see screenshot below) Question is: **How to trim down the list to a couple of entries?** I am Italian but I also write in English so I need both language but, thus I have installed both aspell-en,aspell-it packages; Even if all those English variants have probably a good reason to exists, I do not need and I want to hide them, since make the workflow more complicated and a waste of time. --- **EDIT:** 1. this question is *evince* or better ***aspell***-specific, since the former's spell checker is based on it; 2. I am looking for **any** kind of solution: a *"proper"* one if it exists, or a brutal one as @tink point out, that's simply delete implicated files --- Arch Linux w/ Evince-46.3.1 aspell-0.60.8.1 aspell-en-2020.12.07

when opening a particular pdf file, evince decides to open it in "presentation mode". I see in the man page that evince has -s option to open in presentation mode, but I did not invoke it. I am simply opening all pdfs as evince file.pdf Somehow evince has decided on its own, to open this particular kind of pdf in presentation mode. Other pdfs open just fine in normal window. How can I disable this behavior?

using Debian testing, Xfce v4.12 here. My preferred PDF viewer, evince (or "document viewer" under Ubuntu? Don't know) keeps changing my print settings, even when I tell it not to: - Open PDF, set number of pages per sheet to 2, print - ~/.config/evince/print-settings is changed to reflect that - next time I want to print one page per sheet I forget and document is printed with 2 pages per sheet - sigh and print again with my "standard settings" Attempted remedies: - tried to make ~/.config/evince/print-settings read-only (chmod 444), to no avail, permissions are set to 644 after printing - chown'ed the file to root:root, but after next print it is reset to USER:GROUP. What's going on? How do I prevent changes to this file, while still being able to use other settings every now and then? Enno

The UI of Evince on my OS is transparent. As you can see, the whole interface is 100% see-through. This makes working with the app very difficult. How do I make it appear opaque similar to other GTK apps? No other GTK apps (i.e. Gnome Tweaks) exhibit this problem. Note: I'm using Debian 12 with GNOME. **Update**: Just found out that the issue occurs because of evince not being able to access the custom theme. This happens because I added the theme in the .themes folder using symlink. I'll add further updates if I'm able to solve the symlink situation. For now, keeping real theme files with proper ownership and permissions is the only solution. Thanks.

Is there a way to customize keyboard shortcuts for Evince, the GNOME document viewer?

Once you have inspected the screenshots below, you will see that Okular is significantly worse at rendering my two test files than many other well-known viewers. This is unfortunate, because in Kubuntu, Okular is the natural default viewer. My questions are as follows 1. Is there anything I can do—e.g. downloading and installing some patches or the like—to improve the rendering in Okular? (The 'Enable Graphics Antialias' and 'Enable Text Antialias' are both already enabled in my Okular.) 2. Why is Okular so much worse at rendering these test files than the other viewers?


**The tests** All the images in this post, for all pdf viewers, were captured using the same size of the capturing region. In order to see what I am talking about, you may have to click on the images and view them in full resolution. **The first test file** The one-page pdf test file in question can be downloaded [here](https://drive.google.com/file/d/1QHnNzo8KnTshYtbulPfWyXH2N1XA-LJL/view?usp=sharing) . It was created using [xournalpp](https://github.com/xournalpp/xournalpp) . Below, I repeat the test with a pdf file created in [Inkscape](https://inkscape.org/) , with similar results. As I said, he 'Enable Graphics Antialias' and 'Enable Text Antialias' are both enabled in my Okular. At 75%, the rendering is mostly fine, although you can see that the left side of the gray square is thinner than the other three, which shouldn't be the case. But real problems start happening when we zoom in, below. As you can see, some of the blue horizontal lines are rendered as significantly thicker than the others. The problem (for this test file) does not affect any other viewers I've tried. Evince: Foxit: PDF-XChange Editor (through Wine): Adobe Acrobat Reader DC (through Wine):

**The second test file** I've tried a different test pdf file, produced in inkscape by copying and pasting the same horizontal line many times (the one-page pdf file in question can be downloaded [here](https://drive.google.com/file/d/1LF4s4M3okuF4FXcp0XWlKsYQhMGegW0Y/view?usp=sharing).) While Okular is still the worst offender, most of the other ones are less than perfect, too: if one plays with different zoom levels, eventually one will hit upon a level where the rendring is off. For this particular file, only with the PDF-XChange Editor have I been unable to find a zoom level where the rendering is off. Okular: In order to see the imperfections in the rest of these, you really may need to click on the images and view them in full resolution (even if you didn't have to do that for the images above). You should be able to see that some of the lines are rendered thinner than the others. Evince: Foxit: Adobe Acrobat Reader DC: As I said, I was unable to find any imperfections in PDF-XChange Editor's rendering of this file at any zoom level. But it is possible I haven't tried enough zoom levels. For what it's worth, though it presumably shouldn't matter, here is my system configuration:
Laptop model: Dell Latitude 7490.
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-48-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz (Graphics: Intel UHD Graphics 620 integrated graphics processor)
Memory: 15.5 GiB of RAM Let me repeat my questions: 1. Is there anything I can do—e.g. downloading and installing some patches or the like—to improve the rendering in Okular? (The 'Enable Graphics Antialias' and 'Enable Text Antialias' are both already enabled in my Okular.) 2. Why is Okular so much worse at rendering these test files than the other viewers?

When I search for a word in a PDF file using mupdf. It, only, finds the whole word. For example, searching for the word “meaningless” will find the whole word: This is a short, staggeringly meaningless sentence. There is no way I can know in advance whether a word is broken over two lines – and therefore: hyphenated – or not. Searching for hyphenation explicitly would also be too cumbersome. However, when a word is wrapped at the end of a line , it will not be found. Searching for “meaningless” won’t find the word in this example: This is a short, staggeringly meaning- less sentence. The PDF viewer "Evince" behaves in the same way. Is there a (simple) way to make "Mupdf" find hyphenated terms?

I have a scanned PDF file , with low-quality OCRed text. I would like to have a PDF file without the OCRed text. How can I convert a scanned PDF with OCRed text to without OCRed text? I am thinking about what ways can recover the original scanned PDF file before OCR as much as possible, without changing the width and height of each page in pixels, and without changing the pixels per inch of each page? Is some kind of rasterization again help? Will rasterization again loose the image quality? Several attmepts: 1. I use the print to file in Evince, which I think uses cups-pdf, it doesn't remove OCRed text. 2. Following command using gs doesn't remove OCRed text either (I think I haven't found out how to use gs properly): gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 \ -dNOPAUSE -dQUIET -dBATCH -sOutputFile=out.pdf toc.pdf

On my machine (see details below) Evince does not open documents as expected, but this depends on the method used. The two methods I mean are: - (A) starting Evince by giving a document as a target (e.g. clicking on the document and using "open with" and "Evince" *or* running evince from the terminal); - (B) starting Evince first, without a document, and then clicking on "open..." in the Evince window *or* dragging a document on top of an already open Evince window (this opens another Evince window with the new document). Method A (mostly) does not work. This results in a hung process, which I can see with pgrep and via an icon in the dock. htop shows that these processes use nearly no CPU and nearly no memory. I can kill these processes normally. However, if I click on the icons for these Evince instances in the dock, my system immediately and completely freezes (I cannot open a tty), and the solution is a forced restart via the power button. The exceptions: Method A sometimes works. I found it (mostly but *maybe* not always? I am unsure now) works on a small (0.5 MB) PDF which *has only images and no text*. I found it would *sometimes* also work on a medium sized (4 MB) PDF with both image and text. In this case, a window would sometimes also appear with the UI for viewing PDFs, but the PDF would not appear. Other times, the process would hang or the PDF would open normally. I found it would not work on a larger PDF (6 MB) with both images and text, and I never got it to work on a small (0.2 MB) PDF with only text and no images. I also tried a small (0.2 MB) .ps image, and could not open it with method A. Method B (mostly) functions normally. The exception: Method B sometimes does not work if a hung process is already running. That is, if a hung process is running, I can get an empty Evince window open, but using "open..." or dragging a document onto the window sometimes opened the document and sometimes not. My machine: - Ubuntu 20.04.6, 64 bit - Windowing system: Wayland - 64 GiB of memory - 11th gen Intel processor - Some onboard graphics: Mesa Intel XE (TGL GT2) - 2 TB SSD space, nowhere near full Additionally, I'll add that this was not always a problem. I used to be able to use Evince totally normally. However, at some point in time in the past, this behavior started, and I simply avoided using Evince because I couldn't identify what might have changed. Some more diagnostics: I tried running strace on a hung Evince process. I read this could be helpful, but I don't understand any of the output:

strace: Process 12102 attached
restart_syscall() = 1
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
recvmsg(11, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\4\1\1\21\0\0\0\373\5\0\0\205\0\0\0\1\1o\0\30\0\0\0/org/a11"..., iov_len=2048}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 169
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
recvmsg(11, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}], 3, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\3\0\0\0\0\0\0\0", 16)         = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}], 3, -1) = 1 ([{fd=11, revents=POLLIN}])
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
recvmsg(11, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\4\1\1\21\0\0\0\375\5\0\0\205\0\0\0\1\1o\0\30\0\0\0/org/a11"..., iov_len=2048}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 169
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
recvmsg(11, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}], 3, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\3\0\0\0\0\0\0\0", 16)         = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}], 3, -1

I waited some minutes, and no additional output was written. I also ran netstat because read that could be helpful, but again I don't understand the output.

$ netstat -p | grep 12102
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
unix  3      [ ]         STREAM     CONNECTED     150817   12102/evince         
unix  3      [ ]         STREAM     CONNECTED     149214   12102/evince         
unix  3      [ ]         STREAM     CONNECTED     149075   12102/evince         
unix  3      [ ]         STREAM     CONNECTED     149074   12102/evince         
unix  3      [ ]         STREAM     CONNECTED     149213   12102/evince         
unix  3      [ ]         STREAM     CONNECTED     151902   12102/evince

I ran ls -l /proc//fd, again, because I read it could help. On a hung process (12102) and then, after killing this process and using method B on the same PDF (process 15795):

@:~$ ls -l /proc/12102/fd
total 0
lr-x------ 1   64 Okt 11 18:37 0 -> /dev/null
lrwx------ 1   64 Okt 11 18:37 1 -> 'socket:'
lrwx------ 1   64 Okt 11 18:37 10 -> 'socket:'
lrwx------ 1   64 Okt 11 18:37 11 -> 'socket:'
lrwx------ 1   64 Okt 11 18:37 12 -> 'anon_inode:[eventfd]'
lr-x------ 1   64 Okt 11 18:37 13 -> anon_inode:inotify
lr-x------ 1   64 Okt 11 18:37 14 -> '/home//.local/share/gvfs-metadata/home (deleted)'
lr-x------ 1   64 Okt 11 18:37 15 -> '/home//.local/share/gvfs-metadata/home-a9b0a1cb.log (deleted)'
lr-x------ 1   64 Okt 11 18:37 16 -> /home//Downloads/.pdf
lrwx------ 1   64 Okt 11 18:37 2 -> 'socket:'
lrwx------ 1   64 Okt 11 18:37 3 -> 'socket:'
lrwx------ 1   64 Okt 11 18:37 4 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:37 5 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:37 6 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:37 7 -> '/memfd:wayland-cursor (deleted)'
lrwx------ 1   64 Okt 11 18:37 8 -> 'socket:'
lrwx------ 1   64 Okt 11 18:37 9 -> 'anon_inode:[eventfd]'
@:~$ ls -l /proc/15795/fd
total 0
lr-x------ 1   64 Okt 11 18:58 0 -> /dev/null
lrwx------ 1   64 Okt 11 18:58 1 -> 'socket:'
lrwx------ 1   64 Okt 11 18:58 10 -> 'socket:'
lr-x------ 1   64 Okt 11 18:58 102 -> '/home//.local/share/gvfs-metadata/root-5357d137.log (deleted)'
lrwx------ 1   64 Okt 11 18:58 11 -> 'socket:'
lrwx------ 1   64 Okt 11 18:58 12 -> 'anon_inode:[eventfd]'
lr-x------ 1   64 Okt 11 18:58 13 -> anon_inode:inotify
lr-x------ 1   64 Okt 11 18:58 14 -> '/home//.local/share/gvfs-metadata/home (deleted)'
lrwx------ 1   64 Okt 11 18:58 15 -> '/memfd:wayland-cursor (deleted)'
lr-x------ 1   64 Okt 11 18:58 16 -> '/home//.local/share/gvfs-metadata/home-41fe52fb.log (deleted)'
lr-x------ 1   64 Okt 11 18:58 17 -> /home//Downloads/.pdf
lrwx------ 1   64 Okt 11 18:58 2 -> 'socket:'
lrwx------ 1   64 Okt 11 18:58 3 -> 'socket:'
lrwx------ 1   64 Okt 11 18:58 4 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:58 5 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:58 6 -> 'socket:'
lr-x------ 1   64 Okt 11 18:58 60 -> '/home//.local/share/gvfs-metadata/root (deleted)'
lrwx------ 1   64 Okt 11 18:58 7 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:58 8 -> 'anon_inode:[eventfd]'
lrwx------ 1   64 Okt 11 18:58 9 -> '/memfd:wayland-cursor (deleted)'

This looks the same to me, except that the latter process has two "wayland cursor" lines. I would appreciate all your suggestions about how to diagnose this. I typically would use Okular for PDFs, but I found Evince tended to work better with PDFs that have large images, and I am starting to view more PDFs of that kind. Also, this problem just utterly perplexes me and I'd like to solve it.

Say I start off from a PDF document, say of 12 pages, viewed with **evince**. To produce another PDF of 6 sheets, with a page setup of two pages per side, I normally use the "Print to File" device listed in the ^P dialogue window. This works out pretty neatly. I would like to translate this operation for the command line. - To my understanding, this is not an operation that **pdftk** can do. Please cross check. - The command lp, which would accept the option -o number-up=2, does not recognize any device called "Print to File", which indeed does not show up in lpstat -p -d. - I am aware of the post What is “Print to File” and can it be used from command line? . I have installed **cups-pdf** whereby a new printer named PDF is acknowledged. However, the print quality of a simple text file is way too raw (for example, no print margins to start with). Moreover, if I reprint an existing PDF file on this device, say lp -p PDF existing.pdf, evince can't even manage to open that copycatted output, while this is not the case with the "Print to File" way. - I had a look at man evince. At the bottom, it touches upon a few print preview options and redirects to a GNOME-developer project page . Admittedly I am not able to make sense and use of it. Is there actually a way to combine the flexibility of the command line with the print quality that I obtain from that "Print to File" option in the GUI evince? My test case, again, would be to create from the command line a PDF out of a source document printed with two pages per sheet. Thanks for thinking along.

I am running 16.04 with evince GNOME Document Viewer 3.20.1 Now evince 4.X displays hyperlinks as pop-up windows, which is very useful for documents with equations. I installed evince 4.4 via snap sudo install snap and even linked the binaries to /usr/local/bin

sudo ln -s /snap/bin/evince /usr/local/bin/evince

However the daemon does not start!

snap services just shows
Service            Startup  Current  Notes
cups.cups-browsed  enabled  active   -
cups.cupsd         enabled  active   -

but I need the org.gnome.evince.Daemon.service so I changed the line

[D-BUS Service]
Name=org.gnome.evince.Daemon
Exec=/usr/lib/evince/evinced
SystemdService=evince.service

to

[D-BUS Service]
Name=org.gnome.evince.Daemon
Exec=/snap/evince/current/usr/libexec/evinced
SystemdService=evince.service

but it did not help running

/snap/evince/current/usr/libexec/evinced

resulted in

/snap/evince/current/usr/libexec/evinced: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/evince/current/usr/libexec/evinced)

which is odd since I thought the idea of snap is, to have a self-contained binary without external dependencies. I have no glibc 2.34 installed and rather prefer not to mess up my 16.04 distribution the point is I need evinced to run, so that Emacs is able to communicate between the latex source file and the pdf file displayed by evince (forward and inverse search from source to pdf) any ideas? thanks in advance Uwe Brauer

while I successfully installed evince, via snap for Ubuntu 16.04 (see https://unix.stackexchange.com/questions/755478/ubuntu-16-04-install-evince-via-snap-but-no-service-via-dbus?noredirect=1#comment1438828_755478) I run into a problem when I try to do the same for a friend using Ubuntu 20.04. The installed works as expected, but when I open evince, via /snap/bin/evince and then a pdf file that contains hyperrefs the pop-up window pops up as it does in my Ubuntu 16.04, but the pop-up window is **empty** The message in the command line is

infinite surface is not supported.

I have no idea what this is supposed to mean. any help is strongly appreciated. Uwe Brauer

Upon opening a pdf in evince and then making a change to that document (recompiling it in LaTeX), evince will automatically refresh to the latest version of the document. mupdf however does not do this: it keeps showing the version I originally opened. The latest version can be loaded with the r command, but is there a way to make mupdf behave like evince in that respect? The manual doesn’t mention this.

It is extremely likely this question comes from a major misunderstanding, but I will explain what I am trying to do/have done. I am also not fully sure this is a Linux/Unix issue. My goal is to view a pdf on a remote computer that I am accessing with ssh -X. For context, I am doing this on Windows 11 Powershell. (EDIT) This is on my local laptop using Windows 11 Powershell. I want this display to be on my local laptop and the pdf is on the remote computer which uses Linux. I installed WSL while trying to figure this out, but I don't think I've used it for anything. I started with using evince Filename.pdf as I've done on my school's lab computers, but it gives me Cannot parse arguments: Cannot open display: I've tried setting a display with export DISPLAY='IP:0.0' because some StackExchange comments said to try that. I called xhost + a bunch. I don't know what that does, but comments said do that. My question is simply how to use Evince to open this PDF file. I'm not specifically tied to Evince. I just want to view the PDF and I'm unsure of the process. It's worth mentioning that I have sudo permissions.

Suppose I have opened a pdf file (say /path/to/my/file.pdf generated from LaTeX) in evince and want to open the corresponding LaTeX source file (/path/to/my/file.tex) in my emacs editor, I click on properties in evince and copy the path to the file to the clipboard, paste it to the minibuffer from emacs find-file dialogue, manually change the file ending pdf to tex and open the file. Now I want to ask if there is a significantly faster way to do the same thing (maybe using another pdf-viewer), for example by configuring a keyboard shortcut (for example in the pdf-viewer itself or on wm level, in my case xmonad) or configuring a custom button in the pdf viewer. **Edit** I should add that the situation where I need it is, that I have 20 pdf documents opened at the same time. **Edit 2** Following @meuh suggestion I tried the following

cat get_tex_name.sh

#!/bin/sh
pid=xprop _NET_WM_PID
filename=ls -l /proc/'$pid'/fd/ | grep pdf |  sed 's/.*\(\/.*home.*\).pdf/\1tex/'
#emacsclient -c $filename
urxvt -hold -e sh -c "echo $filename"

and in my .xmonad file:

[...]
-- find corresponding tex file
    , ((modm,               xK_p     ), spawn "get_tex_name.sh")

Now if I have a focused evince instance and run the stript via Windows-p, it doesn't seem to get the filename (I think because xprop doesn't seem to return the pid of the focused window but only after clicking on it). So how to make it work?

I'm desperately looking for the integration of keyboard shortcuts to add notes and highlighting to PDF documents in Evince on Ubuntu 18.04 LTS. This feature comes with evince 3.31.0 but Ubuntu 18.04 ships 3.28.4. What I tried so far: - Installed ppa:gnome3-team/gnome3 repository and tried to upgrade from there as suggested [here](https://askubuntu.com/questions/310974/how-can-i-install-the-latest-version-of-evince) . The package manager insists that I already have the newest version. - Install the newest version of evince from source. Configuring, making and installing works fine, but

evince: symbol lookup error: evince: undefined symbol: ev_view_set_enable_spellchecking

- install *exactly* the version that ships the feature, 3.31.0, from source, same issue as above. - try the previous, but disable spell checks upon configuring with --without-gspell as suggested [here](https://unix.stackexchange.com/questions/564110/how-to-install-and-run-evince-from-tar-gz) , but the error is the same. Any help would be appreciated since I (1) do not like other pdf viewers and (2) need the feature for commenting on publications. Thanks!