Zeioth
Zeioth
@Cliffback woah that was fast thanks!! I've tested the PR: ## Manual testing Spring projects now display application taks.  Our `/examples/bau/gradle` test show user registered tasks correctly too. ...
It would be important we only run `gradle --list` after checking a gradle file do indeed exist. The reason is [we check for all build automation tools](https://github.com/Zeioth/compiler.nvim/blob/cb14acd32ba9ea09d01bbe3493aefdc59b68965c/lua/compiler/utils-bau.lua#L265) of the project,...
If at least one of the files `gradlew`, `build.gradle.kts`, or `build.gradle` is present, then we can then do `gradle --list`.
The PR should be a single function. I'm gonna try to refactor it when I have time.
Thank you for the good PR!! It's ok to hardcode the commands as you are doing, as there is nothing to parse. ## TODOS: * `bau-utils`: Let's also add the...
Hey @aaronmcadam I realize, and what you say makes total sense. It's not trivial to achieve though, as we use `overseer.nvim` as task runner. I don't think [the orchestrator strategy](https://github.com/stevearc/overseer.nvim/blob/master/doc/strategies.md#orchestratoropts)...
Now that I remember: this was the original behavior of this plugin actually. The change has been upstream on overseer in how it order orchestrated tasks. I'm gonna ask Steve....
PR sent, waiting for feedback. https://github.com/stevearc/overseer.nvim/pull/299
Alternative approach added to overseer: ```lua -- define the componen `custom_tasklist`. -- when a task start, auto open the tasklist and focus the first child. require("overseer").register_alias("custom_tasklist", { "default", { "open_output",...
I've been testing the solution and I like it but there is a problem I'm not sure it has solution: * Every time the user run `:MarkmapWatch`, it spawns a...