-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upcoming changes in run-command #3
Comments
Some documentation about the next version is up: https://bard.github.io/emacs-run-command |
I will try remove usages of the internal functions and make code of the recipes more easily where can, but most of the recipes from this repo couldn't be more easily, so think the cookbook from your repo is an awesome idea! and link to this repo is superfluous. Thanks for last changes, i think it cool! |
if you think, that I closed the your remarks, then close this issue Good Luck! |
I guess so, but only had a quick glance, so it's up to you. One thing you might want to keep in mind is that one of the term modes (either |
Thought I'd give you a heads-up about changes in the next version of run-command, as they might impact compatibility with this collection.
Recipes will support an optional
:runner
property pointing to runner function; the runner function configures the buffer where the command runs to (among other things) select the major mode, such asterm-mode
,compilation-mode
etc. When the recipe doesn't have a:runner
property, the value of therun-command-default-runner
variable is used instead.There will be no
run-command--run-compile
,run-command--run-term
, andrun-command--run-vterm
functions anymore. (As you might know, functions and variables prefixed with double hyphen are considered internals and can change or disappear at any time.)The "lisp function" experiment will almost certainly be retired.
Finally, some of the recipes currently featured as examples might become part of the package; there may be overlap but there should be no danger of name conflict. (Initially I considered pointing to this package, but the implementations here seem quite a bit heavier on code than how I originally envisioned recipes, as lightweight and mostly data, to allow understanding and hacking by people who know little elisp.)
The text was updated successfully, but these errors were encountered: