Note that this would be very easy to add to codewise code, as the database already contains this info from ctags (file name, regexp pattern for the line of the definition) On May 27, 2012 6:23 PM, "Terry Brown" <[email protected]> wrote:
> On Sun, 27 May 2012 05:37:16 -0500 > "Edward K. Ream" <[email protected]> wrote: > > > Rather than create nifty web pages that almost nobody will use, > > I disagree that nobody would use them. I constantly jump around the > HTML hyperlinked API docs. for Qt when I'm coding PyQt. Same for other > libraries I use - for API reference I don't think Leo's tree view can > compete with the convenience of web-pages and wouldn't expect it too. > For example Qt's docs. show not just the list of functions a class has, > but their parameters and return types as well, in one compact list. > > > wouldn't it be good to have a find-def command (with ctrl-click > > support) that would do the hyperlinking in Leo? It shouldn't be too > > hard: create an auto-completion-like popup if there are multiple > > possibilities. > > Yes, it would be excellent, to me not as an alternative to the above, > but as an additional tool. Emacs has something like that using ctags > where it can find the definition of the thing at the cursor, and it was > extremely useful. > > Cheers -Terry > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/leo-editor?hl=en. > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
