Thread: [cedet-semantic] Question about semantic-complete-jump(-local)
Brought to you by:
zappo
From: Arne S. <arn...@gm...> - 2010-11-04 18:24:22
|
And I have another question: How does semantic-complete-jump choose the symbol to jump to? E.g. in Python I have expressions like: self.someFunction() When the cursor is somewhere on someFunction, semantic-complete-jump will still suggest to jump to self, which is rather useless. Can I change this behaviour, to get it to suggest someFunction instead? Best regards, Arne Schmitz -- Dipl.-Inform. Arne Schmitz Phone +49 (0)241 80-21817 Computer Graphics Group Mobile +49 (0)151 29145947 RWTH Aachen University Fax +49 (0)241 80-22899 Ahornstrasse 55, 52074 Aachen, Germany http://www.rwth-graphics.de |
From: Eric M. L. <er...@si...> - 2010-11-10 23:09:35
|
On 11/04/2010 02:24 PM, Arne Schmitz wrote: > And I have another question: How does semantic-complete-jump choose the symbol to jump to? E.g. in Python I have expressions like: > > self.someFunction() > > When the cursor is somewhere on someFunction, semantic-complete-jump will still suggest to jump to self, which is rather useless. Can I change this behaviour, to get it to suggest someFunction instead? If you use: M-x semantic-analyze-current-context RET you will get a buffer that shows the interpreted prefix. If it says something like this in the buffer: Prefix: moose self "someFunction" that means if found a variable called 'self' of type moose, but has no idea what someFunction is. In this case, it will fall back to just going to wherever self is. Use: M-x semantic-analyze-debug-assist RET to identify more details about the code that is having issues. In the case of python, I suspect that analyzer support there is incomplete. Someone posted a question about imports today not working. Fixing that might help get this working for python, but it could be anything. I don't know python, so it will take a python & Emacs hacker to finish the python support. Eric |