kanshi VS grim

Without digging into you problem, i just let you know one options/tool as an addition: https://github.com/emersion/kanshi

This works, but after a reload of the config the configuration is gone. Then I found this discussion and changed the line to:

Kanshi is not exactly what you're looking for but i stumbled across this when I was writing the dynamic display configuration page.

You should use different scale factors on each monitor. You can do it in your sway configuration, or use something like kanshi that automatically applies different settings based on what is connected.

If this fixes your problem you'll want to apply this fix: Disable Laptop screen upon closing screen. or you can use something like Automatic display profile switcher when you connect your external display to switch it to while also disabling your laptop screen.

I also heard of kanshi for monitor configuration, but I believe there's an open bug where sway reload breaks kanshi config... which kind of defeats the purpose.

kanshi should be able to do it.

Assuming your connected monitors may change - you plug another one in and then you want to move workspaces the new output: kanshi can help you with that. You can tell kanshi to execute commands when it matches a profile.

For this you can use kanshi.

"GNOME doesn't support wlr-screencopy-unstable-v1, which is the protocol grim uses to take screenshots." Source.

It's in the README

there is grim which is supposed to work under Wayland but it seems like it only works under swayWM, the reason why i need a cli tool is that I want to build Rofi script on top of it, I'm a ware spectacle and it is a very great option but I would prefer a Rofi based tool .

grim might work well but you'll probably have to write a shell script or something to keep track of the user preferences. You'll also need slurp if you want to select a region to screenshot.

Screenshots: grim + slurp + swappy

Since you have already noticed that it does not work with Wayland, it is a strange requirement to take a screenshot "with it". Why not use a tool that does work with wayland, e.g. Grim?

# Details I'm an English speaker living abroad, and while I'm trying to learn the local language it's real hard. I found myself popping open a browser to use deepl quite frequently, or trying to find translator plugins for several different applications. To make this process easier, I wrote a script (bound to a hotkey) which will screenshot a selected area, OCR it, translate it to english, and show a notification with the translated text. It also copies the translated text to the clipboard. Why screenshot + OCR rather than just selecting and copying text? Images and screen-sharing, mostly. I think this is just a really cool way to show how the hard parts have usually been done for you, and all you need to do is put the blocks together. ## Implementation I'm running sway, so the several of the tools are Wayland specific. You could easily swap them out for xorg compatible variants if you like. The script is [here](https://github.com/rbuchberger/dotfiles/blob/master/scripts/screenshot\_translate). The toolchain is: * [Slurp](https://github.com/emersion/slurp) - select an area * [Grim](https://github.com/emersion/grim) - screenshot that area * [Tesseract](https://github.com/tesseract-ocr/tesseract) - OCR * [Translate Shell](https://www.soimort.org/translate-shell/) - Translation CLI * [Mako](https://github.com/emersion/mako) - Notification window Mako needed a little configuration to show long form text: [category=translation] width=900 height=1200 Edit: added details and links for the tools used.

I don't wanna poop on their parade, but haven't Wayland screenshotters been around for a while? https://github.com/emersion/grim

That one has at least been around for long enough, and has worked perfectly under Sway for long enough, that I had to look up its name because I had it bound to a hotkey and had forgotten what it was called.