kanshi
grim
kanshi | grim | |
---|---|---|
22 | 11 | |
553 | 757 | |
- | - | |
5.9 | 6.9 | |
over 2 years ago | about 2 years ago | |
C | C | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kanshi
-
Sway external display
Without digging into you problem, i just let you know one options/tool as an addition: https://github.com/emersion/kanshi
-
Starting kanshi from sway
This works, but after a reload of the config the configuration is gone. Then I found this discussion and changed the line to:
-
Arch users belike
Kanshi is not exactly what you're looking for but i stumbled across this when I was writing the dynamic display configuration page.
-
Terminal font size on hidpi + normal display
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.
-
Inaccessible workspaces
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.
-
How to toggle transparency and gaps? Preserve display configuration?
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.
- Single Background / Multiple Monitors
-
Script for docked mode
kanshi should be able to do it.
-
Organising workspaces on multiple monitors
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.
-
Sway not picking the highest refresh rate available
For this you can use kanshi.
grim
-
Ubuntu 22.10: Error "compositor doesn't support wlr-screencopy-unstable-v1" when trying to record the screen
"GNOME doesn't support wlr-screencopy-unstable-v1, which is the protocol grim uses to take screenshots." Source.
-
[GRIM] question
It's in the README
-
Good cli screenshots tool under wayland ?
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 .
-
Tell HN: Gnome on Wayland Is Amazing
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
[5] https://github.com/dunst-project/dunst
[6] https://hg.sr.ht/~scoopta/wofi
-
Screenshot app: remembers "selection" mode, copies to clipboard, wayland support?
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.
-
What apps are you running on Sway? (Wayland Native Apps of course)
Screenshots: grim + slurp + swappy
- Can I install Spectacle merely without other kde packages?
-
How can I take screenshot with imagemagick?
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?
-
What are some automation scripts that have made your life easier?
# 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.
-
Flameshot, powerful screenshot tool, fully support Wayland (able to run on sway)
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.
What are some alternatives?
wlr-randr - An xrandr clone for wlroots compositors
slurp - Select a region in a Wayland compositor
wayvnc - A VNC server for wlroots based Wayland compositors
swappy - A Wayland native snapshot editing tool, inspired by Snappy on macOS
dwl - dwm for Wayland - ARCHIVE: development has moved to Codeberg
wayland-protocols - Wayland protocol development (mirror)
wdisplays - GUI display configurator for wlroots compositors
wl-clipboard - Command-line copy/paste utilities for Wayland
wayland - Core Wayland protocol and libraries (mirror)
xdg-desktop-portal-wlr - xdg-desktop-portal backend for wlroots
wdisplays
Waybar - Highly customizable Wayland bar for Sway and Wlroots based compositors. :v: :tada: