Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

dwm

dwm.suckless.org

Post reply on HN
Print view View original

61–70 of 98 posts

Re: dwm

#61

Post by niij »

justinsaccount wrote: post #38
racingmars wrote: post #20

Earlier quoted context omitted.

Yes! Before I went all-in on desktop Linux, I was a Mac user, and MacOS definitely got virtual desktops exactly right in this regard.

They definitely did not. OS X has the same issue as a lot of other VMs. You can not simply have a single pool of workspaces and chose to view any N of them, where N is the number of monitors that you have. In OS X you can have workspaces on your left monitor, and workspaces on your right monitor, but you can't easily share the workspaces between the monitors without re-arranging them. The only WM I have used that get…

You can drag a workspace from one monitor to another in native Mac OS. With yabai you can hotkey it to send to a different one.

Re: dwm

#62

Post by eternityforest »

fouric wrote: post #22

> In contrast to ion, larswm, and wmii [...] dwm has no Lua integration, no 9P support, no shell-based configuration, no remote control, and comes without any additional tools, such as for printing the selection or warping the mouse Holy cow, some of these features seem really useful. I should look at some of those other window managers! > customized through editing its source code Yikes, this is a very bad idea. Thi…

It's suckless. Once you know them and their goals none of this is surprising.

I'm not even sure what they actually use computers for at all, it always seems like lightweight enthusiasts actually do less with tech than average people, if you don't count random tinkering and stuff they do at work.

Their goals are just... very different from most.

Re: dwm

#63

Post by raspyberr »

ognarb wrote: post #52

Just in case you thought about using Suckless/dwm: They’re doing literal torch hikes through southern Germany at their conferences, fighting online against "cultural marxism", and their mail server has the hostname "Wolfsschanze" (see: https://twitter.com/pid_eins/status/1113738766471057408 ) Source: https://twitter.com/kuschku/status/1156488420413362177

No post body was provided.

Re: dwm

#64

Post by jonaustin »

saladuh wrote: post #55
ghostpepper wrote: post #19

Earlier quoted context omitted.

I use both i3 (actually Sway) and MacOS on a daily basis and they both support this feature. I agree I could not live without it. I have never used dwm seriously, but as far as I can tell the main feature it offers over i3 is tagging. I don't really understand how this meaningfully changes the day to day workflow, and I'd love to hear what you consider to be the advantages.

No, the biggest feature of DWM is dynamic window tiling (pretty sure DWM stands for Dynamic Window Manager). Sway/i3 can be made to kinda dynamically tile with scripts, but it's much less consistent, less powerful, and hardly works. They are manual tilers and they don't try to be dynamic tilers. Personally I prefer being able to quickly toggle a dynamic window layout based on my current workflow, and switch back to m…

fwiw; for i3/sway I use this autotiling script: https://github.com/nwg-piotr/autotiling

Re: dwm

#65

Post by addicted »

tomxor wrote: post #36
fouric wrote: post #22

> In contrast to ion, larswm, and wmii [...] dwm has no Lua integration, no 9P support, no shell-based configuration, no remote control, and comes without any additional tools, such as for printing the selection or warping the mouse Holy cow, some of these features seem really useful. I should look at some of those other window managers! > customized through editing its source code Yikes, this is a very bad idea. Thi…

>> Because dwm is customized through editing its source code > Suckless tools are developed for the needs (and the benefit) of their own developers, and nobody else. Remember that. Just to flip this on it's head a bit (because different perspectives are more illuminating than crude dichotomies). One of the underlying principles they use to justify not supporting external configuration, is minimal code. The absence of…

Can reading a configuration value from a file (something that can be abstracted away in a fairly simple single function) really make code so much more complicated than hard coding that configuration value in code?

Re: dwm

#66

Post by hiptobecubic »

sbysb wrote: post #13
racingmars wrote: post #10

I've used dwm as my window manager for a couple years now, after switching from i3, and have never looked back (i3 was fine, but it had a bug that was affecting me too often--I don't even remember what now). For me, the killer feature (aside from tiling vs overlapping) is that on my three monitors, I can switch virtual desktops independently on each monitor. After being able to do this, I don't understand why every w…

This is something I have come to realize I unconsciously have gotten very dependent on - MacOS let's you swap virtual desktops for the monitor you are currently focused on without swapping any of the others. I never realized how intuitive this is until switching back to my XFCE linux installation and getting very frustrated with virtual desktops entirely. I might have to give dwm a try again on my linux machine if it…

My first real job back in 2013 gave all of the devs macbooks to work on. I never used it specifically because osx couldn't do this.

Even now, they still don't get it right and treat each monitor as its own set of desktops.

Re: dwm

#67

Post by tomxor »

addicted wrote: post #65
tomxor wrote: post #36

Earlier quoted context omitted.

>> Because dwm is customized through editing its source code > Suckless tools are developed for the needs (and the benefit) of their own developers, and nobody else. Remember that. Just to flip this on it's head a bit (because different perspectives are more illuminating than crude dichotomies). One of the underlying principles they use to justify not supporting external configuration, is minimal code. The absence of…

Can reading a configuration value from a file (something that can be abstracted away in a fairly simple single function) really make code so much more complicated than hard coding that configuration value in code?

You can probably make a small function to do it, but then it might take more than you imagine to do it robustly... then there are 1000 other "small" features like this, if you accept them all you wouldn't have a small code base any-more. They are just pretty brutal about what is and what isn't worth a line of code.

Re: dwm

#68

Post by skulk »

LargoLasskhyfv wrote: post #40
skulk wrote: post #4

The zen of dwm is endlessly browsing this list of patches and eventually adding so many that any new patches cause merge errors that take a long time to untangle: https://dwm.suckless.org/patches/

Isn't that what https://github.com/bakkeby/dwm-flexipatch is made for?

eh, perhaps, but I'd never use it. I used dwm because I loved staring at that code and modifying it to my needs, and all those preprocessor directives are frankly horrifying. I'm sure this would have been much more practical, but I stopped using dwm in the name of practicality anyways.

Re: dwm

#69

Post by seanw444 »

I tried DWM, and I think it's pretty cool. But extending the functionality through C, and the limited set of patches, kind of bothered me. I wanted to essentially DIY my own window manager, but with a language that's a bit quicker to write, and less a burden to think about.

For this, I highly recommend AwesomeWM. Been my daily driver for half a year now. I absolutely love it. It's scripted with Lua, so it's still snappy, while being easy to extend. The only downside is the *meh* documentation, but it's still usable.

Re: dwm

#70

Post by LanternLight83 »

ghostpepper wrote: post #58
sidpatil wrote: post #54

Earlier quoted context omitted.

> I have never used dwm seriously, but as far as I can tell the main feature it offers over i3 is tagging. What are you specifically referring to when you say "tagging"?

I think it was explained to me as the ability to tag certain windows with short descriptors and then assign tags or groups of tags to different displays/layouts/panes. The main reason I haven't tried it because I had already switched to Sway and gotten rid of Xorg entirely.

I think the great part is being able to assign multiple tags to a window so it appears under multiple workspaces (same toolbelt as a sticky tag, which can co-exist), and being able to assign multiple tags to a workspace ("Chat" and "Music"). The ability to toggle your music windows in and out of existence, independently of other contexts, feels more like having every window on a hotkey than switching to another entire workspace or using sticky. It abstracts your contexts out from your workspaces and allows you to preform manipulations across those sets. I don't think dwm would let you show the difference (https://en.m.wikipedia.org/wiki/Difference_set) between two tags without a patch (because why?), but if you wanted to you could.
Post reply on HN