Is #firefox really the best way to sign a #pdf document on #linux with a touchscreen? I somehow cannot believe that even after trying 5 different programs...
@holgerschurig I'm absolutely willing to do a) on a limited range of programs (mostly spacemacs). However, for b) it goes both ways. Do developers make it easy to report issues and feature requests? Do they actually want to see feature requests or are those a nuisance for them? Users don't want to create the nth account on a custom bug tracker, waste time looking for possible duplicates on bug trackers with poor search functionality (I'm looking at you, bugzilla) and in the end run into a dev who poorly communicated the scope of their project to start with.
Do I want a non-Firefox way of signing PDFs? No, I already scratched the itch (signing the document and setting Firefox as default for opening PDFs). I'm just surprised that organizations like #GNOME spend development effort into #evince. But yes, I guess that's your point, it isn't PM driven...
Das Evince-Projekt kann derzeit keine grösseren Änderungen durchführen, wie etwa die Portierung auf GTK 4 und Libadwaita. Diese Ziele werden nun im Rahmen des Papers-Projekts verfolgt.
"'"And if you did not know already, that Core app is #Evince, now renamed to #Papers and submitted to Incubation this week. But if you’re still interested after the spoiler, let’s start from the beginning."'"
(Some people add %O %S after evince, but those are unnecessary in my case.)
The command runs xelatex, creates a pdf, and opens it in #Evince; and it continues running so that any change in document.tex appears in Evince shortly after it is saved.
I've also created an #Emacs command to run the process.
While triaging some #Mutter issues in #GNOME, I saw a claim that the default "extend to external display on connect" behavior is confusing for some non-technical presenters.
Unable to trigger the issue using LibreOffice Impress, I did some #usability mind-reading and guessed that they must have been using a PDF instead of .odp/.pptx, in which case yes, the #UX would fail because the #Evince#PDF reader doesn't handle this correctly. Filed: https://gitlab.gnome.org/GNOME/evince/-/issues/1986
#TIL sometimes windows in #GNOME, especially #evince, seem not to open at all, but in fact they are located somewhere outside the visible area.
Solution: pressing SUPER + UP brings them up full screen, then they can be moved and resized as usual.