Re: The great #! forums DWM thread

erm how do you know that?I tried it on a vanilla untouched dwm and got an error abt not being able to find file to patch at input line 4, but if I try other .diff patches they are no problem.I changed the top 3 lines of your .diff file and it worked

Re: The great #! forums DWM thread

This is a prime example of why one has to supply the exact error one is getting. "It doesn't accept it, I got errors" is no such exact description. I assumed, since you said "accept" that it couldn't apply some hunks.

The error you got instead was that it could not find dwm.c! Of course it doesn't, if your setup does not match mine and if you don't give it the path to your dwm.c...

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos TorresGithub

I am a #! forum moderator. Feel free to send me a PM with any question you have!

Re: The great #! forums DWM thread

Re: The great #! forums DWM thread

Just a quick question, since I'm currently trying to read somewhat into dwm. How do you manage your wireless connection and volume control without tray icons? Do you just run network manager and your audio control of choice as usual, but without an icon, or do you resort to alternatives like ipconfig/wpa_supplicant?

Re: The great #! forums DWM thread

This is already very specific, but I'd like to get some things straight before I even start, so some more feedback would be much appreciated: I know about remapping (I've read this) the meta-key, IE using the windows key instead of ALT. But is it possible to use a (theoretical) modkey like mod4 (super/win) as a keybind by itself, alone? I would like to bind dmenu directly to the super key, without the support of any other keys, like you do for the PRINT key which uses no modifiers either. In Gnome 3, the super key brings up the overview, equal to clicking to start button. There, I can simply start typing to launch programs, without further clicking. By default, dwm uses this:

{ MODKEY, XK_p, spawn, {.v = dmenucmd } },

Would it be sufficient to remove MODKEY and replace "XK_p" with "mod4"? Will this work at all or is a MODKEY obligatory? Would I need to define that differently? Or use xbindkey, alternatively?

Something a little more light hearted: In config.h, there's "killclient", bound to ALT-Shift-c. Is killclient what's used with CTRL+q / CTRL+w in other environments and programs or is it something completely different? Is killcient a sane way to close a program window? Also, shutting down the machine. The tutorial and config both use ALT-shift-q to quit. Do you actually use this, did you remove/rebind it or do you use a script like cb-exit? I'm not sure if I'd want a keybind to do this and thought about a solution with two bash-scripts (shutdown and reboot), which could be invoked via dmenu (so, super key + "quit" for shutdown -h now, e.g.) Or is dwm's quit command a saner way to shutdown? Is shutdown -h sane? AM I EVEN SANE?

So much curiousity here. I'm sorry. I find dwm so very intriguing that I want to avoid any frustration which would make me hate it in the first place.

Re: The great #! forums DWM thread

@Menschenkind:You could try just binding Mod4 to see if it works: you need to replace "MODKEY," with "0,""killclient" is the correct method to close any selected window. It is equivalent to clicking on the "x" symbol in the corner of an openbox window.<Alt><Shift>+q is used to kill dwm itself. This will put you back at the login screen (or back to the console).For shutdown & reboot I bind a key combo (Windows key + Shift + Escape & Grave) to (sudo) shutdown & shutdown -r, then add this to /etc/sudoers

Re: The great #! forums DWM thread

The tutorial and config both use ALT-shift-q to quit. Do you actually use this, did you remove/rebind it or do you use a script like cb-exit?

I have done it both ways. Be advised though, since cb-exit brings up a dialog window, it will get tiled into the stack so you will need to set it up to float by default in the appropriate section of config.h.

But is it possible to use a (theoretical) modkey like mod4 (super/win) as a keybind by itself, alone?

I've never tried it. The problem you will then face is that MOD4 could not be used with any other bindings.

"It does not require many words to speak the truth." - Chief Joseph, Nez Perce tribe

Re: The great #! forums DWM thread

I'm still busy reading up on customizing dwm and how to build a system around it and haven't felt secure enough to simply start compiling yet. You're all so very helpful. Thank you very much. (And thank you for the link and write-up, bronto. Just what I need right now.)

PackRat wrote:

Be advised though, since cb-exit brings up a dialog window

I only used cb-exit as an example for the mechanism – since I expected everyone around here should be familiar with it – which Head_on_a_stick outlined. My homebrew would shutdown without confirmation (dmenu + "shutdown" + enter is assertive enough, imo). I still tend to this option after your and Head's feedback.

PackRat wrote:

The problem you will then face is

not a problem at all, but expected and intended. I'd stick to ALT as modkey. But I guess I'll have to try for myself if it works at all. It seemed like an obscure idea in the first place, so I'm glad both of you found an answer at all. Thank you.

Any experience with nodm + dwm? Is there any easier way to autologin, which would make nodm redundant? Security isn't an issue; I'm the only user and this notebook doesn't leave its home, so I'd prioritize convenience and startup speed. I've seen some hacking around surrounding /bin/login too, but nodm seemed more straightforward and less intrusive in case I ever make up my mind and install LightDM along with another WM/DE.

Re: The great #! forums DWM thread

Menschenkind wrote:

Any experience with nodm + dwm? Is there any easier way to autologin, which would make nodm redundant? Security isn't an issue; I'm the only user and this notebook doesn't leave its home, so I'd prioritize convenience and startup speed. I've seen some hacking around surrounding /bin/login too, but nodm seemed more straightforward and less intrusive in case I ever make up my mind and install LightDM along with another WM/DE.

IMO Display Managers (slim) are only really needed for changing DE/WM options, I always use ~/.xinitrc:

So to put that all together, I hit Mod4 to launch dmenu, type `wifi' to launch the tray and nm-applet, then when I'm done with it, just use the `killclient' binding to kill the tray "window" and then the script kills nm-applet to clean up.(and yes, `killclient' is a sane way to close a window)

Instead of a volume control icon I use keybindings to control it and my status bar shows the volume as a %