Thread: [CEDET-devel] semantic-find-file-noselect, warnings
Brought to you by:
zappo
From: Yagnesh R. Y. <ya...@li...> - 2012-05-26 06:42:19
|
Hello list., I get to see these warnings when I start editing python files (with imports in them) --8<---------------cut here---------------start------------->8--- WARNING: semantic-find-file-noselect called for /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py while in set-auto-mode for /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py. You should call the responsible function into `mode-local-init-hook'. --8<---------------cut here---------------end--------------->8--- I don't have any fancy configuration for cedet. I am not what they mean.? could you explain about them.? -- ఎందరో మహానుభావులు అందరికి వందనములు YYR |
From: David E. <de...@ra...> - 2012-05-26 07:15:42
|
Yagnesh Raghava Yakkala writes: > I get to see these warnings when I start editing python files (with > imports in them) > > WARNING: semantic-find-file-noselect called for > /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py while in > set-auto-mode for > /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py. You should > call the responsible function into `mode-local-init-hook'. > > I don't have any fancy configuration for cedet. > I am not what they mean.? could you explain about them.? This is an internal debug message. It is most likely a bug in the python parser, but unfortunately I currently do not have time to look into this further. Just ignore it for the time being. -David |
From: Yagnesh R. Y. <ya...@li...> - 2012-05-26 07:47:31
|
Hello David, Thanks for the reply., David Engster <de...@ra...> writes: > Yagnesh Raghava Yakkala writes: >> I get to see these warnings when I start editing python files (with >> imports in them) >> >> WARNING: semantic-find-file-noselect called for >> /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py while in >> set-auto-mode for >> /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py. You should >> call the responsible function into `mode-local-init-hook'. >> >> I don't have any fancy configuration for cedet. >> I am not what they mean.? could you explain about them.? > > This is an internal debug message. It is most likely a bug in the python > parser, but unfortunately I currently do not have time to look into this > further. Just ignore it for the time being. Sure., Another question (I consider it bug), why is semantic is opening all imports.? Suppose if I open a python file containing following line. --8<---------------cut here---------------start------------->8--- import os --8<---------------cut here---------------end--------------->8--- Semantic opens "os.py" file into a new buffer background instead of just parsing. is there a I can stop this? Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు YYR |
From: Eric M. L. <eri...@gm...> - 2012-06-03 23:52:42
|
On 05/26/2012 03:48 AM, Yagnesh Raghava Yakkala wrote: > > Hello David, > Thanks for the reply., > > David Engster<de...@ra...> writes: > >> Yagnesh Raghava Yakkala writes: >>> I get to see these warnings when I start editing python files (with >>> imports in them) >>> >>> WARNING: semantic-find-file-noselect called for >>> /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py while in >>> set-auto-mode for >>> /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py. You should >>> call the responsible function into `mode-local-init-hook'. >>> >>> I don't have any fancy configuration for cedet. >>> I am not what they mean.? could you explain about them.? >> >> This is an internal debug message. It is most likely a bug in the python >> parser, but unfortunately I currently do not have time to look into this >> further. Just ignore it for the time being. > > Sure., > > Another question (I consider it bug), why is semantic is opening all imports.? > > Suppose if I open a python file containing following line. > --8<---------------cut here---------------start------------->8--- > import os > --8<---------------cut here---------------end--------------->8--- > > Semantic opens "os.py" file into a new buffer background instead of just > parsing. is there a I can stop this? Hi, Doing any kind of code analysis can be time consuming, so Semantic opens and parses your includes in idle time in preparation of doing some code analysis. It can't parse the file unless it opens it, so it will open the file for parsing. 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? Eric |
From: Yagnesh R. Y. <ya...@li...> - 2012-06-04 03:27:25
|
Hello Eric, "Eric M. Ludlam" <eri...@gm...> 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.? Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు YYR |
From: Eric M. L. <eri...@gm...> - 2012-06-04 12:04:11
|
On 06/03/2012 11:30 PM, Yagnesh Raghava Yakkala wrote: > > Hello Eric, > > "Eric M. Ludlam"<eri...@gm...> 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.? Hi, 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. Thanks Eric |