I've updated my various scripts and language modules on BitBucket for the Textadept 5 beta. I have a Javascript module, a D module, and several other scripts in my ta-common repository. Both the javascript and the D modules depend on code found in the common repository (It has things such as comment continuation, brace matching, and other things for curly-brace languages) There's also code for dealing with XML files in there. (It is shared by both my hypertext and xml modules, which I have yet to post).
The D module depends on an external program for a lot of its autocomplete magic. If you get both working together though, you'll get autocomplete that can almost rival that of an IDE.
On Wed, Jan 18, 2012 at 10:25 AM, Brian Schott <briancsch...@gmail.com> wrote: > The D module depends on an external program for a lot of its > autocomplete magic. If you get both working together though, you'll > get autocomplete that can almost rival that of an IDE.
This strategy would also work for Go, so I'll look at your implementation. There's a very clever program called gocode (originally designed for use from Vim) which scans Go code and imports library definitions; the particular cleverness is that it spawns a daemon process so that subsequent calls do not have to rescan the project and the libraries - net result is that it's very fast once it's up and cooking.
My code is not clever enough to do caching yet, but it is so fast at lexing and doing a light parse of the source code and imports that I haven't bothered. (The implementation is multi-threaded and I've run it through Callgrind a few times) The bottleneck is still loading its output into TA. https://bitbucket.org/SirAlaran/dscanner/overview
I still have a few minor bugs in the various adeptsense functions that I've overridden, so be careful when using the D module as a reference.
If you find any problems with the callStack() function from cstyle.lua, let me know.
<steve.j.dono...@gmail.com> wrote: > On Wed, Jan 18, 2012 at 10:25 AM, Brian Schott <briancsch...@gmail.com> wrote: >> The D module depends on an external program for a lot of its >> autocomplete magic. If you get both working together though, you'll >> get autocomplete that can almost rival that of an IDE.
> This strategy would also work for Go, so I'll look at your > implementation. There's a very clever program called gocode > (originally designed for use from Vim) which scans Go code and imports > library definitions; the particular cleverness is that it spawns a > daemon process so that subsequent calls do not have to rescan the > project and the libraries - net result is that it's very fast once > it's up and cooking.
> steve d.
> -- > You received this message because you are subscribed to the Google Groups "textadept" group. > To post to this group, send email to textadept@googlegroups.com. > To unsubscribe from this group, send email to textadept+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/textadept?hl=en.
