2008/12/5 Neale Pickett [EMAIL PROTECTED]:
Neale Pickett [EMAIL PROTECTED] writes:
Would you mind sharing how you launch dwm?
It might also be helpful to share your status script. If you launch
your status script like this:
status | dwm
and status forks, the parent may not be exiting.
2008/12/5 James Turner [EMAIL PROTECTED]:
Great! Thank you for dwm-5.3. I think that it's needed to #include
signal.h, infact without it I couldn't compile on NetBSD.
#include signal.h is also required on OpenBSD.
Oh yes, I missed that. I will re-issue dwm-5.3.1 with this fix tonight.
Kind
On Fri, 5 Dec 2008 08:33:44 +
Anselm R Garbe [EMAIL PROTECTED] wrote:
2008/12/5 Neale Pickett [EMAIL PROTECTED]:
Neale Pickett [EMAIL PROTECTED] writes:
Would you mind sharing how you launch dwm?
It might also be helpful to share your status script. If you launch
your status
2008/12/5 Guillaume Quintin [EMAIL PROTECTED]:
On Fri, 5 Dec 2008 08:33:44 +
Here is my .xinitrc :
while true
do
echo `date`
sleep 1
done | dwm
A bit off-topic, but, why the echo? A simple date should do it.
--
- yiyus || JGL .
I have the same problem, although my status feed setup is nearly identical
to the one Neale shows. I use 'tail -f $XSTATUS | dwm' instead of 'dwm
$XSTATUS' because for some reason dwm always showed EOF the other way.
Anyways, my .xinitrc is simply 'exec dwm-launch' and dwm-launch does the
fifo
On Fri, 5 Dec 2008 15:52:26 +0100
yy [EMAIL PROTECTED] wrote:
2008/12/5 Guillaume Quintin [EMAIL PROTECTED]:
On Fri, 5 Dec 2008 08:33:44 +
Here is my .xinitrc :
while true
do
echo `date`
sleep 1
done | dwm
A bit off-topic, but, why the echo? A simple date
On Fri 05 Dec 2008 - 07:12AM, Marcin Cieslak wrote:
The new flag means: do not allow to change tags, and do not display tag
indicator.
I don't know about you, but I don't try to change the tags for
stalonetray very often. :) My patch also has the benefit of working
with anything with all tags
Hi, I have been thinking about this for some time, and I like dwm a
lot but I don't like it to manage all my windows, so I was wondering
if it's possible to nest it inside another manager and tell it to
handle only some windows? Please note I used this a long time ago in
the 2.x releases so I'm
