rustic-compile always prompts for compile command

[holgerschurig]

Experience behavior

The compile method of Rustic differs to the built-in one: it is always interactively prompting for a compile-command, no matter if it's called interactively or programmatically.

Example 1:

(rustic-compile "cargo build")

Here I provided my own compile command, and I expect the compilation to start immediately. But it doesn't, I'm getting needlessly asked for a compile-command. This makes (rustic-compile ...) unusable for scripting in Elisp.

Example 2:

(let ((compilation-read-command nil))
 (rustic-compile "cargo build"))

Even that generates a prompt for the interactive command.

Expected Behavior

Contrast this with

(compile "cargo build")

which doesn't prompt at all and just does what it is called to do: compile my source. That is: the provided optional argument overrides the variable compile-command, and makes it not prompt. The "not prompting" btw also happens when compilation-read-command is t.

Version of rustic-mode

This is on rustic-mode HEAD d765680

[holgerschurig]

Oh, as brotzeit seems to be MIA, I'll open this issue at the fork.