Replies: 1 comment 2 replies
-
Im not sure what exactly you want to achieve with this to be honest. a specific use case would be helpful for me. a few request-sources and better alternatives i can think of:
a few results it could achieve and why i think theyre a bad idea:
another idea would be a application, which uses nushell as its interface. PS: i wrote another gigantic wall of text.. i don't want / mean to directly shoot you down with this. please don't feel discouraged due to this - i just tend to think way to much about such things and often don't see the obvious things. |
Beta Was this translation helpful? Give feedback.
-
Plugins currently can only read commands from the shell and respond to these command immediately. I think they could be so much more powerful if they could also initiate interaction with the shell when something happen on their side - when they receive a message on a socket they've opened, or when something they watch changes, or even just when a timer expires.
The language that the plugin is written in can be the one responsible for running the background task (in Rust's case, though, the official
nu-plugin
crate should assist with that). What the nushell protocol needs to support is for the plugin itself to initiate things. Namely:$env
which the prompt uses.Beta Was this translation helpful? Give feedback.
All reactions