Re: [cedet-semantic] some background task is killing buffers behind my back.
Brought to you by:
zappo
From: Eric M. L. <eri...@gm...> - 2012-01-24 01:07:23
|
On 01/23/2012 01:51 PM, Nate Schley wrote: > 1st, I have to say I'm not sure if this is something solely within > CEDET, or due to something ECB is triggering. I'd appreciate any thoughts. > > Once in a while I find some background activity trying to kill buffers. > I notice this most often when emacs -- for no obvious reason -- pops up > the prompt like "file <X> modified. do you really want to kill it?" > The most aggravating symptom is when I'm ediffing files, and ediff > announces "You have killed a vital Ediff buffer---you must leave Ediff now!" > > I'm guessing something in the fine CEDET family of tools thinks *IT* has > scooped up a particular file for parsing, then parses it and attempts to > clean up after itself, not realizing its cleanup efforts exceed its > scope of work. > > I can collect and share more details, if anyone's curious. > Hi, This comes up periodically, and I went through and fixed a bunch of save-excursion defeated by set-buffer warnings, so the fix might be in bzr/trunk. If that is what you are already using, I know David fixed all the warnings in 'newtrunk', so you could try that version, and see if that fixes it. Newtrunk is a bit different to install, so be sure to ignore INSTALL (which we need to fix), and use cedet-devel-load.el instead. Good Luck Eric |