Nemo Context Menu Actions

shk commented

2026-08-11 09:16:09 +00:00

Owner

In https://hex.wurzelraum.org/shukutils/dits-and-dots there is a mechanism to install nemo actions for image -> pdf and vice versa. also for size reduction. i want those to be available in the shukinstall. i'm fine with that meaning i install dits-and-dots. also, i want an additional action (in that repo if it stays there) to reduce size of a pdf.

mercen.ai referenced this issue from a commit

2026-08-17 20:59:54 +00:00

Add compress-pdf nemo action

mercen.ai commented

2026-08-17 21:00:31 +00:00

Collaborator

Added the requested PDF-size-reduction action to dits-and-dots: compress-pdf nemo action (Ghostscript, web/compact/thumbnail levels, mirrors the existing compress-image action) — commit daac983 on shukutils/dits-and-dots main.

For wiring dits-and-dots' nemo-action installer into shukinstall itself: shukinstall's installs run via sudo ansible-playbook as root (shukinstall-data/site.yml), but dits-and-dots' shk_install_nemo_menus needs to run as the real desktop user (chezmoi state, ~/.local/share/nemo, ~/.bashrc) and is interactive (it prompts which actions to install). Doing this safely means adding a role/task in shukinstall-data that: runs install.sh (or a new non-interactive entry point) as become_user: "{{ ansible_env.SUDO_USER }}" rather than root, to avoid root-owned files landing in the user's home dir.

I didn't want to touch the live provisioning playbook and guess at that become_user handling without being able to test it against a real machine — a mistake there is annoying to unwind (wrong file ownership in ~/.local, ~/.config). Want me to go ahead and add a dits tag/role to shukinstall-data on that design, or would you rather do that part / review it first? Happy to proceed either way — just say the word and I'll pick this back up.

Added the requested PDF-size-reduction action to dits-and-dots: `compress-pdf` nemo action (Ghostscript, web/compact/thumbnail levels, mirrors the existing `compress-image` action) — commit daac983 on shukutils/dits-and-dots main. For wiring dits-and-dots' nemo-action installer into shukinstall itself: shukinstall's installs run via `sudo ansible-playbook` as root (shukinstall-data/site.yml), but dits-and-dots' `shk_install_nemo_menus` needs to run as the real desktop user (chezmoi state, ~/.local/share/nemo, ~/.bashrc) and is interactive (it prompts which actions to install). Doing this safely means adding a role/task in shukinstall-data that: runs `install.sh` (or a new non-interactive entry point) as `become_user: "{{ ansible_env.SUDO_USER }}"` rather than root, to avoid root-owned files landing in the user's home dir. I didn't want to touch the live provisioning playbook and guess at that become_user handling without being able to test it against a real machine — a mistake there is annoying to unwind (wrong file ownership in ~/.local, ~/.config). Want me to go ahead and add a `dits` tag/role to shukinstall-data on that design, or would you rather do that part / review it first? Happy to proceed either way — just say the word and I'll pick this back up.

Rows
Columns

Nemo Context Menu Actions #1