<div dir="ltr">On Sat, Jan 14, 2012 at 19:17, Jacek Generowicz <span dir="ltr"><<a href="mailto:jacek.generowicz@cern.ch">jacek.generowicz@cern.ch</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":3t">Don't you mean PipeReader, if we started it with spawnPipe? And<br>
presumably StdinReader would be used with the startupHook version you<br>
suggested?<br></div></blockquote><div><br></div><div>spawnPipe creates an anonymous pipe which is connected to xmobar's stdin, and corresponds to a StdinReader in xmobar.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":3t">In any case, I had neither StdinReader nor PipeReader in my xmobar<br>
config. StdinReader doesn't fix it</div></blockquote><div><br></div><div>Right, as I said, if you aren't using StdinReader then xmobar isn't reading from its stdin and therefore will not know when xmonad goes away. You need to configure a StdinReader and use %StdinReader% in the template (if it's not in the template, the StdinReader again won't be used, and xmobar won't be reading its stdin so it won't know when the connection to xmonad goes away).</div>
<div><br></div><div>Actually, if you have DynamicLog configured but no StdinReader in xmobar, I'm a little surprised that xmonad isn't eventually hanging due to a bug in the GHC runtime (which appears to have recently been found and fixed, so hopefully will be in the next GHC release).</div>
<div><br></div></div>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>wandering unix systems administrator (available) (412) 475-9364 vm/sms<br>
<br>
</div>