On Wed, Apr 27, 2011 at 4:15 PM, Kurt Van Dijck wrote:
> I don't understand how the while loop terminates then when dwm terminates.
xsetroot will return a nonzero exit code because the xserver is no
longer running.
--
# Kurt H Maier
On Wed, 27 Apr 2011 22:15:11 +0200
Kurt Van Dijck wrote:
> On Wed, Apr 27, 2011 at 05:51:27PM +0200, Thomas Dahms wrote:
> > Hi Andreas,
> >
> > >while xsetroot -name "$(date +"%a, %b %d %Y | %H:%M")"
> > >do
> > >sleep 20
> > >done &
> > >exec dwm
> >
> > This is even nicer as the original
On Wed, Apr 27, 2011 at 05:51:27PM +0200, Thomas Dahms wrote:
> Hi Andreas,
>
> >while xsetroot -name "$(date +"%a, %b %d %Y | %H:%M")"
> >do
> >sleep 20
> >done &
> >exec dwm
>
> This is even nicer as the original instance of .xsession is not kept
> running.
I don't understand how the while
Hi Andreas,
while xsetroot -name "$(date +"%a, %b %d %Y | %H:%M")"
do
sleep 20
done &
exec dwm
This is even nicer as the original instance of .xsession is not kept
running.
--
Thomas Dahms
On Wed, Apr 27, 2011 at 05:24:55PM +0200, am...@physik.tu-berlin.de wrote:
> > On Wed, 27 Apr 2011 13:55:08 +0200, Kurt Van Dijck
> > wrote:
> >
> >> why not just:
> >>dwm
> >>kill $statuspid
> >>
> >> I see no use in backgrounding dwm, and then waiting for it.
> >> What did I miss?
> >
>
> On Wed, 27 Apr 2011 13:55:08 +0200, Kurt Van Dijck
> wrote:
>
>> why not just:
>> dwm
>> kill $statuspid
>>
>> I see no use in backgrounding dwm, and then waiting for it.
>> What did I miss?
>
> Nothing; backgrounding dwm was left from trying a few other ways to do it.
> Thank you.
> T
On Wed, 27 Apr 2011 13:55:08 +0200, Kurt Van Dijck
wrote:
why not just:
dwm
kill $statuspid
I see no use in backgrounding dwm, and then waiting for it.
What did I miss?
Nothing; backgrounding dwm was left from trying a few other ways to do it.
Thank you.
Then it can be s
On Wed, Apr 27, 2011 at 01:20:13PM +0200, Thomas Dahms wrote:
> Hi list,
>
> The following fixes the problem:
>
> while true; do
> xsetroot -name ...
> sleep 1
> done & statuspid=$!
> dwm &
> wait $!
> kill $statuspid
why not just:
dwm
kill $statuspid
I see
Hi list,
using something like
while true; do
xsetroot -name ...
sleep 1
done &
exec dwm
in .xsession (I have to use KDM at work) as advertised in dwm's README
leaves the background loop running even after logout, which has some ugly
side effects: While not logged in, xsetr
