Re: [dwm] HELP! I don't understand config.h or how dwm works!
On Fri, May 8, 2009 at 12:14 PM, Benjamin Conner wrote: > Hey, I'm new to the mailing lists. The subject says it all. I don't know > how to setup DWM. I want some autostart programs, some keyboard shortcuts, > and some basic stuff so I can use it. (and once I can use it, to use it well > :P) Can anyone give me some basic help to using DWM? I think most of your questions have been answered, but I'll just offer a couple more suggestions for getting started: suckless.org -- first place to start, there's a lot of good info here xbindkeys -- great utility for general purpose keyboard shortcuts xfontsel -- a utility to get the proper syntax needed for choosing different fonts (I highly recommend the terminus and dina fonts) xinitrc -- perfect for loading dwm and any other apps you wanted started automatically Google those terms and you'll be up and running in no time. Cheers
Re: [dwm] Stats script
On Sat, May 2, 2009 at 8:30 PM, Jake Todd wrote:
> I was wondering what some other dwm users were using for stats like
> memory, temperature, et cetera. Right now I'm using this for
> termperature, memory, wifi, date:
I'm lazy and use conky-cli to do most of the grunt work...my conkyrc
(below) displays the cpu frequency, cpu usage percentiles, battery or
AC status, LAN or WIFI stats depending on which is active, and the
date/time:
~$ cat .conkyrc
background no
out_to_console yes
update_interval 2
total_run_times 0
use_spacer none
TEXT
${freq 1}MHz ${cpu cpu1}%/${cpu cpu2}% :: ${if_existing
/sys/class/power_supply/BAT0/present}Bat
${battery_percent}%${else}AC${endif} :: ${if_empty ${exec ifconfig
wlan0 | grep 'inet addr:'}}${upspeed eth0}K ${downspeed
eth0}K${else}${wireless_link_qual_perc wlan0}% ${wireless_essid wlan0}
${upspeed wlan0}K ${downspeed wlan0}K${endif} :: ${time %b %d %H:%M}
...and I combine this with a startdwm script so I can reload dwm
without closing other applications:
$ cat bin/startdwm
#!/bin/sh
# A simple script to start dwm in a while loop which
# allows dwm to be killed without closing programs.
# Usage:killall dwm <-- restarts dwm
# killall startdwm<-- kills session
conky-cli | while read line; do
xsetroot -name "$line";
done | while true; do dwm > /dev/null; done;
Re: [dwm] dwm for win32 - bug.n NEW version (3.5)
On Sat, Feb 7, 2009 at 3:14 AM, A.S. Bradbury wrote: > On Sat, Feb 7, 2009 at 9:27 AM, wrote: >> I have created and uploaded a new version of bug.n (3.5). > > After soom googling, it appears that putty requires the > WM_ENTERSIZEMOVE and WM_EXITSIZEMOVE messages[1] to bracket its > resizes. It seems this has been translated into AutoHotKey commands on > the forums[2]. Is there any chance you could add such a workaround for > putty? Is there an alternative terminal you find works particularly > well with bug.n? I haven't tried bug.n myself, but I prefer the rxvt terminal under Windows (ala Cygwin). I don't know whether rxvt would behave any better, but it might be a good place to start.
Re: [dwm] screen locker
On Sat, Dec 13, 2008 at 9:57 AM, Neale Pickett wrote: > Since the list is talking about slock, now might be an appropriate time > for me to mention again my xss project: > >http://woozle.org/~neale/src/xss/ > > This provides several single-purpose programs which allow you to build a > screen locker (or just saver) with a shell script. I set mine up to > check the entered password against an md5 hash of my password: this > means there's no need for suid root. At work, it runs kinit and unlocks > on success; this has the nice property of getting me a new kerberos > ticket at the same time. > > When I mailed the list about this in April someone responded with a neat > thing called "sinac", which is a little smaller than xss, but polls, and > only replaces one of the 6 programs in my package. Some folks may > prefer it, combined with slock or xlock: > >http://lists.suckless.org/dwm/0804/5534.html Thanks for the info! I have been using xautolock until now. I'll give xss a try soon. FWIW, I tried sinac before xautolock and I found that it consumed an unusual amount of CPU resources in the range of 30-50%. Perhaps there was an incompatibility with the latest Xorg server, I'm not sure. I didn't stay with it long enough to find out.
Re: [dwm] plan for dwm
On Fri, Dec 12, 2008 at 11:23 AM, James Turner wrote: > On Fri, Dec 12, 2008 at 07:15:55PM +, Anselm R Garbe wrote: >> Hi, >> >> here is the plan: >> >> slock-1.1 will be released soon containing Ali's patch with some minor >> modifications. >> >> dwm-5.4 will also be released soon containing the transition patch >> with the proposed x property based status reporting, and Neale's spawn >> patch again, and possibly some other minor patches ;) >> >> After that 5.5 could contain a more advanced approach for multihead >> support (though I think I need to investigate further and experiment >> more into this direction, before agreeing on the final approach). It >> should also contain a cleaned up usage of the HEIGHT/WIDTH macros >> besides the reduction of the ugly "2 * c->bw" occurrences throughout >> the code (I plan to move these border deductions to resize). >> >> Then there will be something else soon as well... >> >> Kind regards, >> --Anselm > > I look forward to all the above mentioned changes, as well as this > mystery item :) > Ditto. A big thanks to Anselm and everyone else contributing to these projects.
Re: [dwm] [slock] slock doesn't like to deactivate after password entry
On Tue, Dec 9, 2008 at 1:49 PM, Thayer Williams wrote: > On Tue, Dec 9, 2008 at 4:48 AM, Anselm R Garbe wrote: >> 2008/12/9 Ali Gholami Rudi : >>> On Mon, Dec 08, 2008 at 04:00:48PM -0800, Thayer Williams wrote: >>>> I've been using slock for about two months now and, as per the >>>> subject, slock doesn't release my screen right away after a valid >>>> password entry. After inputing the password and pressing Enter, the >>>> screen remains blanked and no amount of input brings it up. I can >>>> actually see the LCD backlight flicking on and off with each >>>> subsequent keypress or mouse wiggle. >>> >>> I don't know how to handle others, but I use this patch for handling the >>> flickering problem. AFAIK turning a lamp on and off excessively >>> decreases its lifetime; that might be true for displays, too. > > Ali, thanks for that! This works great and I like the fact that I can > customise the timeout values. It's too early to say for sure, but it > also looks like your patch fixed my input issues (though I'm not sure > how that could be). I've been using it for a few hours now and > haven't encountered any problems yet. I just wanted to report that for whatever reason, Ali your patch does fix the slock unresponsiveness I mentioned in my initial post. Thanks again for that.
Re: [dwm] [slock] slock doesn't like to deactivate after password entry
On Tue, Dec 9, 2008 at 4:48 AM, Anselm R Garbe <[EMAIL PROTECTED]> wrote: > 2008/12/9 Ali Gholami Rudi <[EMAIL PROTECTED]>: >> On Mon, Dec 08, 2008 at 04:00:48PM -0800, Thayer Williams wrote: >>> I've been using slock for about two months now and, as per the >>> subject, slock doesn't release my screen right away after a valid >>> password entry. After inputing the password and pressing Enter, the >>> screen remains blanked and no amount of input brings it up. I can >>> actually see the LCD backlight flicking on and off with each >>> subsequent keypress or mouse wiggle. >> >> I don't know how to handle others, but I use this patch for handling the >> flickering problem. AFAIK turning a lamp on and off excessively >> decreases its lifetime; that might be true for displays, too. Ali, thanks for that! This works great and I like the fact that I can customise the timeout values. It's too early to say for sure, but it also looks like your patch fixed my input issues (though I'm not sure how that could be). I've been using it for a few hours now and haven't encountered any problems yet. Cheers
[dwm] [slock] slock doesn't like to deactivate after password entry
I've been using slock for about two months now and, as per the subject, slock doesn't release my screen right away after a valid password entry. After inputing the password and pressing Enter, the screen remains blanked and no amount of input brings it up. I can actually see the LCD backlight flicking on and off with each subsequent keypress or mouse wiggle. If I wait 3-5 seconds and then press a key or bump the mouse, it finally comes back on, but I do have to wait 3-5 seconds with absolutely no input activity in order for this happen. I'm sure this can't be the expected behaviour. I'm running Arch Linux with xorg-server v1.5.3 on an ATI X1400 (catalyst driver) in case that has any bearing. I normally start slock via xautolock, however I can reproduce this when starting slock manually. Haven't seen anyone else posting about this, so I thought I'd toss it out there. Cheers
Re: [dwm] patch to hide sticky indicators, and add "nofocus" windows
On Fri, Nov 21, 2008 at 10:38 AM, Jeremy Jay <[EMAIL PROTECTED]> wrote: > 2) since it's on every tag, every time i switch tags, it is the first > thing focused. I dont need to type into a system tray, so the > patch also adds a flag to designate a window as "nofocus" which > tells dwm to skip it when trying to find a window to focus. Awesome, I use trayer and would like a nofocus feature as well. I'll try this out when I get a chance. Thanks!
Re: [dwm] make setlayout toggle
On Wed, Nov 5, 2008 at 6:39 PM, Neale Pickett <[EMAIL PROTECTED]> wrote: > "Donald Chai" <[EMAIL PROTECTED]> writes: > >> The proposed change would add inconsistency, unless if people want the >> second MOD+1 to jump to the previously selected set of tags or do some >> other weird thing. > > I think that would make more sense if all available layouts were shown > at the top like the tags are. As it is they're two different beasts. I agree, to me it's comparing apples with oranges. Tags are locations (albeit virtual) and layouts are styles. > Having said that, this is such a minor issue that I don't care at all > what the default behavior is. It's just a 5 line addition to my > config.h and I'm happy to put it on the wiki or whatever. Agreed as well, I'm fine with keeping this a separate function in config.h if the consensus is against it.
Re: [dwm] make setlayout toggle
On Wed, Nov 5, 2008 at 2:38 AM, yy <[EMAIL PROTECTED]> wrote: > I have been using a bit different configuration here for some time and > am very happy with it. I don't toggle to the previous layout, but to > the floating layout. This way you avoid the confusion, and have an > easy way to go directly to any layout in no more than 2 clicks or key > strokes (in practice, setting the floating layout from tile is not the > same than setting it from monocle). I don't see any real benefit over simply pressing mod-f. I mean, if folks are that confused over their current/previous layout, they could just press the layout key for whatever mode they desire. By having a togglelayout() feature that worked for any mode, it would allow folks to quickly go to a desired mode and jump back to the previous when they're done.
Re: [dwm] make setlayout toggle
On Wed, Nov 5, 2008 at 1:39 AM, Anselm R Garbe <[EMAIL PROTECTED]> wrote: > Ok, are there any concerns making this upstream again? (Yes I know, we > had this already in earlier versions, by that time it was called > togglelayout())... There were reasons for not toggling, basically it > was confusing to toggle the layout after a long period of time, > because one forgets about what the previous layout was. I would love to see this upstream, but I don't know the history behind its removal from earlier versions so I'll defer to the long-time users.
Re: [dwm] make setlayout toggle
That did the trick, thanks! On Tue, Nov 4, 2008 at 12:31 PM, yy <[EMAIL PROTECTED]> wrote: > After a quick look, I think the last check in the first if should be > arg->v != lt[sellt^1] >
Re: [dwm] make setlayout toggle
On Tue, Nov 4, 2008 at 9:13 AM, Neale Pickett <[EMAIL PROTECTED]> wrote: > This simple modification to setlayout causes a binding to toggle if it's > already in the requested layout. > > Now Alt-M toggles in and out of Monocle, etc. I far prefer this > behavior, YMMV. This is a great idea and one I would have tried to implement if I knew C, however for me it doesn't work as expected. Upon patching dwm.c the behaviour of setlayout() remains unchanged. Mod-m activates monocle, but pressing it a second time appears to do nothing.
Re: [dwm] sswarp page may need an update
On Mon, Nov 3, 2008 at 12:34 AM, Anselm R Garbe <[EMAIL PROTECTED]> wrote: > 2008/11/2 Thayer Williams <[EMAIL PROTECTED]>: >> To the powers that be, >> >> I just noticed tonight that the swarp page shows some contradictory >> information. Namely, it lists the bin as "sswarp" and the package >> itself as SSWARP, yet the actual files swarp with a single 's'. > > Fixed. However all web pages can be fixed by anyone since we are using > a world-writable hg repository for the wiki contents, see > http://www.suckless.org/wiki.html for details. Thanks Anselm, I wasn't aware of the open policy for the wiki. I've been looking for an excuse to learn mercurial for a while now. Now I've got two! Cheers
Re: [dwm] sswarp page may need an update
On Sat, Nov 1, 2008 at 6:42 PM, <[EMAIL PROTECTED]> wrote: > Thanks for the update, $1. A member of our Support Team will take care of > this important issue. > You might sit still patiently or go for the 100 Dollars we pay for such > reports :-P Only if it's Canadian Tire money...err nevermind.
[dwm] sswarp page may need an update
To the powers that be, I just noticed tonight that the swarp page shows some contradictory information. Namely, it lists the bin as "sswarp" and the package itself as SSWARP, yet the actual files swarp with a single 's'.
Re: [dwm] Configurable app launcher for dwm...
On Thu, Oct 30, 2008 at 8:17 AM, Glyn Faulkner <[EMAIL PROTECTED]> wrote: > Hello all, > > First of all, thank you for the excellent window manager - I've been > using dwm for a couple of months now (my first foray into tiling WMs) > and I'm definitely a convert. > > Anyway, I don't know if anyone can make use of the following, but this > is a re-configurable application launcher (in the form of a three-line > shell script) I wrote for dwm, which needs to be placed somewhere in > your $PATH: > > Questions, comments and cheap abuse are always welcome. :) I just want to mention that the xbindkeys utility does this already and has the added benefit of working in any window manager. If you find yourself bouncing between window managers, xbindkeys can make your life much easier. However, this looks neat for those who want all of their bindings managed by dwm. Thanks for your contribution!
Re: [dwm] SLiM login themes for dwm users
On Wed, Oct 29, 2008 at 12:03 PM, Amit Uttamchandani <[EMAIL PROTECTED]> wrote: > On Wed, 29 Oct 2008 06:59:30 -0700 > "Thayer Williams" <[EMAIL PROTECTED]> wrote: > >> > Sorry I am not too familiar with SLIM but how to you "link" it with >> > dwm's .xinitrc? >> >> No worries! SLiM operates independent of window manager--Arch Linux >> runs it either as a daemon service or the traditional /etc/inittab >> method. Upon successful login, SLiM parses the user's ~/.xinitrc and >> executes whatever commands are present, be that dwm, Xmonad, Openbox, >> etc. Hope this helps...and there's more detailed info at the SLiM >> website: http://slim.berlios.de/ >> > > > Thanks for the reply! > > I got slim to install. I was able to use the themes and have them > display properly using the artwiz fonts. However, I can't seem to login > with it. I get an error "Unable to parse login file" or somewhere along > those lines. > > I have changed the following in /etc/slim.conf: > > #login_cmd exec /bin/bash -login /etc/X11/Xsession %session > login_cmd exex /bin/bash -login ~/.xinitrc %session > > #sessionsstartxfce4,openbox,ion3,icewm,wmaker,blackbox > sessionsdwm > > Am I doing something wrong here? > > I am using debian lenny by the way. What does your ~/.xinitrc file contain? I can't speak for debian, having not used it for several years. Your best bet is to consult the debian forums though; I'm sure there are several SLIM users within that community.
Re: [dwm] SLiM login themes for dwm users
On Wed, Oct 29, 2008 at 12:16 AM, Amit Uttamchandani <[EMAIL PROTECTED]> wrote: > On Tue, 28 Oct 2008 20:16:56 -0700 > "Thayer Williams" <[EMAIL PROTECTED]> wrote: > >> For those interested, I have made an 8-pack of SLiM login manager >> themes for dwm users. >> >> Details and previews can be found here: >> http://bbs.archlinux.org/viewtopic.php?id=57963 > > Sorry I am not too familiar with SLIM but how to you "link" it with > dwm's .xinitrc? No worries! SLiM operates independent of window manager--Arch Linux runs it either as a daemon service or the traditional /etc/inittab method. Upon successful login, SLiM parses the user's ~/.xinitrc and executes whatever commands are present, be that dwm, Xmonad, Openbox, etc. Hope this helps...and there's more detailed info at the SLiM website: http://slim.berlios.de/
[dwm] SLiM login themes for dwm users
For those interested, I have made an 8-pack of SLiM login manager themes for dwm users. Details and previews can be found here: http://bbs.archlinux.org/viewtopic.php?id=57963 Files can be gotten here: http://cinderwick.ca/files/dwm/dwm-slim-themes-1.0.tar.gz Last, but not least a 6-pack of wallpapers can be grabbed here: http://bbs.archlinux.org/viewtopic.php?id=57768 Cheers, Thayer
Re: [dwm] Can dwm ignore tray utilities out of the box?
On Sat, Oct 25, 2008 at 11:02 AM, Anselm R Garbe <[EMAIL PROTECTED]> wrote: > You should define some junk tag and tag such clients accordingly in > some rule, then you could avoid binding any keybinding to this junk > tag that you would never see them, except from clicking the tag. > > HTH, > Anselm Thanks Anselm, that's what I ended up doing.
[dwm] Re: Can dwm ignore tray utilities out of the box?
nOn Fri, Oct 24, 2008 at 9:58 PM, Thayer Williams <[EMAIL PROTECTED]> wrote: > Alright, so here goes my silly newb post #1... > > Is it possible to run a tray utility, such as trayer or stalonetray, > and have dwm ignore it completely? I've tried various tray settings Err, the extended rules were defined further down in the config.h. Note to self: read complete documentation before asking assistance.
[dwm] Can dwm ignore tray utilities out of the box?
Alright, so here goes my silly newb post #1...
Is it possible to run a tray utility, such as trayer or stalonetray,
and have dwm ignore it completely? I've tried various tray settings
and I also found what I thought was a relevant snippet from a recent
(v5.2) config.h. It mentioned an extended set of Rules, which I
adopted for trayer:
/* classinstancetitle tags mask
isfloating isignored isontop*/
{ "trayer", NULL, NULL, 0,True,
True, True },
But this doesn't have the expected effect so I maybe wrong about its intention.
My main goal is to make it so that trays are not selectable as a
client--I'd also like the keep the tray on top of the statusbar at all
times.
