Webterm future #1750
-
I know that (for entirely good reasons) webterm isn't at the top of the priority lists development-wise, but I was wondering what/if the future plans are for it? It seems like it could become a powerful tool that could real advantages over a traditional command line like the ability to return javascript objects, numbers and strings from commands, and can provide rich output. It kind of grabbed my imagination. I was wondering what people thought about some of the following ideas, or there were better ways to do these things?
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hey @matthewauld yeah it's awesome to hear you're digging Webterm. I'm working right now (half a commit done) to sandbox webterm commands properly so we can feel less anxiety about running them. That seems like a pretty key first step, so it wont be in this week's release but probably the next one. There's a semi-outdated webterm specs repo. Why don't we start doing proposals there? I think command composition would be a great thing to start discussing. |
Beta Was this translation helpful? Give feedback.
-
I love webterm. I use my "blogpost" command to write my microblog posts and it's to me at least, the fastest way to browse through drives. |
Beta Was this translation helpful? Give feedback.
Hey @matthewauld yeah it's awesome to hear you're digging Webterm.
I'm working right now (half a commit done) to sandbox webterm commands properly so we can feel less anxiety about running them. That seems like a pretty key first step, so it wont be in this week's release but probably the next one.
There's a semi-outdated webterm specs repo. Why don't we start doing proposals there? I think command composition would be a great thing to start discussing.