Skip to content

Conversation

szulf
Copy link

@szulf szulf commented Aug 28, 2025

Dont think this is finished, its still missing things like displaying inline text in the same way diagnostics do(and also make it possible to turn it off in the config), or probably a few additional regex'es to make it more useful for more people, or probably some tests, but i won't have the time now to implement these now, so figured might as well send the pull request.

I still think its a good start for a feature i've seen was requested by people(and myself).
From testing for a couple days with mainly gcc/clang output it works great.

Here are some suggestions for future development if this ever gets integrated into the codebase, that i didnt have time to implement:
The fact you need to either retype the command(or press the up-arrow a few times) all the time is kind of annoying, maybe it would be nice to specify some commands in the config, and then have a picker over them.
It would be nice to somehow see the full output of the command.
It would be nice to see the returned code by the command.

instead of typing them in all the time
@szulf
Copy link
Author

szulf commented Oct 11, 2025

I don't know how, but it seems i've forgot to explain how this feature even functions
So as of now in your config you can specify make commands the syntax looks something like this

[editor.make-cmds."/home/user/full/path/to/project"]
command = "command to run"
format_type = "format" # as of now only rust, gcc, msvc, clang

then if you have the project open in helix you can type in :make or :mk to run the command, it then uses regex to parse the data and you get a picker over the errors(opened by pressing space-m)

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

Successfully merging this pull request may close these issues.

1 participant