patches VS dwm-single-tagset-6.2

Compare patches vs dwm-single-tagset-6.2 and see what are their differences.

patches

Collection of patches for dwm, st and dmenu (by bakkeby)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
patches dwm-single-tagset-6.2
94 1
268 12
- -
5.9 0.0
about 1 month ago over 2 years ago
- -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

patches

Posts with mentions or reviews of patches. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-06.

dwm-single-tagset-6.2

Posts with mentions or reviews of dwm-single-tagset-6.2. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-29.
  • What is your dwm multi-monitor workflow?
    2 projects | /r/suckless | 29 Mar 2021
    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.

What are some alternatives?

When comparing patches and dwm-single-tagset-6.2 you can also consider the following projects:

dwm-flexipatch - A dwm build with preprocessor directives to decide which patches to include during build time

chadwm - Making dwm as beautiful as possible!

dwm-directionalfocus - Adding directional focus to dwm

rofi - A huge collection of Rofi based custom Applets, Launchers & Powermenus.

dwm

xlivebg - Live wallpapers for the X window system

cwm - portable version of OpenBSD's cwm(1) window manager

kmonad - An advanced keyboard manager

batteryless-patches - Collection of batteryless gameboy game patches

dotfiles

dwm - My clone of dwm