The reason the config looks the way it does for Waybar is because it's pretty much just JSON with comments. That's why the things you don't like are there. As someone else mentioned, applying JSON syntax highlighting to the file will make it easier to read. JSON is an open standard file format that needs to be this way because it's what the parser expects. They could have use YAML, but then you'd get people complaining about the indentation rules.
If you're using treesitter in neovim, you can install the 'jsonc' language to properly support this filetype - the regular 'json' syntax will get upset with the comments. And, as far as I can see, Vim and NeoVim include jsonc filetype support by default from 8.2 / 0.6 onwards.
Rofi -> Wofi (drop in replacement) Flameshot -> grim/slurp These applications don't support wayland, we simply have to use the wayland friendly ones instead. Xwayland has limitations, usually with things like screencapture hence the flameshot issue. Technically flameshot does support wayland, but it's very shotty. Why wayland? No tearing, better multimonitor support, multi refreshrate support, better security, better vrr support ,protocols in the work for hdr, better gesture support -> 1 to 1 gestures, and prob more
Do you know how to setup 3 fingers swipe to left to navigate back to previous directory ? So far I have achieved this in libinput using multitouch app using xorg.
@@Robertass2000 Usually this should be done in the compositor implementation, which the application can then take advantage of, sadly not every compositor exposes this, so you can use things like libinput-gestures in possible combination with something like y-dotool to get this functionality.
Yo should try hyprland as your next compositor, besides it being really focused in being a pretty compositor the configuration is really easy and it's super friendly to debug errors in the config file, tho and overall in my experience it was mostly painless (besides getting used to a new window manager/compositor)
Wayland offers better multi monitor support, where each monitor can have their own resolution and refresh rate. That's the only reason I have a single monitor in X11.
The refresh rate cap you're probably talking about only happens under NVidia with vsync handled by a compositor. You can fix it by replacing the compositor vsync with the "force full composition pipeline" option in nvidia-settings for each of your monitors.
@user-bh1gf1yt8h That's interesting. It's the first time I've heard of this happening but I wouldn't be surprised. On AMD GPUs Wayland works probably just fine.
Wayland is getting better. I have been saying that for (what seems like) years. I use KDE and keep trying the Wayland session. Each time I am impressed that some things have been fixed. They are now only minor issues like a global menu widget not working with all applications. Things I could live with but the improvements associated with using Wayland are not that dramatic for what I do. I suppose Xorg has been around so long (can we really believe that Xorg has survived so long !) that every little feature and nuance has been exploited somewhere by some developer. Obviously I accept that Wayland is the future but developers need to revisit some elements of their code, it is not just a matter of the Wayland team providing a compatibility layer. Similar issue exist with Pipewire/PulseAudio and Proton/Windows of course.
Since I'm late to the party and several people have already informed you that it's JSON and is actually a part of the JavaScript programming language, I'll address the one thing everybody missed. The '/' character is a forward slash, '\' is backslash, and two forward slashes are comments in quite a few programming languages. Also, if you're reading it in Vim you can do a :setf json or :setf javascript and it will properly syntax highlight. Either works because the syntax is entirely within the real of the programming language itself and not separate, but specifically using json highlighting will be easier to read since it slightly alters the highlighting rules.
One thing I know wayland does better than xorg is dealing with multiple monitors of different pixel densities. I'm an xmonad guy, and my work is going back to being a hybrid situation. The monitors they're providing are 32 inch 4k. I'm really wondering how I'm going to manage dealing with a high density monitor and a regular monitor. My fallback plan is to either use Gnome, or a single monitor.
Been using Sway on and off, especially due to nwg-shell, a GTK3 shell on top of it., made by an old Archlabs friend (Piotr). That part is great, but for instance some software just behaves awkwardly in Wayland, so it also effects my ux with Sway.
Good video, but I would like to note that sway cannot set the wallpaper by itself, it uses the swaybg program and the output command in the config is passed to the swaybg program.
BTW I would like you take a shot on Qtile under Wayland too. Because I am on X11 and someday have to switch to Wayland. Sorry if my comments aren't focused on Sway. Because I have no experience with it.
@@bahmak2003 I didn't say I want sway or i3. I am interested into Qtile and would like to see him trying it out on Wayland. He wants to do stuff with Qtile in the future and said this in the video too.
The Sway config file is in JSON. It's not a "language" but a "structured data syntax." It's really easy to store data that will be used dynamically in this way. The { braces } must surround every data object. [ Brackets ] surround a list and, like everywhere else, " quotes " surround strings. The module labels are strings. The braces inside format strings: "static text {dynamic_value}" are escape characters used to insert variables, extremely common, idiomatic Linux shell syntax.
Yeah, in fact you pretty much have to. If you want to run any applications that weren't strictly made with Wayland in mind, they pretty much just run in X inside of Wayland using XWayland.
I like you videos. My only critic is that you speak softly and slowly. I personally can't watch your videos without changing the speed to x1.5. This is just my opinion please do not take it personally.
Huh? They save untold amounts of time compared to traditional stacking wms. It pretty much the complete opposite of wasting time. It’s more efficient and productive
Want more Linux content? Follow me on Mastodon: fosstodon.org/@thelinuxcast
The reason the config looks the way it does for Waybar is because it's pretty much just JSON with comments. That's why the things you don't like are there. As someone else mentioned, applying JSON syntax highlighting to the file will make it easier to read.
JSON is an open standard file format that needs to be this way because it's what the parser expects. They could have use YAML, but then you'd get people complaining about the indentation rules.
If you're using treesitter in neovim, you can install the 'jsonc' language to properly support this filetype - the regular 'json' syntax will get upset with the comments. And, as far as I can see, Vim and NeoVim include jsonc filetype support by default from 8.2 / 0.6 onwards.
Toml would be nice.
The config should be mroe readable with a JSON LSP enabled and you can use JSONQ to navigate it in a friendly way! Love the vids!
"Depreciated" and"deprecated" are not the same thing.
Rofi -> Wofi (drop in replacement)
Flameshot -> grim/slurp
These applications don't support wayland, we simply have to use the wayland friendly ones instead.
Xwayland has limitations, usually with things like screencapture hence the flameshot issue.
Technically flameshot does support wayland, but it's very shotty.
Why wayland?
No tearing, better multimonitor support, multi refreshrate support, better security, better vrr support ,protocols in the work for hdr, better gesture support -> 1 to 1 gestures, and prob more
Do you know how to setup 3 fingers swipe to left to navigate back to previous directory ? So far I have achieved this in libinput using multitouch app using xorg.
@@Robertass2000 Usually this should be done in the compositor implementation, which the application can then take advantage of, sadly not every compositor exposes this, so you can use things like libinput-gestures in possible combination with something like y-dotool to get this functionality.
what problems are you having with rofi? It works great for me on wayland.
Yo should try hyprland as your next compositor, besides it being really focused in being a pretty compositor the configuration is really easy and it's super friendly to debug errors in the config file, tho and overall in my experience it was mostly painless (besides getting used to a new window manager/compositor)
Wayland offers better multi monitor support, where each monitor can have their own resolution and refresh rate. That's the only reason I have a single monitor in X11.
Huh? I run my main 4k screen at 60Hz and my secondary 1080p screen at 180Hz in i3/X11 via xrandr.
The refresh rate cap you're probably talking about only happens under NVidia with vsync handled by a compositor. You can fix it by replacing the compositor vsync with the "force full composition pipeline" option in nvidia-settings for each of your monitors.
@user-bh1gf1yt8h That's interesting. It's the first time I've heard of this happening but I wouldn't be surprised. On AMD GPUs Wayland works probably just fine.
Wayland is getting better. I have been saying that for (what seems like) years. I use KDE and keep trying the Wayland session. Each time I am impressed that some things have been fixed. They are now only minor issues like a global menu widget not working with all applications. Things I could live with but the improvements associated with using Wayland are not that dramatic for what I do.
I suppose Xorg has been around so long (can we really believe that Xorg has survived so long !) that every little feature and nuance has been exploited somewhere by some developer. Obviously I accept that Wayland is the future but developers need to revisit some elements of their code, it is not just a matter of the Wayland team providing a compatibility layer. Similar issue exist with Pipewire/PulseAudio and Proton/Windows of course.
can you take a look at Hyprland ? it is a wayland compositor too but better
Since I'm late to the party and several people have already informed you that it's JSON and is actually a part of the JavaScript programming language, I'll address the one thing everybody missed. The '/' character is a forward slash, '\' is backslash, and two forward slashes are comments in quite a few programming languages. Also, if you're reading it in Vim you can do a :setf json or :setf javascript and it will properly syntax highlight. Either works because the syntax is entirely within the real of the programming language itself and not separate, but specifically using json highlighting will be easier to read since it slightly alters the highlighting rules.
One thing I know wayland does better than xorg is dealing with multiple monitors of different pixel densities. I'm an xmonad guy, and my work is going back to being a hybrid situation. The monitors they're providing are 32 inch 4k. I'm really wondering how I'm going to manage dealing with a high density monitor and a regular monitor. My fallback plan is to either use Gnome, or a single monitor.
Been using Sway on and off, especially due to nwg-shell, a GTK3 shell on top of it., made by an old Archlabs friend (Piotr). That part is great, but for instance some software just behaves awkwardly in Wayland, so it also effects my ux with Sway.
Thank you for sharing. What you said is very, very good. thank you! How to get your configuration？
i use wofi instead of rofi and i use flasmeshot on sway though i had to jump though some hoops
Flameshot works on Ubuntu GNOME with Wayland, but it's a bit weirder to use than on X. There is an extra step
the config file is a json file, it is a subset of JS Matt, it is a programing language
Yup, I'm aware now.
You have to find the alternative. That's the whole point !
You should check out the Hikari WM.
Last I checked you can use i3blocks in Sway. I find it much easier to configure
Good video, but I would like to note that sway cannot set the wallpaper by itself, it uses the swaybg program and the output command in the config is passed to the swaybg program.
Swaybg is a hard dependency of sway as far as I know
on fedora maybe, but on archlinux it's an additional dependency.@@TheLinuxCast
Although sway-git has swaybg-git as a hard dependency.@@TheLinuxCast
@@Федор2236 It's indeed a hard dependency on Fedora, alongside other things like Foot.
BTW I would like you take a shot on Qtile under Wayland too. Because I am on X11 and someday have to switch to Wayland.
Sorry if my comments aren't focused on Sway. Because I have no experience with it.
Try i3 if you want sway
@@bahmak2003 I didn't say I want sway or i3. I am interested into Qtile and would like to see him trying it out on Wayland. He wants to do stuff with Qtile in the future and said this in the video too.
The Sway config file is in JSON. It's not a "language" but a "structured data syntax." It's really easy to store data that will be used dynamically in this way. The { braces } must surround every data object. [ Brackets ] surround a list and, like everywhere else, " quotes " surround strings. The module labels are strings. The braces inside format strings: "static text {dynamic_value}" are escape characters used to insert variables, extremely common, idiomatic Linux shell syntax.
Waybar has json config format.
Yup, I'm aware now.
I don't like to be the one to break it for you but sway doesn't have blur AFAIK
I mean transparency. Which it does have.
can I install sway/wayland alongside xorg?
I did. I have both sway and i3 installed
Yeah, in fact you pretty much have to. If you want to run any applications that weren't strictly made with Wayland in mind, they pretty much just run in X inside of Wayland using XWayland.
Its a JSON file.
I like you videos. My only critic is that you speak softly and slowly. I personally can't watch your videos without changing the speed to x1.5. This is just my opinion please do not take it personally.
Man's never heard of JSON or Javascript before 💀💀
Man's not a developer.
@@TheLinuxCast Man is a developer
GVM.
If they did rounded corners id move to it from dwm.
That's one of my stumbling blocks also.
There’s a fork called swayfx that has rounded corner, shadows and blur.
@@firestormjupiter cool, good to know. But i'm on hyprland, and love it.
Hmm....
I use wofi and grimshot in my sway config...
Why do people waste their times with those WM?
waste what time? configuration? making things work to their liking?
gee, i wonder why.
Especially now you can have the functionality on Gnome and KDE (Bismuth).
Huh? They save untold amounts of time compared to traditional stacking wms. It pretty much the complete opposite of wasting time. It’s more efficient and productive