<div dir="ltr">On Thu, Sep 20, 2012 at 5:04 AM, <span dir="ltr"><<a href="mailto:kedals0@gmail.com" target="_blank">kedals0@gmail.com</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">
toto@compaq:~/.xmonad$ ./xmonad --version<br>
<div class="im">X Error of failed request: BadAccess (attempt to access private resource denied)<br>
Major opcode of failed request: 2 (X_ChangeWindowAttributes)<br>
Serial number of failed request: 7<br>
Current serial number in output stream: 8<br></div></blockquote><div><br></div><div>--version will not work for a user-configured xmonad binary, only for the master one. That is, option checking is not done by the xmonad function but by the Main.hs of the xmonad package, which calls the xmonad function unless options such as --version are passed.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">>> toto@compaq:~$ .xmonad/xmonad-x86_64-linux --help<br>
>> X Error of failed request: BadAccess (attempt to access private<br>
>> resource denied)<br></div></div></blockquote><div><br></div><div>Likewise, neither does --help work for a custom xmonad binary, only for the main one. You should not, in general, run the custom one directly but instead let the main xmonad do so; there are no promises that the linkage between the two will remain the same (fixing the $PATH issue may require changing it, for example).</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>