#i3wm — Public Fediverse posts

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?

I think I need more differences between the configurations of my work and home PC . Right now, I am using same i3wm config, same Emacs config (which is very easy thanks to NixOS). The only differences are the wallpaper and color scheme (and some set of the applications).

While this is convenient, I feel that it blurs the line between using computer at home and using computer at work, which is not healthy...

#nixos #worklifebalance #emacs #i3wm

I think I need more differences between the configurations of my work and home PC . Right now, I am using same i3wm config, same Emacs config (which is very easy thanks to NixOS). The only differences are the wallpaper and color scheme (and some set of the applications).

While this is convenient, I feel that it blurs the line between using computer at home and using computer at work, which is not healthy...

#nixos #worklifebalance #emacs #i3wm

I think I need more differences between the configurations of my work and home PC . Right now, I am using same i3wm config, same Emacs config (which is very easy thanks to NixOS). The only differences are the wallpaper and color scheme (and some set of the applications).

While this is convenient, I feel that it blurs the line between using computer at home and using computer at work, which is not healthy...

#nixos #worklifebalance #emacs #i3wm

@angrylinus @cyon

#Sway and #i3wm have the same feature (tabbed windows)

That's 95% of what I use on those machines.

On KDE, I have sway-like keybinds for moving windows around defined, but no tabs, except for programs that use them natively (like Firefox, Okular, Dolphin, etc.)

@angrylinus @cyon

#Sway and #i3wm have the same feature (tabbed windows)

That's 95% of what I use on those machines.

On KDE, I have sway-like keybinds for moving windows around defined, but no tabs, except for programs that use them natively (like Firefox, Okular, Dolphin, etc.)

@angrylinus @cyon

#Sway and #i3wm have the same feature (tabbed windows)

That's 95% of what I use on those machines.

On KDE, I have sway-like keybinds for moving windows around defined, but no tabs, except for programs that use them natively (like Firefox, Okular, Dolphin, etc.)

@angrylinus @cyon

#Sway and #i3wm have the same feature (tabbed windows)

That's 95% of what I use on those machines.

On KDE, I have sway-like keybinds for moving windows around defined, but no tabs, except for programs that use them natively (like Firefox, Okular, Dolphin, etc.)

@angrylinus @cyon

#Sway and #i3wm have the same feature (tabbed windows)

That's 95% of what I use on those machines.

On KDE, I have sway-like keybinds for moving windows around defined, but no tabs, except for programs that use them natively (like Firefox, Okular, Dolphin, etc.)

@jameshowell @guix @daviwil I did some tests few months ago. I wanted to verify how usable will be a beautiful #thinkpad X200s which I bought long time ago. Instead of having some stable system as a base I used #guixos . Before I knew nothing about Scheme (still not much more) but it wasn’t any obstacle. The whole idea is elegant and clear. During my journey I used official docs and #LLM companion (#kiro cli). This combo let me move on super fast. I am amazed by results. I like minimalistic setups so my choose were: #i3wm , #neovim , qutebrowser, pass, #NextCloud client and #aerc . I also gave a try to #emacs but I still don’t feel it. The whole setup works extremely well. Thanks to good LLM advice on structuring config files to achieve composability I was enabled to prepare different profiles for my different machines while maintaining single configurations per functionality. Now I have longer pause but in nearest time I plan to experiment with #ubuntu + guix. I hope I reach out testing phase and stary using the setup for daily basis.

@jameshowell @guix @daviwil I did some tests few months ago. I wanted to verify how usable will be a beautiful #thinkpad X200s which I bought long time ago. Instead of having some stable system as a base I used #guixos . Before I knew nothing about Scheme (still not much more) but it wasn’t any obstacle. The whole idea is elegant and clear. During my journey I used official docs and #LLM companion (#kiro cli). This combo let me move on super fast. I am amazed by results. I like minimalistic setups so my choose were: #i3wm , #neovim , qutebrowser, pass, #NextCloud client and #aerc . I also gave a try to #emacs but I still don’t feel it. The whole setup works extremely well. Thanks to good LLM advice on structuring config files to achieve composability I was enabled to prepare different profiles for my different machines while maintaining single configurations per functionality. Now I have longer pause but in nearest time I plan to experiment with #ubuntu + guix. I hope I reach out testing phase and stary using the setup for daily basis.

@jameshowell @guix @daviwil I did some tests few months ago. I wanted to verify how usable will be a beautiful #thinkpad X200s which I bought long time ago. Instead of having some stable system as a base I used #guixos . Before I knew nothing about Scheme (still not much more) but it wasn’t any obstacle. The whole idea is elegant and clear. During my journey I used official docs and #LLM companion (#kiro cli). This combo let me move on super fast. I am amazed by results. I like minimalistic setups so my choose were: #i3wm , #neovim , qutebrowser, pass, #NextCloud client and #aerc . I also gave a try to #emacs but I still don’t feel it. The whole setup works extremely well. Thanks to good LLM advice on structuring config files to achieve composability I was enabled to prepare different profiles for my different machines while maintaining single configurations per functionality. Now I have longer pause but in nearest time I plan to experiment with #ubuntu + guix. I hope I reach out testing phase and stary using the setup for daily basis.

@jameshowell @guix @daviwil I did some tests few months ago. I wanted to verify how usable will be a beautiful #thinkpad X200s which I bought long time ago. Instead of having some stable system as a base I used #guixos . Before I knew nothing about Scheme (still not much more) but it wasn’t any obstacle. The whole idea is elegant and clear. During my journey I used official docs and #LLM companion (#kiro cli). This combo let me move on super fast. I am amazed by results. I like minimalistic setups so my choose were: #i3wm , #neovim , qutebrowser, pass, #NextCloud client and #aerc . I also gave a try to #emacs but I still don’t feel it. The whole setup works extremely well. Thanks to good LLM advice on structuring config files to achieve composability I was enabled to prepare different profiles for my different machines while maintaining single configurations per functionality. Now I have longer pause but in nearest time I plan to experiment with #ubuntu + guix. I hope I reach out testing phase and stary using the setup for daily basis.

@jameshowell @guix @daviwil I did some tests few months ago. I wanted to verify how usable will be a beautiful #thinkpad X200s which I bought long time ago. Instead of having some stable system as a base I used #guixos . Before I knew nothing about Scheme (still not much more) but it wasn’t any obstacle. The whole idea is elegant and clear. During my journey I used official docs and #LLM companion (#kiro cli). This combo let me move on super fast. I am amazed by results. I like minimalistic setups so my choose were: #i3wm , #neovim , qutebrowser, pass, #NextCloud client and #aerc . I also gave a try to #emacs but I still don’t feel it. The whole setup works extremely well. Thanks to good LLM advice on structuring config files to achieve composability I was enabled to prepare different profiles for my different machines while maintaining single configurations per functionality. Now I have longer pause but in nearest time I plan to experiment with #ubuntu + guix. I hope I reach out testing phase and stary using the setup for daily basis.

I wrote this a bit back and it's been running swimmingly, as good or better than i3blocks but, at heart, simpler: https://github.com/pjz/hardbar

#zig #i3wm

I wrote this a bit back and it's been running swimmingly, as good or better than i3blocks but, at heart, simpler: https://github.com/pjz/hardbar

#zig #i3wm

I3wm config on MX is different in one of two things from the one I've been using along the years. That's why it was giving me problems.

I removed the old config, generated a new one with i3wm wizard and now it seems all good.

#linux #i3wm #mxlinux

I3wm config on MX is different in one of two things from the one I've been using along the years. That's why it was giving me problems.

I removed the old config, generated a new one with i3wm wizard and now it seems all good.

#linux #i3wm #mxlinux

I3wm config on MX is different in one of two things from the one I've been using along the years. That's why it was giving me problems.

I removed the old config, generated a new one with i3wm wizard and now it seems all good.

#linux #i3wm #mxlinux

I3wm config on MX is different in one of two things from the one I've been using along the years. That's why it was giving me problems.

I removed the old config, generated a new one with i3wm wizard and now it seems all good.

#linux #i3wm #mxlinux

Another day, another slop replacement. Just switched from i3wm to dwm. Couldn't find anything slop related in their repository.

And I love the simplicity and the compile-your-own wm mentality. Any change to the style is just a change in a header file, followed by a re-compilation. Pretty cool so far :blobcatcoffee:

#dwm #i3wm #FckLLMs #FckAI

Another day, another slop replacement. Just switched from i3wm to dwm. Couldn't find anything slop related in their repository.

And I love the simplicity and the compile-your-own wm mentality. Any change to the style is just a change in a header file, followed by a re-compilation. Pretty cool so far :blobcatcoffee:

#dwm #i3wm #FckLLMs #FckAI

Another day, another slop replacement. Just switched from i3wm to dwm. Couldn't find anything slop related in their repository.

And I love the simplicity and the compile-your-own wm mentality. Any change to the style is just a change in a header file, followed by a re-compilation. Pretty cool so far :blobcatcoffee:

#dwm #i3wm #FckLLMs #FckAI

Another day, another slop replacement. Just switched from i3wm to dwm. Couldn't find anything slop related in their repository.

And I love the simplicity and the compile-your-own wm mentality. Any change to the style is just a change in a header file, followed by a re-compilation. Pretty cool so far :blobcatcoffee:

#dwm #i3wm #FckLLMs #FckAI

Another day, another slop replacement. Just switched from i3wm to dwm. Couldn't find anything slop related in their repository.

And I love the simplicity and the compile-your-own wm mentality. Any change to the style is just a change in a header file, followed by a re-compilation. Pretty cool so far :blobcatcoffee:

#dwm #i3wm #FckLLMs #FckAI

Всё, что вы настроили в Linux, можно было не настраивать

Я использую Linux 15 лет. Ну, то есть как использую: первые года три я его настраивал, а не использовал. Это разные вещи, и мне понадобилось позорно много времени чтобы это понять. Сейчас у меня Fedora. Из коробки. С GNOME. Почти без кастомизации. Я набираю в ней код, сижу в браузере, иногда монтирую видео для внутренних демок. Всё работает. Пятнадцать лет назад я бы от такого описания плевался. Как это «из коробки»? А где i3? Где polybar? Где 400 строк .vimrc? Где кастомный скрипт на баше который при подключении второго монитора переключает раскладку DPI и температуру цвета? Ну вот, нету. И ничего не сломалось.

https://habr.com/ru/articles/1044236/

#linux #gnome #i3wm #dotfiles #fedora #продуктивность #прокрастинация #оконный_менеджер #тайлинг #окружение_рабочего_стола

Всё, что вы настроили в Linux, можно было не настраивать

Я использую Linux 15 лет. Ну, то есть как использую: первые года три я его настраивал, а не использовал. Это разные вещи, и мне понадобилось позорно много времени чтобы это понять. Сейчас у меня Fedora. Из коробки. С GNOME. Почти без кастомизации. Я набираю в ней код, сижу в браузере, иногда монтирую видео для внутренних демок. Всё работает. Пятнадцать лет назад я бы от такого описания плевался. Как это «из коробки»? А где i3? Где polybar? Где 400 строк .vimrc? Где кастомный скрипт на баше который при подключении второго монитора переключает раскладку DPI и температуру цвета? Ну вот, нету. И ничего не сломалось.

https://habr.com/ru/articles/1044236/

#linux #gnome #i3wm #dotfiles #fedora #продуктивность #прокрастинация #оконный_менеджер #тайлинг #окружение_рабочего_стола

Всё, что вы настроили в Linux, можно было не настраивать

Я использую Linux 15 лет. Ну, то есть как использую: первые года три я его настраивал, а не использовал. Это разные вещи, и мне понадобилось позорно много времени чтобы это понять. Сейчас у меня Fedora. Из коробки. С GNOME. Почти без кастомизации. Я набираю в ней код, сижу в браузере, иногда монтирую видео для внутренних демок. Всё работает. Пятнадцать лет назад я бы от такого описания плевался. Как это «из коробки»? А где i3? Где polybar? Где 400 строк .vimrc? Где кастомный скрипт на баше который при подключении второго монитора переключает раскладку DPI и температуру цвета? Ну вот, нету. И ничего не сломалось.

https://habr.com/ru/articles/1044236/

#linux #gnome #i3wm #dotfiles #fedora #продуктивность #прокрастинация #оконный_менеджер #тайлинг #окружение_рабочего_стола

• Not all Fediverse frontends have an "Alt" button.
• "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
• There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
• Not everyone in the Fediverse uses a pointing device of whichever sorts.

• Not all Fediverse frontends have an "Alt" button.
• "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
• There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
• Not everyone in the Fediverse uses a pointing device of whichever sorts.

• Not all Fediverse frontends have an "Alt" button.
• "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
• There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
• Not everyone in the Fediverse uses a pointing device of whichever sorts.

• Not all Fediverse frontends have an "Alt" button.
• "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
• There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
• Not everyone in the Fediverse uses a pointing device of whichever sorts.

• Not all Fediverse frontends have an "Alt" button.
• "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
• There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
• Not everyone in the Fediverse uses a pointing device of whichever sorts.

@Lori_Noctis I've really been loving Regolith, which is an #i3wm desktop that installs on top of Ubuntu and maybe other Debian-ish distros. Tiling window managers are a paradigm shift, a different way of managing your desktop. I love them!

@Lori_Noctis I've really been loving Regolith, which is an #i3wm desktop that installs on top of Ubuntu and maybe other Debian-ish distros. Tiling window managers are a paradigm shift, a different way of managing your desktop. I love them!

@Lori_Noctis I've really been loving Regolith, which is an #i3wm desktop that installs on top of Ubuntu and maybe other Debian-ish distros. Tiling window managers are a paradigm shift, a different way of managing your desktop. I love them!

@Lori_Noctis I've really been loving Regolith, which is an #i3wm desktop that installs on top of Ubuntu and maybe other Debian-ish distros. Tiling window managers are a paradigm shift, a different way of managing your desktop. I love them!

Jajajaja recuerdo mi pánico la primera vez que me pasó esto :blobcatpats:
#i3 #i3wm

Jajajaja recuerdo mi pánico la primera vez que me pasó esto :blobcatpats:
#i3 #i3wm

It is so cool to be able to configure #XFCE with a script via command line. It is even cooler to simply share one config file as with #i3wm or #Niri. Although i3wm is "better" as it can include a file called config.`hostname` 👍

It is so cool to be able to configure #XFCE with a script via command line. It is even cooler to simply share one config file as with #i3wm or #Niri. Although i3wm is "better" as it can include a file called config.`hostname` 👍