You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
What is the status of jsctags? From occasional blog posts, I gather that it is actively being used as a basis for prototyping, and that enthusiasm is still there, but available development time less so. But what about its use as development tool? Accidentally losing core functionality is somewhat worrying, especially if combined with long response times. Is there a mailing list?
Given that the main contributors seem to have a lot less time for this project than they would like to have, it would be good to have some high-level documentation (how are things supposed to work; to pick a random example: how do I run jsctags over its own sources while making sure that exports objects are handled specially?) and a discussion medium (would it be acceptable to intrude on the narcissus list?). Then many small contributions from tool users might sum up to progress (for the "I just want the tool" users;-) again?
I'm working on a patch to generate scoped tags (tags for local variables and parameters) in such a way that Vim can figure out which of those local declarations is in scope, and it would be helpful to have a community to talk to, to clear up issues arising (how to arrange a pull request, given that the patch affects the narcissus submodule as well? why is the treatment of export objects linked to the presence of package files? how do I distinguish scripts from modules, if not via the commonJS option?).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the status of jsctags? From occasional blog posts, I gather that it is actively being used as a basis for prototyping, and that enthusiasm is still there, but available development time less so. But what about its use as development tool? Accidentally losing core functionality is somewhat worrying, especially if combined with long response times. Is there a mailing list?
Given that the main contributors seem to have a lot less time for this project than they would like to have, it would be good to have some high-level documentation (how are things supposed to work; to pick a random example: how do I run jsctags over its own sources while making sure that exports objects are handled specially?) and a discussion medium (would it be acceptable to intrude on the narcissus list?). Then many small contributions from tool users might sum up to progress (for the "I just want the tool" users;-) again?
I'm working on a patch to generate scoped tags (tags for local variables and parameters) in such a way that Vim can figure out which of those local declarations is in scope, and it would be helpful to have a community to talk to, to clear up issues arising (how to arrange a pull request, given that the patch affects the narcissus submodule as well? why is the treatment of export objects linked to the presence of package files? how do I distinguish scripts from modules, if not via the commonJS option?).
The text was updated successfully, but these errors were encountered: