> Ok I made a feature request for THIS one.
> https://sourceforge.net/tracker/index.php?
> func=detail&aid=1841542&group_id=85796&atid=577332
>
> What about the idea of improving go-to-definition so that it use
> pydev-extensions code-analysis information (to effectively select the
> right one from the list of options) - when code analysis is available
> and has a definitive result?
>
> (and if so, it would be good to add a second go-to-definition which
> always shows the list, in case code-analysis has got it wrong...)

Actually, it should already do this... it only shows the list with the
potential name matches when it's not able to find a correct match
through the type-inference (that's used in the code-analysis).

If that's not working for you in some case, that might be a bug (note
that the code-analysis may sometimes find multiple definitions for a
given token -- in which case the list would be shown anyway).

Cheers,

Fabio

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Pydev-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pydev-users

Reply via email to