Skip to content
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

Open
SimLV opened this issue May 9, 2024 · 4 comments
Open

Run tools #557

SimLV opened this issue May 9, 2024 · 4 comments

Comments

@SimLV
Copy link

SimLV commented May 9, 2024

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.
image

So one could either run simple git pull or run whole make process and grep some results from top menu

Describe alternatives you've considered

No response

@dail8859
Copy link
Owner

dail8859 commented May 9, 2024

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?

@SimLV
Copy link
Author

SimLV commented May 9, 2024

I think we are talking about different stuff.
I mean these (per project) menu items like "do something with current project"
They are just "exec some stuff" using QProcess
image

@SimLV
Copy link
Author

SimLV commented May 9, 2024

Lua could be useful for filtering and/or controlling the editor itself.
Like placing bookmarks and navigating between multiple files.

I.e. Now I am debugging a network code tracing it from two machines using statsd-like UDP event streams.
And I want to see a list of points in code where these events originated.
Yes it is very specific use case but not more specific than base64 encode/decode inside editor.
Such stuff should be placed into some simple plugins/snippets and lua is a good option to implement them.

@dail8859
Copy link
Owner

dail8859 commented May 9, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants