![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Oh it’s done by assigning the same keybind to each action.
That will likeky make my config 1000 lines long 😅
Oh it’s done by assigning the same keybind to each action.
That will likeky make my config 1000 lines long 😅
That’s just the way you write the rules being deprecated, not the functionality.
I didn’t say that it is impossible to do it, just that after I read the documentation it told me that.
Something that I couldn’t even find in the documentation was how to do several actions with one keybind, on i3 each action is separated by a comma and you can assign variables to them, for example:
$BIND $MOD+$SHFT+Mod2+KP_1 $MVTO $WS1, $WS1, $WDUNST "$WS1"
Which means:
bindsym Mod4+Shift+Mod2+KP_1 move container to WorkSpace "1", WorkSpace "1", --no-startup-id dunstify -r 33 -t 600 "$WS1"
In english that is move the focused window to workspace 1, focus workspace 1 and send a notification of the current workspace (the last one is for some visual feedback).
hyperland itself told me that, I have a terrible picture (I didn’t setup screenshots lol) of it: https://imgur.com/a/fWwmt1e
This was right before yuzu closed down btw.
and have none of the problems you mentioned.
You can move floating windows between displays with the move left/right commands? (not the move to workspace commands).
edit: Found a related issue https://github.com/hyprwm/hyprland-wiki/issues/242
Yes, I spent a while reading the documentation on how to pin workspaces to certain monitors only for hyprland to tell me that it is deprecated.
Also an issue I noticed is that you can’t move floating windows between displays with the move left/right commands, move left/right moves the floating window to the left or right of the display and no more, meaning that the window gets stuck at the border of the display and doesn’t move more.
Also I couldn’t figure out how to make hyperland run several commands in a row with one keybind, or how to filter windows with expressions, something that I do a lot on my i3config .
And my biggest issue, and this one seems to be with wayland in general is that it seems that it is impossible to set my displays to extended more, that is turn the 3 displays that I have into a single display which I use with some games.
i3 isn’t perfect either, I actually had to fork it and apply a patch that fixes and issue that I have that hasn’t been merged yet either.
I will list all my issues with sway anyway, hopefully somebody out there notices it and fixes them:
https://github.com/swaywm/sway/issues/8000
https://github.com/swaywm/sway/issues/8001
https://github.com/swaywm/sway/issues/8002
https://github.com/swaywm/sway/issues/8191
And all these bugs are the result of less than 2 days in total of use of sway, there is likely more that I haven’t run into.
I also had an issue that affected xfce4 apps, but that issue ended up being a dbus-broker
issue that only happens on wayland for some reason lol
I have a feeling I will be on i3 for many many years given all the issues that I’ve had with sway.
I use kdeconnect with this script: https://github.com/Samueru-sama/kdeconnect-any-filemanager
AppImages, which have no automated update facility, are terrible idea for software that is based on the security of the messaging syatem.
https://docs.appimage.org/packaging-guide/optional/updates.html
And if you want an example of one that self updates, ferdium.
My numbers were correct and I explained why.
Do you mind telling me the application list so I can check that myself?
because they are problematic by design. I didn’t go out of my way to cherrypick a small handful of applications that just so happened to use three different runtimes
Kinda odd, I didn’t even know it was using 3 different runtimes until very recently, I just installed the biggest applications that I had as appimages to make the comparison, and yuzu because I use that one very often lol.
EDIT: Don’t you think that on itself isn’t problematic by design?
in order to bash it.
How should I have phrased my comment so that I wasn’t bashing flatpak?
due to the huge systematic problems they have.
Such as?
I do that with appimages as they support a portable home. And that location can be moved around.
You can’t get bubblewrap sandboxing with appimages in a user friendly way though, but I think I will start working on that (yes I’m serious).
Flatpak hardcoded ~/.var
which I found a really bad decision and they had several issues opened on this which went really bad if you ask me:
https://github.com/flatpak/flatpak/issues/46
I know storage doesn’t matter these days, but another different thing is suggesting flatpak “because it keeps bloat down”.
but that can and does cause reliability and probability issues.
Flatpak and snaps have been the most broken on this. Just recently I was talking about issues that I had with yuzu on that. And more recently steam as I wanted to test something…
Also I remember you, you were the guy that didn’t reply when you gave a number that I found very odd (Basically impossible lol):
https://lemmy.ml/post/16669819/11551689
Were you guy that downvoted the comment btw?
Appimages don’t use any deduplication at all and usually package everything in the app.
Yes, doesn’t mean anything if flatpak uses way more storage…
How big is your distro right now?
I am at 4.2 GIB with my distro (artix) + 30 appimages + home. Though stuff like ~/.local/steam
is on a different partition.
They still use way more storage.
My entire distro + home + 30 appimages (which includes the equivalent flatpak applications as appimage) is 4.2 GiB
While they use more disk space than most native packages, this point is often exaggerated. Flatpak uses deduplication and shared runtimes if multiple apps use the same runtime.
4.79 GiB
with deduplication.
Worth mentioning that my entire distro with those applications included, and about 30 appimages is 4.2 GIB
total, and that includes the home btw.
I like flatpak as it helps me keep bloat down
Impossible. Like flatpak itself with 5 applications was using more storage than my entire distro with the same apps as appimages on top.
This is another issue with:
https://github.com/flatpak/flatpak/issues/46
https://github.com/flatpak/flatpak.github.io/issues/191
https://github.com/flatpak/flatpak/issues/1651
Others like valve have just ignored the issue for years, but the flatpak devs decided to argue that it doesn’t apply to them, to the point that one even mentioned modifying the spec so that they are exempt…
because the UX of using a sandboxed CLI app sucks
I think it is more because of this issue because as far as I know snaps have some level of sandbox and you can still use CLI apps as you said.
The whole plasma DE meta package on arch is 1.1 GiB. It will be lower indeed but I don’t think it is that significant? (Unless flatpak has a surprise here lol)
edit: iirc the app that really blew the overall size in that screenshot was libreoffice btw.
Feels like an OS inside an OS
It’s actually more than it, you can get to the point of having something like several different OS inside the OS because it might start having several different versions of big dependencies like mesa.
You have that option with the appimage, inkscape releases it themselves.