On 06/03/2012 11:30 PM, Yagnesh Raghava Yakkala wrote:
> Hello Eric,
> "Eric M. Ludlam"<ericludlam@...> writes:
>> If it leaves it open when it is done, that would be a bug, though I
>> am not that familiar with the python specific bits. Is that what you
>> mean, or are you just seeing the file access?
> Yes, It does leave the imports open. Could you point me how to narrow down
> such a bug.?
You can use:
M-x debug-on-entry RET find-file-noselect RET
and see when it is opened. In the debug window, hit 'c' to continue.
If it gets tedious going into the debugger all the time, use:
M-x cancel-debug-on-entry RET
to remove the debugging.
You will likely get a lot of false positives, so you'll need to examine
the stack at each break to see if it is opening some python file, and
try to guess which CEDET related feature is doing the deed. Many
semantic functions open files, but have code at the end that basically
says "Did I open this? If so, kill the buffer." We'll need to check
the functions you found to make sure they are doing their job correctly.