Support Iron.nvim and user functions for sending code to REPL #109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi folks, thanks for this package.
When I was trying to set it up for myself, I wanted to hook it into my REPL workflow that uses
iron.nvim
instead of converting to molten or slime. It seemed easy enough to add aniron.lua
runner file, but more generally it seems like the user should be able to pass any fn they want from their config. So this PR does both:If you don't want to support Iron I would at least encourage you to support functions in the
default_method
config field. It's nicer than having the user hack into the pkg tables to override the entire send() function.Thanks, eager to see what you think (fair warning I'm a lua noob and not too familiar with either quarto-nvim or iron code bases).