dail8859 / NotepadNext

A cross-platform, reimplementation of Notepad++

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Run tools

SimLV opened this issue · comments

commented

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

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?

commented

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

commented

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.

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.