-
Notifications
You must be signed in to change notification settings - Fork 376
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
Support for REPLs (irb, ipython, psql, node, mongosh, etc.) #4082
Comments
Support |
Support Show support for ipython REPL on the dedicated issue #4400 |
Support |
Support |
Support |
Support |
Support |
Support |
Support |
Support |
Hopefully, it includes support of REPLs inside of subshells (e.g. calling irb when inside k8s instance) |
Support |
Support |
Hey there, I'm an IPython dev. I'd love to learn how to make IPython work well with warp (protocols, etc.). |
i've been working on rewriting i noticed that for bash there is this special message warp can use to activate a subshell print '\eP$f{ "hook": "SourcedRcFileForWarp", "value": { "shell": "bash" } }\x9c' which triggers some magic internally, likely specifically designed for warps integration with bash. it would be very cool if this could be used by a TUI application developer to deeply integrate the blocks and autocomplete feature into the application. but unfortunately, i dont think it is yet possible to do any custom integrations. the warp docs do not seem to have any technical information about what "warpify" actually does; it seems to be a private protocol that outsiders are not meant to use. it would be very cool to have something like: print '\eP$f{ "hook": "InitShell", "value": { "shell": "custom" } }\x9c' along with many other input and output escape sequences to communicate rich terminal features like blocks and request. is something like this in scope for this issue? or should i raise a separate issue for this "custom" shell integration. |
Support |
Support Show support for bun REPL on the dedicated issue #4401 |
Hey @rgbkrk & @paperdave, Thanks for reaching out and offering to help support We do have plans to support REPLs and a more explicitly designed and thought-out extensibility effort on the roadmap. We plan to dedicate resources to work on this later this year. We’d love to work with you on them and we’ve opened separate issues to track support for each REPL here. ipython and bun. We’ll also link them in the meta issue for REPL support so that users can track the progress. Please feel free to reach out with any comments or concerns on the respective issues. |
Support |
Its not clear to me the scope of the REPL support imagined in this issue, but I could imagine some fairly fancy and awesome options. But with the "later this year" time scales, I wonder whether there is not some very simple and quick stopgap that would make things 90% usable at least? The only problem with the two I've played with (ipython and julia) is basically simply that the clear screen keyboard shortcut ("Ctrl+L") scrolls the REPL to the wrong spot, or leaves it covered up, whch is unfortunately a serious usability killer. Conversely, an explicit |
How about https://orbstack.dev/ which using orb commad to enter docker or vm? |
If this will take a while to implement, could we at least disable blocks while a REPL is active? If you accidentally select a block (which I do all the time) it's really hard to be able to input again because the input block is selected when you click on it. I think double clicking usually works, but it's hard to remember to do that. |
Support |
Support |
Support erl: erl is the REPL for the Erlang programming language. It provides an interactive environment for writing and executing Erlang code. Erl is specifically designed for Erlang and offers features like code evaluation, tab completion, documentation lookup, and shell command execution. |
Support |
Describe the solution
** Support for the running list of non-shell based REPLs without Warp features ( i.e. Blocks, Autocomplete) **
irb, ipython, pipenv, psql, node, mongosh, rails, julia, iex, nix-shell, etc.
How does this Feature request thread work?
We've included comments below for each of the REPLs that has been requested, please 👍 each comment to signal interest in that REPL.
If the REPL isn't on the list, please add a comment for it along with a brief description of the REPL in a similar format (e.g. "Support
REPL command
: REPL description")Subscribe to get updates on the status of this request, the Warp team will post any comments if one of the REPLs support is being worked on.
Please avoid commenting with the same REPLs, or comments like "+1 for ipython" as they create spam on the thread.
Note this is a different issue than support for shell-based "subshells", which we launched and you can learn more about here.
The text was updated successfully, but these errors were encountered: