David Bjergaard Said:
"1. Start with the git head and roll back commits until you see the older
behavior. (This could be potentially painful depending on how far
back you have to go and how hard it is to get your 120 windows back
open)"
Instead of going one commit by one commit, you shoul
Hi Evan,
Thanks for the hints! I hope that Jim can provide us some useful
information for debugging this further.
Jim: Feel free to open an issue on github, its much more likely that I
spend time on this if its on the issue tracker. I don't mind where we
discuss the details as long as there's
I often use stump + emacsclient + slime. What happens is that I connect
to stump via slime/swank, and whenever the hang occurs I switch to a
virtual terminal, attach to the running emacs server (so make sure that
was running before hand) and then switch the sldb buffer.
On 11/12/2014 06:12 PM, Dav
Hi Jim,
I have to admit, I've never considered the magnitude of the number of
windows your trying to manage when writing code for StumpWM. That being
said I haven't written much of it, so hopefully we can sort things out.
There are two options:
1. Start with the git head and roll back commits un
1) My apologies about the confidentiality notice; we're still sorting
out our free-software contribution infrastructure.
2) I lost a little clarity in editing: My entire UI hangs, and as far as
I can tell, all keyboard events are lost to all applications, it was
just particularly easy for me to ve
