-
-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run tools #557
Comments
I really do not want to further expose Lua as a solution right now. That would then create a burden of maintaining a semi-stable API. Many editors expose a terminal/console/etc within the application. Would that make more sense so users can have an interactive shell within the application? |
Lua could be useful for filtering and/or controlling the editor itself. I.e. Now I am debugging a network code tracing it from two machines using statsd-like UDP event streams. |
I don't want to add features just because it's possible. Functionality should be best focused on core features that majority of users are likely to use for now. I do agree having ways to operate based on the current "project" would be useful but starting way overkill tends to lead to feature creep. Even with some sort of command line interface could integrate application information. |
Description
I need a way to run custom tools from editor
Describe the solution you'd like
I am going to add a Tools menu with tools.
Each tool could be managed like this.
So one could either run simple
git pull
or run wholemake
process and grep some results from top menuDescribe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: