Re: [dev] mcabber (IM) and dwm?
Hi! On Sat, Jul 18, 2009 at 09:59:20AM +0200, Preben Randhol wrote: > I'm using mcabber (http://mcabber.com/) as an IM client. I'm trying to > get it to set it upso that on new messages the tag should be > highlighted. You will need to use a terminal which can set the X11 urgency hint when a bell occurs in the terminal. Using urxvt, you put the following in .Xdefaults: URxvt*urgentOnBell: true Now you have to set mcabber to bell when a message arrives: set beep_on_message = 1
Re: [dev] Why use Mercurial?
Hi! On Sun, Feb 14, 2010 at 09:32:23AM +0100, markus schnalke wrote: > Speed should be the least important argument, especially if it affect > only a specific system. Speed does matter, and it affects all systems, but i think the suckless codebases are small enough that there shouldn't be an apparent difference. > I see no point why git should be more Unix-like than mercurial. In > fact, git includes much more unrelated features and bloat than > mercurial does. git's architecture is is nicely layered so that one can use very lowlevel stuff but one also can combine it to more comfortable tools like git does it. The bloat you are talking about is mostly in small scripts that are layered above git core functionality. And mercurial does have many "bloat" and plugins in its core distribution as well. And i think every suckless-alarm-bell should ring when you merely can hear the word python ;)
Re: [dev] Why use Mercurial?
On Sun, Feb 14, 2010 at 01:24:22PM +0100, Preben Randhol wrote: > What a braindamaged statement, especially as git uses perl... I thought the irony was clearly visible... Nevertheless, git's core uses C, only a few scripts are written in perl and are getting rewritten in C.
Re: [dev] Anyone have the traditional vi working on the xterm?
On Fri, Apr 16, 2010 at 07:49:02PM +0100, Rob wrote: > Which version do you mean by original vi? > $ pacman -Qi vi > [...] > That works fine with my xterm, maybe you've got some strange Xdefaults? archlinux applies a patch to vi to increase the maximum screen size: http://repos.archlinux.org/wsvn/packages/vi/trunk/increase-tube.patch
Re: [dev] [dwm] number of tag limited?
On Thu, Aug 05, 2010 at 06:59:29PM +0200, yy wrote: > You can define as many tags as you want in your config.h file. thats actually not true: struct NumTags { char limitexceeded[LENGTH(tags) > 31 ? -1 : 1]; };
[dev] tiny dmenu patch
Dear suckless list, attached is a trivial 1 line patch that aligns the text in vertical mode on the left. This makes the output nicer on long prompts. Before: http://www.brechpunkt.de/paste/v9aYZ3DE.png After: http://www.brechpunkt.de/paste/QOruE5yA.png bye, Christoph diff -r 23bd778df432 dmenu.c --- a/dmenu.c Fri Aug 20 19:57:13 2010 +0100 +++ b/dmenu.c Fri Sep 03 21:25:06 2010 +0200 @@ -109,6 +109,7 @@ dc_drawtext(dc, text, normcol); if((curpos = dc_textnw(dc, text, cursor) + dc->h/2 - 2) < dc->w) dc_drawrect(dc, curpos, 2, 1, dc->h - 4, True, FG(dc, normcol)); + dc->x = 0; if(lines > 0) { dc->w = mw - dc->x;
Re: [dev] [dwm] zoom() monocle
On Sun, Jun 12, 2011 at 08:22:59AM -0800, Andrew Hills wrote: > [...] but that's the only purpose of zoom in monocle mode that I can > think of. The idea is to view zoom as a method to bring a window to the front of the window-stack. That way you can use your windows in a LRU manner, which saves you endless moving through the window list just to toggle between two windows.
Re: [dev] [dwm] zoom() monocle
On Sun, Jun 12, 2011 at 07:21:35PM -0400, Kurt H Maier wrote: > This can't be achieved by alternating Mod+k and Mod+j? No. Assume you have windows 1,2,3,4,5,6 with 1 being focused. Now you need window 4, so you press mod+j/k 3 times, so in between you focus 2,3. If you need 1 again, you have to mod+j/k 3 times again. It gets annoying if you have to alternate between those windows often. With the modified version, you would call zoom() after you focused window 4, which results in the stack 4,1,2,3,5,6. Now you can exchange window 4 and 1 with one call to zoom, which will result in the window stack 1,4,2,3,5,6. zoom() allows you to toggle between window 1 and 4 with one key press.