window-live-p nil error on C-x b sometimes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. With nav open, press C-x b in some buffer.

What is the expected output? What do you see instead?
Sometimes it says window-live-p nil. I think it only happens in Follow mode, 
but I'm not sure.

Original issue reported on code.google.com by issac.tr...@gmail.com on 24 Aug 2009 at 11:43

[GoogleCodeExporter]

Has this issues been corrected by using the timer functions in follow mode 
instead of
the hooks. 

This was the main problem of using all those hooks. That sometimes nav/emacs is
culling frames that are not there or not update-able.

Original comment by matthew....@gmail.com on 31 Aug 2009 at 5:59

[GoogleCodeExporter]

I'm not sure since I haven't been using follow mode lately. We can close the 
bug if you 
have been using it and haven't been having this problem. I'll file it again if 
I encounter it 
again.

Original comment by issac.tr...@gmail.com on 1 Sep 2009 at 7:09

[GoogleCodeExporter]

I have this issue, and it can be reproduced always with following steps:
1.runemacs to open a file
2.M-x nav
3.b nav to buffers
4.select a buffer to show
5.C-x 1 to close the nav window

Then return error: Wrong type argument: window-live-p, nil
After this, try C-x b to change buffer will return same error above, and M-x 
get the 
error too. 
The buffer --(nav)-- Buffer Mode can not be killed by C-x k. It must be changed 
to 
*nav* buffer with b again and then it can be killed by C-x k.This is just a 
work around 
for this issue, please help to investigate, Thanks.

Original comment by z.lag...@gmail.com on 2 Jan 2010 at 1:06

[GoogleCodeExporter]

I can reproduce this by following z.laguna's instructions above. Would love a 
fix!

Original comment by chris.se...@gmail.com on 22 Nov 2010 at 11:16

[GoogleCodeExporter]

Hi, thanks for reminding me about this. Nothing I've tried has gotten rid of 
this bug, but I'll keep looking.

Original comment by issac.tr...@gmail.com on 28 Nov 2010 at 6:47

[GoogleCodeExporter]

I changed nav to no longer have any mode except the simple filesystem 
navigation mode, and to no longer change the window layout when it starts. I 
haven't seen any window issues since making these changes, so I'm marking this 
as fixed. Let me know if you see any more problems like this though.

Original comment by issac.tr...@gmail.com on 26 Dec 2010 at 9:10

• Changed state: Fixed