And whether you're using csh or not, you can use "env DISPLAY= bk pull".
tcsh disagrees: > setenv A B > echo $A B > env A= echo $A B > env A=X echo $A B
If you're doing it a lot, an alias or function seems indicated.
I already have a plethora of scripts unsetting DISPLAY and running bk. What I'd like to know is what the fuck is going on though.
Or go into the source and fix it so it doesn't fuck around with $DISPLAY until it's ready to use it for something.
The source of what? bk doesn't come with source. And recompiling and reinstalling X is something I wouldn't do even if I had time and authority (pun intended) to do so.
And how does "fucking around with env vars" trigger pointless locking attempts until a timeout expiration? And what if I had the source? Of course one can fix hateful software (to an extent). One can also write a brand new hateful program
from scratch. How does it make existing broken hateful software less hateful?
