When using run-command with Helm, one can press C-u before selecting a command and edit it. Provide the same functionality when running in Ivy.

Discussion: #19

Hello, I was looking for a package which does a similar job to what offered from VSCode tasks.json file and I bumped in this package, which I believe to be the closest out there.

Though I cannot figure out how to:

• let a task take an optional command from user
• add task dependency, i.e. when running a task, this will first run the one(s) it depends on

Cheers,
Samuele

This is an exciting project, and one I know I will find useful for a number of different projects, so thanks for writing it!

I'm trying to set this up in Doom Emacs (with Selectrum), but I'm getting an error when trying out the simple example recipes.

When I try to run a command with the config below, both commands are displayed correctly in the minibuffer, but when I select either, I get the error 'Symbol's value as variable is void: command-name'. I do have sloccount installed and it works fine run manually, but the echo command example doesn't work either.

I suspect that the way I have added the examples to the run-command-recipes variable is wrong, but I'm a bit of a newbie with elisp and suspect that I somehow haven't quoted it properly (quoting still baffles me!).

Here's my configuration:

(defun run-command-recipe-example ()
  (list
   (list :command-name "say-hello"
         :command-line "echo Hello, World!")
   (when-let ((buffer-file (buffer-file-name)))
     (list :display "Count lines of code"
           :command-name "count-lines-of-code"
           :command-line (format "sloccount '%s'" buffer-file)))))

(use-package! run-command
  :config
  (setq run-command-recipes '(run-command-recipe-example))
  :bind ("C-c c" . run-command))

Any help you can give me would be much appreciated!

in the manual it says

To activate the recipe, execute M-x customize RET run-command-recipes RET and add run-command-recipe-example to the list.

What is the command to do this non-interactively?

Nice project!

I wonder if a feature could be added so that run-command execute elisp functions instead of shell ones?

It would help me avoid making regular elisp commands (along with a "package" prefix for them, which pollutes the global namespace) just for some specific projects.

Furthermore, this feature would let run-command execute elisp functions instead of just limited to executing shell commands.

The first time I run a command with run-command-runner-vterm, it works fine. But if I try running the same command again, nothing happens other than I get an error:

You cannot change major mode in vterm buffers

This seems to be because the vterm runner executes the command by setting vterm-shell and then calling vterm-mode:

But when the buffer is already using vterm-mode (as happens when re-running a command), it runs into this guard in vterm's code that prevents changing the major mode (even "changing" it from vterm-mode to vterm-mode):

https://github.com/akermu/emacs-libvterm/blob/990cc18decb489c54d16d03fd8acbfe268b98a9c/vterm.el#L757-L762

I haven't yet been able to think of a way around this other than locally disabling the "reuse buffer" feature and having it always generate a new buffer (which I believe was the behavior in older versions of run-command). Locally removing that guard in vterm's code and then re-running a command results in a different error: vterm-mode: Buffer is read-only. I suppose something, not sure what, in the code that runs when activating vterm-mode breaks when run in a read-only buffer. If I manually turn off read-only-mode in the command buffer and re-run the command again, the command re-uses the buffer as expected.

Unfortunately vterm doesn't seem to offer anything like term-exec, and the approach of setting vterm-shell is the only way I've found of having vterm run an arbitrary command.

Thanks for sharing this package.
I'd like to run some commands and compilations and them to survive an Emacs close or crash. This can accomplished with detached.el, which is an Emacs integration for crigler/dtach.

Having the corresponding run-command-runner-*-detached variants would be great for integrating both packages.

I use popper: https://github.com/karthink/popper which lets you toggle windows of "temporary" buffers

Can you make the names of the term buffers uniform so I can add that regex to my popper list? Like eglot for example: "^\\*EGLOT" - anything that starts with *EGLOT

As mentioned on reddit :)

A fully functioning term environment is an expectation of many commands. Once the term run method is sufficiently tested, it should become the default.

should do

but instead i get

pinned package at 22844ae for now