Hi,
attached are two minor cleanups. The first simplifies grabkeys()
similar to grabbuttons().
The second removes isurgent() and isoccupied(). This also means that
we need to loop over all clients only once in drawbar() now.
Cheers,
Johannes
diff -r 40cd44593977 -r 4cae21457969 dwm.c
--- a/dwm.c
Hi,
with current tip (118ea4f4f554) it seems no longer possible to focus
a client by clicking it with the left mouse button.
To reproduce move the mouse over the stack, focus the main window
using MODKEY-k, close that window e.g. using Ctrl-d. Now it is not
possible to focus the window under the
On Sat, Jun 14, 2008 at 06:31:31PM +0200, yy wrote:
2008/6/14 Johannes Hofmann [EMAIL PROTECTED]:
Hi,
with current tip (118ea4f4f554) it seems no longer possible to focus
a client by clicking it with the left mouse button.
To reproduce move the mouse over the stack, focus the main
Hi,
in tip I see a weirdness whenever a new client has exactly the size
of the screen. On my laptop e.g.
xpdf -geometry 1400x1050
makes the tiled layout go crazy. bisect shows that 941bd7c15a32
introduced this behaviour.
Cheers,
Johannes
On Thu, May 22, 2008 at 08:17:47PM +0200, Antoni Grzymala wrote:
Anselm R. Garbe dixit (2008-05-17, 16:05):
- removed reapply()
[...]
Let me know how welcome do you feel about those changes. Bug
reports are also welcome.
I'm not sure removing reapply() and forcing people to
Hello,
below is a patch that shortens grabbuttons() a bit.
Cheers,
Johannes
PS: I really appreciate the attitude to reconsider everything from
time to time - even though I'm quite satisfied with current dwm.
diff --git a/dwm.c b/dwm.c
--- a/dwm.c
+++ b/dwm.c
@@ -805,36 +805,18 @@
void
Hi,
first of all thanks a lot for dmw! Works great for me.
On Sat, Mar 15, 2008 at 03:59:35PM +0100, Anselm R. Garbe wrote:
Hi there,
I thought about all those feedback mails so far and implemented
a new setgeom function which expects a certain input syntax. I'm
not confident yet if this
On Sat, Mar 15, 2008 at 05:55:11PM -0300, Brendan MacDonell wrote:
On Sat, Mar 15, 2008 at 5:30 PM, Johannes Hofmann
[EMAIL PROTECTED] wrote:
Huh? That's a config parser in dwm!
Luckily I'd say, since otherwise we'd seem to be stuck hardcoding
values for screen sizes as 24-line functions
Hello,
thank you very much for dwm. It's simply great!
I have a minor annoyance with fltk (http://www.fltk.org) apps.
On startup, they show a white window with the default fltk window
position and size.
Only later they get moved and resized to the correct position by
dwm. This is mostly visible
