-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Jack in #363
Comments
https://github.com/clojure-vim/vim-jack-in might serve as inspiration Feedback that I received on the initial vim-jack-in, people don't like it when closing their editor closes the REPL. |
I would be willing to try to work on this—is there any particularly good launching point? Or should I just look for where the commands are run and wrap them in an "if jobs, do that, otherwise do the original synchronous thing"? |
I need to reword that. Perhaps it would be simpler to simply write a |
I think a separate command is probably the way to go. Calling |
Can I take this to mean that fireplace detects the creation of Another Q: does fireplace already have standard code for detecting lein vs. clojure-CLI (are there any others?), or would I need to write that/rip that from salve/classpath/etc.? |
Automatically created on demand.
Nothing exists for this in Fireplace. In fact I am undecided on whether this feature should live inside of Fireplace or outside of it for that reason. |
Jobs make firing off
lein repl :headless
or a similar command in the background a much less dicey prospect than when Fireplace was introduced. Evaluate adding the option to start a REPL in the background.The text was updated successfully, but these errors were encountered: