I use to use Awesome, but I got tied of having to fix Lua scripts during major updates. I have since switched to using herbstluftwm, which I like due to it being lightweight, easily customizable via a shell script or be done on the fly with herbstclient.
Not really, I didn’t really use a whole lot of widgets. I usually like to keep my workspaces minimal. My setup is mainly a panel, (Lemonbar) on the top part of my screen and a wallpaper. I also use pywal to adjust the color scheme used by Herbstluftwm, Lemonbar, and my terminal based on my current wallpaper.
(Yes I did put that tag in floating mode for that screenshot, but normally I have them in tiling mode, usually with 1-2 frames so I can have different tiling rules in effect so some windows will tile horizontally while others tile vertically etc…)
And if that description sounds great to you, but herbstluftwm seems a bit too unusual, then I can recommend bspwm.
(I don’t think they’re forks of each other, but they’re really similar in a lot of ways…)
I have not tested bspwm, but I have seen it come up on occasion under various unixporn communities. I take it you use it, or just know of it?
I don’t know if herbstluftwm is really a fork of anyone WM but it does heavely borrow from i3, musca, xmonad, and wmii. So it wouldn’t suprise me that there are other WMs out there that is similar.
The FAQ of herbstluftwm says it’s not a fork of anything. And the first commits of bspwm look like that was written from scratch, too. (Yep, I actually spent a fair amount researching that, because it really bothers me how similar they are without being forks.)
And I have used bspwm in the past. It’s been a major contributor to my current workflow, by being so limited that I didn’t believe it: You couldn’t minimize windows in bspwm. It just didn’t have that feature.
So, when I looked up what the heck that’s about, it said to just move the window to a different workspace instead.
That was when I stopped treating workspaces as individual compartments for different topics and instead started grouping multiple workspaces together with 1 or 2 windows per workspace, which just works a lot better for me. In a way, it takes out one layer of complexity by never minimizing windows.
The FAQ of herbstluftwm says it’s not a fork of anything. And the first commits of bspwm look like that was written from scratch, too. (Yep, I actually spent a fair amount researching that, because it really bothers me how similar they are without being forks.)
Yeah after making that post I checked the FAQ as well as I thought there was something there about it and was too tired to update my comment. I have no issues with FLOSS projects borrowing ideas from other FLOSS projects, IMO within the FLOSS world imitation is the best form of flattery :winking face:
And I have used bspwm in the past. It’s been a major contributor to my current workflow, by being so limited that I didn’t believe it: You couldn’t minimize windows in bspwm. It just didn’t have that feature. So, when I looked up what the heck that’s about, it said to just move the window to a different workspace instead.
Yeah herbstluftwm has a similar limitation, it actually seems pretty common for the tiling WMs that I have seen. Although there is a script for herbstluftwm that adds a hacky way to do this by creating a virtual monitor that you can put appliacions on then show and hide it. I don’t use that but it exists.
That was when I stopped treating workspaces as individual compartments for different topics and instead started grouping multiple workspaces together with 1 or 2 windows per workspace, which just works a lot better for me. In a way, it takes out one layer of complexity by never minimizing windows.
That is similar to how I work, but I have a few dedicated tags (workspaces) for web browsing, IM+Chat apps, Email that has predefined layouts. Everything else is kind of fair game use.
I use to use Awesome, but I got tied of having to fix Lua scripts during major updates. I have since switched to using herbstluftwm, which I like due to it being lightweight, easily customizable via a shell script or be done on the fly with
herbstclient.do you miss any functioality from
awesomeafter switching toherbstluftwm? Stuff like widgets etc?Not really, I didn’t really use a whole lot of widgets. I usually like to keep my workspaces minimal. My setup is mainly a panel, (Lemonbar) on the top part of my screen and a wallpaper. I also use pywal to adjust the color scheme used by Herbstluftwm, Lemonbar, and my terminal based on my current wallpaper.
(Yes I did put that tag in floating mode for that screenshot, but normally I have them in tiling mode, usually with 1-2 frames so I can have different tiling rules in effect so some windows will tile horizontally while others tile vertically etc…)
Dang that’s pretty.
Thanks!
And if that description sounds great to you, but herbstluftwm seems a bit too unusual, then I can recommend bspwm.
(I don’t think they’re forks of each other, but they’re really similar in a lot of ways…)
I have not tested bspwm, but I have seen it come up on occasion under various unixporn communities. I take it you use it, or just know of it?
I don’t know if herbstluftwm is really a fork of anyone WM but it does heavely borrow from i3, musca, xmonad, and wmii. So it wouldn’t suprise me that there are other WMs out there that is similar.
The FAQ of herbstluftwm says it’s not a fork of anything. And the first commits of bspwm look like that was written from scratch, too. (Yep, I actually spent a fair amount researching that, because it really bothers me how similar they are without being forks.)
And I have used bspwm in the past. It’s been a major contributor to my current workflow, by being so limited that I didn’t believe it: You couldn’t minimize windows in bspwm. It just didn’t have that feature. So, when I looked up what the heck that’s about, it said to just move the window to a different workspace instead.
That was when I stopped treating workspaces as individual compartments for different topics and instead started grouping multiple workspaces together with 1 or 2 windows per workspace, which just works a lot better for me. In a way, it takes out one layer of complexity by never minimizing windows.
deleted by creator
Yeah after making that post I checked the FAQ as well as I thought there was something there about it and was too tired to update my comment. I have no issues with FLOSS projects borrowing ideas from other FLOSS projects, IMO within the FLOSS world imitation is the best form of flattery :winking face:
Yeah herbstluftwm has a similar limitation, it actually seems pretty common for the tiling WMs that I have seen. Although there is a script for herbstluftwm that adds a hacky way to do this by creating a virtual monitor that you can put appliacions on then show and hide it. I don’t use that but it exists.
That is similar to how I work, but I have a few dedicated tags (workspaces) for web browsing, IM+Chat apps, Email that has predefined layouts. Everything else is kind of fair game use.