patches VS dwm-flexipatch

I am trying to setup my workspaces for stumpwm, but am running into a wall due to not being able to find much documentation, is there is even support, for a few things I want to do. For some background, I am coming from dwm which I have used for a few years and even forked a few times. In dwm I had a rather simple, but extremely useful, setup where I would store specific types of programs on specific tags. I was able to figure out getting this done in stumpwm and it working just fine. The main issue with this portion of my workspace setup is that the Default workspace still exists. I have tried to figure out how to delete it, but cannot. I know how to rename it, so I could just do that and use it for my terminals, but the issue arises where I have no idea how to change it from the default stacking layout to the dynamic one. Any advice? Additionally, is there a way to get something like dwm's fakefullscreen?

I would like to add the statuscmd (for dwmblocks) feature to my dwm build. I tried this patch (from the suckless website) and this one, from u/bakkeby's Github, which seems more pertinent to my case since I use dwmblocks. I also patched my dwmblocks build with this patch, from the suckless website.

dragcfact is a patch that depends on another patch, cfacts, that assigns a 'weight' to each client in the view area and allows you to resize them by increasing or decreasing the weight of a given client. Yes, in the case of the tile layout that does allow for 'vertical' resizing.

Another way you could achieve this is via floatpos. One way I use this is to toggle tiled windows to become floating and take up 80% of the screen, which gives a kind of semi-fullscreen mode which is kind of nice.

I don't know what they are refering to, but the swallowing that has become popularized is not what that screenshot shows. The functionality is taken from Plan9's window manager, rio. When you launch, say, firefox from a terminal on non-swallowing window managers the terminal just sits there and the window is spawned on it's own. With swallowing, the terminal swallows the window in that the newly spawn windows takes up the window that is the terminal until it exists at which point the terminal window is restored. I can not an example of this in video, but there are patches to implement this into dwm such as rio draw/swallow

dwm-desktop_icons-6.2.diff - hardcoded to not manage windows that have the window type of _NET_WM_WINDOW_TYPE_DESKTOP, for programs that provide desktop icons as an example, and

I'm not really knowledgeable with dwm but googling around I found this thread where someone linked this GitHub repo, which aims to combine different fullscreen patches so they can work together.

I've applied the barmodules patch with the hope of controlling multiple status segments via IPC.

and i would recommend to use dwm-flexipatch, it makes the hole patching process very easy, and you can try out all the patches...

I just wanted to add that if anyone is experiencing this issue and using dwm-flexipatch then enabling the patch BAR_NO_COLOR_EMOJI_PATCH may solve the issue.

a lot of functionality can be added with patches, but you have to try and juggle those all yourself (and work out any conflicts between them yourself) - there are some projects like dwm-flexipatch to try and make it easier to deal with them, but it's way more trouble than I am interested in

To better understand how statuscmd works, I took a step back and decided to try some experimentation before patching my own build: I compiled dwm-flexipatch (obviously with BAR_DWMBLOCKS_PATCH and BAR_STATUSCMD_PATCH set to 1), and tried it with my patched dwmblocks and modified one of my statusbar scripts accordingly for testing purpose:

https://github.com/bakkeby/dwm-flexipatch https://github.com/bakkeby/st-flexipatch

How easy is to configure and build suckless software like DWM? (more specifically, building DWM using flexipatch

I don't think I ever made a standalone patch for this, but you can derive what needs to be changed if you grep the dwm-flexipatch code base for PERTAG_VANITYGAPS_PATCH and have a look at what the changes are.

I like and use dwm but it was becoming an overkill for me to mix and match patches, plus updating of dwm from git, I started using dwm-flexipatch from bakkeby, which I suggest you to try. He's incorporated many patches - all the ones I needed where there, which can be enabled/disabled very easily. A drawback is the config.h file: It's a bit intimidating at first, because it includes the possible options of all patches, enabled or not.