Our great sponsors
-
I've switched from i3 to dwm couple days ago. I like it so far but I have one major problem: I can't come up with a comfortable workflow with my dual-monitor setup. I love the way i3 manages multi-monitor setups - single set of workspaces for all monitors, but each workspace is assigned to a monitor. I used it this way for working: Firefox on ws1, Spotify, Slack and Telegram on ws2, terminal running tmux in ws3 (where most of the stuff is done). I keep terminal workspace on the primary monitor and workspaces 1,2 on the secondary monitor - this way I can switch between my messengers and browser without having to hide my code from primary monitor. I really got used to this workflow. Now I'm trying to adapt this sort of workflow to the DWM's philosophy and probably make it better (or at least not worse). I've tried to apply single tagset patch but it has a bug which basically makes it unusable. I really want to try it out and even think of trying to fix it myself since I have some C knowledge and programming background. At this point, I don't really like the fact that I have to press mod + >/< to switch between my monitors, when on i3 I could do it by just focusing the desired workspace. Or maybe I'm just not getting the idea behind separate tags on multiple monitors? I'm sure there's a reason why it works this way. Any advice appreciated.
-
If you want the desktop experience then that makes it so that changing to a tag does so in unison across all monitors. This gives the illusion that the workspace spans all monitors while taking away some flexibility.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.