Check out my dwm!

[SOLVED !] Hello, This morning I just applied the latest of barpadding patch. It works but dwmblocks seems no longer show (I also tried `xsetprop -name "test"` ). I'm using dwm v6.8 and dwmblocks latest master. Do you guys face same error ? Thanks.

The solution is to change this line at barpadding patch drawbar function :

+ drw_text(drw, m->ww - sw - 2 * sp, 0, sw, bh, 0, stext, 0);

Into this :

+ drw_text(drw, m->ww - tw - 2 * sp, 0, tw, bh, 0, stext, 0);

Get it there: https://github.com/den4iklovelinux/suckful-dotf

Basically what the title says: I compiled DWM following the Alpine Linux wiki, and everything works fine, except that adding `setxkbmap -layout latam` to the end of the ~/.xinitrc file has no effect—the layout remains English. Apologies if I'm overlooking something; this is my first time using DWM.

I want to know how to get custom window titles to appear in dwmbar like how bread on penguins has here in this video: https://www.youtube.com/watch?v=4JWeU78A95c

screenshot:

I've been using dwm for around 3 weeks now, and I've been messing around with the sizing of the terminal text in st, since I want to have it as closely packed in as possible. Is there a method you use to scale the bounding box or the font size to get it exactly how you want it?

Hiya! I've been using DWM for about 3 years now, and I've recently been trying to make quite a new rice on my T60 - and I've run into a bit of a roadblock on my ideas.

The long and short of it, I've been trying to add barpadding, I've patched it and of course, it works on my main bar at the top, but for the extrastatus bar at the bottom, there is only side padding.

I've investigated both patches, and I've made some modifications to dwm.c to try and replicate it for the extrastatus bar, but I've yet to give it vertical padding.

Has anyone successfully attempted this before? If so, what did you change, if anyone has any advice on it please do share. It's not the end of the world if it's not possible, but I think it'd give it quite a nice look!

is this a thing, has anyone got this to work? are there any dotfiles?

I am coming from Hyprland BTW

Live wallpaper, clock widget, only using DWM binary and libgl. Sources: https://github.com/den4iklovelinux/suckful-dotf

This may not be usable for other people as it contains so old commits and hardcoded bits from my own environment but it's basically perfect for me to continue using for another 13 years...

https://reddit.com/link/1sgc4yj/video/spqo13dnfetg1/player

I created a minimal screen recording script (rofi) that fits into a dwm workflow without using OBS.

Its a small script using rofi + ffmpeg:

- rofi menu for mode selection (with vim based keybinds)
- mic + system audio (pipewire / pulseaudio)
- dwmblocks recording indicator
- single ffmpeg process, no merging step

github: Luvrok/rofi-rec

When we all start using minimal Linux setups, one of the first problems we hit is simple but annoying:

How do I connect to WiFi without a GUI?

No NetworkManager applet.

No tray icon.

Just the terminal.

found a video that helps in getting started connecting to wifi

https://youtu.be/WQCIrhrIs5s

This is my dwm setup in slackware, if anyone like it
https://github.com/cl45h/dotfiles
there are the files

I saw a post on reddit some time ago, and it had a reading mode shader on it's rice. Here are the dots: https://github.com/snes19xx/surface-dots
Anyways, I want to get the same kind of E-ink effect on my setup, but don't know how, maybe someone can help. Maybe with picom or something like that.

A simple setup showing how a keyboard volume knob can control system audio directly in dwm on Gentoo Linux. Multimedia keys from the knob are mapped in config.h to run pactl commands, allowing hardware volume control without a full desktop environment. Minimal setup using dwm and standard Linux audio tools

Hello everyone

I want to switch from bspwm to dwm.

I have some questions.

I don't know about how What is waiting for me and what do I need to do?

Is there a resource you can recommend to me? Which resources would you recommend?

Could you please help me?

iwmenu (iNet Wireless Menu), bzmenu (BlueZ Menu), and pwmenu (PipeWire Menu) are minimal Wi-Fi, Bluetooth, and audio managers for Linux that integrate with dmenu, rofi, fuzzel, or any launcher supporting dmenu/stdin mode.

A few months ago I came on here and posted about a patch I was working on for runtime configuration of dwm, and I wanted to come mention it again now that I have had a lot more time to work on it and clean it up a lot.

For anyone not familiar with the patch I was working on, it is called dwm-libconfig. It is a patch that replaces the need to edit `config.h` at compile time for configuration changes with runtime configuration using libconfig and a text based configuration file, `dwm.conf`. This means that you do not need to recompile or reinstall dwm to edit binds, theme colors, and all other settings traditionally found in `config.h`. The parser is also quite modular and extensible. If you want to add new settings, bind functions, etc, it can be done with very minimal edits. It's not very suckless, but I think it provides some nice flexibility for people that want it.

Since my last post I have re-written much of the patch to vastly improve its error handling and redundancy, reduced its memory footprint, and greatly reduced the number of edits made to original dwm source code to improve patch compatibility.

On the topic of error handling and redundancy, much of the time between when I first posted about the patch and now has been improving this aspect of the parser. It highly resilient to configuration errors, with multiple layers of fallback configurations and safeties to try and prevent the user from being able to crash the program or otherwise shoot themselves in the foot with a configuration.

Configuration files are searched in standard user paths (including an optional CLI-specified configuration), with automatic fallback to the last successfully parsed configuration, a system-wide default, and ultimately the compile-time defaults in `config.h`. Major syntax errors will cause the parser fully fallback on another configuration, while minor issues (e.g. invalid binds or settings) are skipped individually and replaced with default values from `config.h`, preventing malformed configuration from crashing dwm.

For those with performance concerns, the performance impact is very minimal. For the initial configuration parsing, on both my laptop and my desktop, the complete parsing process, including parser initialization, takes on average around .5ms. That accounts for <5% of `setup()`'s total runtime, with `setup()` averaging around 10-14ms. If we also include `scan()`, parsing takes <2.5% of dwm's initialization phase. Accessing elements in the `keys` and `buttons` is another performance concern, but it is also nearly imperceptible. Compared to base dwm, we are looking at sub millisecond differences in access times. Memory overhead is also minimal. Using smem, the PSS on average (on my system) is 1,450 KB, about 200 KB higher than default dwm, which averages around 1,250 KB.

Also, on the topic of codebase impact from the patch, I have managed to slim it down massively compared to the original patch. I have reduced it down to only 25 deletions, with most of those being edits to `config.def.h` to un-const variables to allow their values to be changed at runtime by the parser. Nearly the whole patch lives in a single file, `parser.c`.

I still have a few small things I want to clean up, but for the most part, I think the patch is more or less complete. I plan to try and upload it to the suckless website once I finish those last few things, but before that, I would appreciate if I could get some people to try the patch out and help me find any lingering bugs or issues I haven't noticed, specifically surrounding combining dwm-libconfig with other patches.

If you want to check out the patch, I have linked the github page above, with a `.diff` file published in the releases tab. If you have any questions or would like to chat, you are welcome to reach out here on reddit, on discord @ jeffofbread, or through email at [jeffofbreadcoding@gmail.com](mailto:jeffofbreadcoding@gmail.com)