What are /r/swaywm's favorite Products & Services?

From 3.5 billion Reddit comments

I've been using CopyQ on sway, in runs natively in Wayland when it comes to handling the clipboard, and also when it comes to its UI (it's built on Qt). It has excellent image handling as well. The only thing I never managed to make it do is auto-typing of the clipboard contents after selection.

I also do a tiny bit of layouting (auto-tiling, tiling/tabbing all windows of a workspace) in swayr and AFAIK, you cannot have empty space and then open a window there. Also, I think, new windows will always appear "after" the current one, i.e., to the right in a vertically tiled container. I see no other way as to use move commands which will induce a bit flicker. But well, one uses sway for efficiency and not for eye candy, right? ;-)

Maybe you could make use of [con_mark="main_XXX"] move position center to move the main window into the center of the workspace after a new window appears? I didn't test but the docs suggest that would be the most simple solution.

Out of curiosity: did you try the normal blocking version of sway-ipc before using the async version? If so, why did you switch to async? I've never tried the latter but haven't seen a reason to try it out given that the number of events my demon receives is easily manageable even when I press and hold a shortcut so that it gets repeated 2 dozen times a second ("Super Super" is my switch-to-last-recently-used-window shortcut). Well, and even if my demon would hang a second, I'd hardly notice it.

No, the Arch User Repository (AUR) is a place where anyone can upload build-scripts. It is not guaranteed to be vetted by the Arch folk.

pacman can only access the official repositories, so what you installed by that command is from there, and not the AUR.

These are the catalogues of the official repos, and the AUR:
https://www.archlinux.org/packages/
http://aur.archlinux.org/

Split into parts: https://gitlab.com/xPMo/dotfiles.cli/-/tree/dots/.config/sway/conf.d

I have a couple unique takes:

• System control is on $mod+F1-F4, instead of $mod+Shift+c/r/e
• No split h/v bindings, $mod+n being split toggle is almost always what I want anyway.
• Lots of assign/for_window rules. Dedicated workspaces for web, mail, games, audio, doc. These all have numbers above 10, so they are sorted after workspaces 1:1 - 9:9, 10:X.
• $mod+x enters Focus/Launch mode. In this mode, I have <key> bound to first attempt to focus a program, then launch it if no matching app_id/class is found. Then I bind Shift+<key> to launch a program without trying to find an existing window first.
  • Example: $mod+x, w will focus a Firefox window (Web browser) if it exists. Otherwise, it launches Firefox.
  • Exception: $mod+x, x will run wofi -Sdrun as a program launcher. I have $mod+x, $mod+x bound for convenience as well.

I am also trying to implement something like this when launching applications. I think using systemd-run --user --slice=app --scope may be sufficient.

Looks like packager error. Fixed in the yet-unreleased sway 1:1.4-4. Grab the updated config and include it if you like, or just wait for the maintainer to release the fix.

Sway aims for feature parity with i3 where wayland doesn't demand differences, so here:
https://i3wm.org/docs/userguide.html#binding_modes

This is all the documentation in sway itself:

manpage sway(5) ... mode <mode> Switches to the specified mode. The default mode is default.

mode [--pango_markup] <mode> <mode-subcommands...> The only valid mode-subcommands... are bindsym, bindcode, bindswitch, and set. If --pango_markup is given, then mode will be interpreted as pango markup.

I'm still be very manual (I don't assign workspaces automatically) but I think you're looking for the assign configuration:

# Assign URxvt terminals to workspace 2
assign [class="URxvt"] 2

There's a bunch of different criteria filters to use. I tend to do swaymsg -t get_tree | grep appname to try figuring out what I can filter on.

For the ones that don't run, it might be worth checkout out what is actually executed in the desktop files under /var/lib/flatpak/exports/share/applications. I also wonder if trying to do a exec swaymsg exec flatpak run com.spotify.Client would work oddly.

Funny, because I was just reading about yambar (a status bar/panel for X11/Wayland by the author of foot) and he explicitly requests you to use icon fonts.

> There is no support for images or icons. use an icon font (e.g. Font Awesome, or Material Icons) if you want a graphical representation.

Ah. I just try foot again and the newest stable release 1.8.2 fixed that problem. What I meant is described here in foot issue. https://codeberg.org/dnkl/foot/wiki#user-content-cut-off-glyphs

In previous versions, Nerd Font icons get cut-off. For example, I could only see half of the Python Icon in neovim. I'm so glad that it gets fixed since foot runs really smoothly on my PC.

Yes, they have a complete manpage available to consult on your terminal with the command man rofi. You can also see it online here

1. Well, you can compare the two yourself if you wish, I like Alacritty because of GPU-acceleration. It works really well keeping ncurses apps snappy, and is under constant development.

2. You might look at this blog post.

There's been a pinebook pro (arm) sway edition for a while. It's what I use on my PBP for fiddling around. It's been really stable and great for me for the last 5-6 months. https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-sway/

Fwiw there is also a fairly small utility by one of the maintainers of swaywm: https://sr.ht/~kennylevinsen/wlsunset/

I never got the red shift fork to work properly and wlsunset is a nice tiny thing (even if it has no geoip, it doesn't matter)

> I tried to love i3, but was stuck with screen tearing issues on x11 that I could never fix properly.

Similar story here, except for me scaling was the straw that broke the camels back. Getting i3 to work well with one high DPI screen (a macbook pro with the so-called retina display) and a cheap extra monitor was quite painful in i3, but with built-in scaling support in sway it literally just worked out of the box. I think even before I'd got my config all set up even.

I'm also one of those weirdos who use their laptop both as a portable computer and a workstation, so automatic detection of displays being added and removed is great.

> (And thank you to the Manjaro team for packaging and maintaining Sway - it was just a pacman install away!)

Isn't manjaro using the package from the arch community repo just with some time delay?

I think, for it to work in the terminal, you need to have https://www.archlinux.org/packages/community/x86_64/bemenu-ncurses/ installed. If you uninstall bemenu and then reinstall it, it prompts you for which bemenu-renderer to use.

I never understood the craze about Arch tbh. I mean, all you do there you can do with other distros too just with higher quality packages (is my impression). If people use Debian, Fedora, openSUSE and just select a minimal install on the system. Or if they just partition, format etc by hand on a live cd and then install Debian (etc) on there without the official installer.. I don't see why Arch is special in this regard. The wiki is very good though. And actualy I think this is why people like Arch. All the information in one place and they don't have to hunt for it themselves.

Link to Debian by hand installation (as an example): https://www.debian.org/releases/buster/amd64/apds03.en.html

Yeah, I always used dd too until I read the Debian installation guide for some reason, which suggests cp and sync: https://www.debian.org/releases/stable/amd64/ch04s03.en.html#usb-copy-isohybrid

Swayr has the commands next-window-of-same-layout & prev-window-of-same-layout which switch between windows whose parents have similar layouts, that is, stacked and tabbed are considered to be there same layout where splits are different. That would probably fit your bill.

Have a look at https://sr.ht/~tsdh/swayr/

For keeping clipboard data after an application exists, I've written clipmon.

My intent with this tool was to actually monitor the clipboard to log when applications snoop in it, but due to how the protocol works, I had to implement a full clipboard manager for that to work.

It doesn't mess up mime types or formatting in any way, and your data is never flushed to disk (this is important to me since I often copy data that's too sensitive to have lying around).

I suspect it's basically same issue as here:

https://codeberg.org/dnkl/yambar/issues/106

It should already be fixed in git master (just no new release since the fix landed). But you can try...

It's a libinput "clickpad" option. You want "clickfinger" (https://wayland.freedesktop.org/libinput/doc/latest/clickpad-softbuttons.html?highlight=clickfinger#clickfinger) rather than "software button areas" (https://wayland.freedesktop.org/libinput/doc/latest/clickpad-softbuttons.html?highlight=clickfinger#software-buttons). To set this in Sway, as listed in man sway-input, you need the following:

input type:touchpad { click_method clickfinger }

Note that it's more clear to call it a "two-finger click" and a "three-finger click", since "double click"/"triple click" usually mean clicking wih a single finger two or three times in a row.

Don't know exactly how you do this, but I do know you'll want to check out this to see how libinput deals with button areas and 'clickfinger' behaviour, and the 'Libinput Configuration' section of sway-input's man page (or man sway-input) to see how to apply that in your Sway config file.

Don't worry nobody knows everything and asking questions is the only way to find out. Basically you can send any number of windows to the scratchpad to be recalled for later use. Once in the scratchpad they are no longer visible but are still there. Sorry if my description is rubbish but it sounded ok in my head. Incase you want more info See here

You got me thinking: why do we even need all these little stats on the screen all the time? Is it 2001 and are we still tinkering with E16 and gkrellm?

If I'm honest, I only care about the time in HH:MM format (not the year, the month, or the day, really), the level of the battery if I have one, and that's just about it. I like to see the new-ish PSI indicators – none of the bars have those – but really I don't care a lot about CPU usage, load average, RAM usage or disk usage. If and when I do need to know these, I can just fire up Htop or run a quick df.

Long story short, I replaced all of it with a 15-line Python script which I maybe could later rewrite in a language that's more CPU-efficient. No need for little pictures because there's so little that it's pretty obvious what is what.

Thanks for pointing this out. I was wondering if I had done something wrong on my machine.

As an alternative, I added my user to the video group and that worked too. Light's README.md mentions this as a requirement if using a udev rule, which looks like arch linux does https://www.archlinux.org/packages/community/x86_64/light/

Mostly stuff I carried over from "Wallpaper Engine" like videos and screencaps of the 3d stuff. But I also got some more from Youtube and https://pixabay.com/videos/search/looping/. Have fun filling up your wallpaper folder!

I'm a recent convert to i3/sway, after a solid decade using spectrwm (which has not been ported to Wayland, I'm afraid).

I am still learning how to fully exploit the i3/sway tree model, so I was a bit perplexed when I found this binding in the default config:

```

# Move focus to the parent container
bindsym $mod+a focus parent

```

I had tried the binding, but even though I saw its effects, I wasn't sure what was it good for.

After reading your question, something clicked in my mind. I think it is the answer you are looking for!

Hope that it helps.

Happy hacking,

Read the i3 user's guide, especially how command criteria work. (sway and i3 have much in common.) You might need to negate a PCRE, and that's the bit I stumble on, but otherwise it tells you how to have a command work only on certain conditions.

https://i3wm.org/docs/userguide.html

The i3 protocol is based on json messages sent through a socket. https://i3wm.org/docs/ipc.html Sway uses the same protocol, with some extensions and minor differences where wayland has differences like app_id vs class. https://github.com/swaywm/sway/blob/master/sway/sway-ipc.7.scd

There is no common IPC mechanism for wlroots compositors. Some functionality may be exposed through wayland protocols like wlr_foreign_toplevel_management_unstable_v1, wlr_output_management_unstable_v1, or wlr_output_power_management_unstable_v1.

It seems like your primary concern is security? Are you using QubesOS? https://www.qubes-os.org/

If no you should take a hard look at it, seems like it has some design goals that fit with your security model. Not Wayland/Xorg specifically, but the whole OS.

I have a similar issue with my monitor -- the monitor doesn't report what it is correctly to the OS for some reason. I was able to fix my issue with a simple boot parameter. I use systemd-boot, so I made a custom entry at /boot/loader/entries/fix_monitor.conf:

title    Arch Linux for Home
linux    /vmlinuz-linux
initrd   /initramfs-linux.img
options  video=DP-1:1920x1080@60 root=PARTUUID=71925b3d-df2d-4e83-bbfc-3c16eb029157 rw quiet splash

I made the entry by simply copying the one Arch generated for me at /boot/loader/entries/arch.conf, then adding that one option video=.... In case you don't know, the first part is the name of the display, followed by the . I know my monitor is 1920x1080 and runs at 60Hz. To get the name of the display, you can check swaymsg -t get_outputs (though there are other ways too, which I can't remember)

More info about adding boot parameters here: https://wiki.archlinux.org/index.php/Kernel_parameters

Kernel docs on video option: https://www.kernel.org/doc/html/latest/fb/ep93xx-fb.html#setting-the-video-mode

Yes, since you can configure sway and waybar how you like I'd say this is possible. You can run shellscripts with sway or waybar btw so you could create a hotkey or a button on waybar and then run a script like an app launcher.

Ima leave my config here (I have a screenshot-, qrcode- and color picker tool as buttons on waybar): https://codeberg.org/papojari/nixos-config-desktop/src/branch/main/users/default

You'd have to teach the other users some hotkeys (list of hotkeys on wallpaper?) or make buttons for those hotkeys.

Does anyone know how to set font size? I was reading the section on the repo on DPI and fontsize but it was lost on me. That and for some reason colors in the LF file manager don't work, but they work fine in sakura...

Recently IME support has been implemented into foot and it is supposed to be working with the above (wlhangul, etc.) and fcitx5, provided you have the input method keyboard grab patch for sway. I haven't tested it either because I am too lazy to use the patch, will just wait until it gets merged into master.

Nevertheless, it is a great minimalistic terminal emulator. Definitely worth checking it out!

Celluloid is also installed, but I want a simple popup gui for mpv like here on the right side

https://www.slant.co/versus/13972/13973/~mplayer_vs_mpv

Season 4. A lot of blah blah and a little action. But I like him

Maybe have a try of luakit, which basically is a webkit-based and vim-like browser written in C and Lua. In addition, it is faster than qutebrowser. Really good document and free customization as well.

No, just warning: I have met plenty of people who persuaded that as a Windows “power users” (whatever it means) they will have no problems with really hardcore Unix tools, and then they were very disappointed. Let me just quote (yes, that IS the true condescension):

> Because dwm is customized through editing its source code, it’s pointless to make binary packages of it. This keeps its userbase small and elitist. No novices asking stupid questions. (from http://dwm.suckless.org/)

Yes, sway is much more user-friendly than that, but it is still not exactly the same as Gnome or KDE. And I am not saying that it is bad, I like sway mostly because of that, but the learning curve is rather steep.

And I didn’t know that the OP has been using i3.

You don't eliminate it via sway config, but better by libinput quirks https://wayland.freedesktop.org/libinput/doc/latest/device-quirks.html . So, for example, I have for Microsoft Bluetooth Sculpt Mouse this in /etc/libinput/local-overrides.quirks:

[Microsoft Sculpt Comfort Mouse] MatchUdevType=mouse MatchBus=bluetooth MatchVendor=0x045E MatchProduct=0x07A2 AttrEventCodeDisable=BTN_SIDE

To find out what exactly you need to disable, you can use evtest.

Saying compositing is built-in is kinda misleading as it would suggest they could be separate entities. You will also find the term "Wayland compositor" come often time in the official docs.

scroll_method etc. are settings that are passed directly to libinput. But, libinput doesn't send scroll events for tablet devices (https://wayland.freedesktop.org/libinput/doc/latest/scrolling.html), so this option has no effect.

Could you open a ticket on https://github.com/swaywm/sway/issues regarding this, describing how it works in other WMs? I haven't noticed this behavior before elsewhere, at least.

FingerLow is not a setting, it's a synaptics option.

sway uses libinput, not synaptics, when transforming evdev event streams into wl_pointer event streams. libinput has no equivalent.

In synaptics, it seems that FingerLow is related to pressure sensitivity in pressure sensitive touchpads. In libinput, those settings are modified by hwdbs instead of a libinput option.

See the libinput docs on this topic. If you have such a touchpad you can use sudo libinput measure touchpad-pressure --touch-theshold=<down>:<up> <device> to test various values for the touch threshold before committing them to a hwdb.

Thanks for the info!

Out of curiosity is this architecturally the same reason that desktop icons don't work on Wayland?

&#x200B;

>It's kinda hard to justify that work when it might not be that much more difficult get a basic port of conky to wlr_layer_shell for native wayland support.

It seems that certain conky contributors have been making a slow crawl toward separating the display backend from the rest of the source code.

https://github.com/brndnmtthws/conky/issues/56

But while we wait for this change, a wayland fork will likely be somewhat difficult.

>Plus then you could call the wayland fork "wonky".

However calling "wonky" might just be incentive enough.

I am using Kitty.

the only thing that bothers me is this: I get errors about the terminal being unknown or opening the terminal failing when sshing into a different computer.

But the rest is great!…

Sway is a port of i3's logic for organizing windows, which uses a tree instead of the dynamic stack. As far as I know, no project currently exists bringing dwm logic to wayland, but I could be mistaken.

I don't recommend trying to shoe-horn dynamic window management into an explicit window manager. It can be done, since Sway supports a powerful IPC compatible with i3, so if you find an i3-msg or i3-ipc script which claims to do what you want, it may be worth giving it a try.

Things don't appear to be moving but fwiw:

https://symless.com/synergy/roadmap

This roadmap is a sneak peek at what's coming in the next major version of Synergy.

Wayland Support

There's a new Linux display manager that is set to replace Xorg/X11, which has been the defacto Linux desktop manager for as long as we can remember! Wayland is very similar to Xorg/X11, in terms of the API, but sadly is incompatible with Synergy. It is possible to switch between Xorg/X11 and Wayland on most Linux distros, but since Wayland is the way forward and Xorg/X11 is being phased out, we are committed to adding official Wayland support.

Maybe Pixeluvo -- It's 35$ but basic functions are easy.

https://store.steampowered.com/app/314500/Pixeluvo/

Free demo if the image isnt over a certain W x H res

http://www.pixeluvo.com

Most importantly the text tool is pretty good.

this is a recording of the bug, I couldn't use `wf-recorder` because when it's running, I can't reproduce the bug

https://asciinema.org/a/f54At2lK2ZThAHT0XVuarhbHV

This is just MPV with the OSD in a box layout, see in the manual how to configure that via script-opts/osc.conf.
You can also start in this mode via the command-line:

mpv --script-opts=osc-layout=box /path/to/video/file

I personally prefer passwordsafe aka pwsafe. https://pwsafe.org

Then

bindsym $mod+k [app_id = "^pwsafe$"] scratchpad show

I have once audited the code myself years ago and it was a project started by Bruce Schneier. https://www.schneier.com/academic/passsafe/

When it comes to security I generally prefer not to trust anything that looks fancy, it might signal deception or at least where priorities and competencies lie.

Don't use gnome-keyring for SSH keys. Consider gpg-agent's SSH key capabilities, where you can not only work with keys stored on a token/yubikey/nitrokey/etc, but also have more flexible options to manage access to the keys.

https://www.gnupg.org/documentation/manuals/gnupg/Agent-Configuration.html

...and look at the sshcontrol file with the 'confirm' flag; you can be prompted to enter a PIN each time the corresponding SSH private key is used, or give it a "time-to-live" before needing a PIN to use it again.

Aside what has already been mentioned about w3m image handling being a hack, you may want to try browsh for a weird Firefox terminal experience. It's not light, but it's as good as terminal browser can get, probably.

This is not a second monitor, but you could use scrcpy I think.

If you want to use it as a second monitor for the PC, you could create a virtual screen in sway and use vnc to show it on the tablet. (or possibly a screen recorder and stream it as a video to your device)

There's probably a more quaint way to explain it but here it goes.

They're essentially windows in i3 and sway that you can hide.

a better explanation

Ie, Torguard doesn't have an applet working with Wayland, so I have to keep it running but don't want it to stay in the foreground. I'll move it to a scratchpad where it disappears and can be brought back to the foreground.