51–60 of 93 posts
Earlier quoted context omitted.
> so I went back to the default macOS one I find iTerm to be the standard among macOS developers.
ya, i love iTerm. been a loyal user for more than 10 years. that is until Wave of course :)
But nothing can beat foot [0]. But it's only for wayland, so I need to use alacritty on macOS.
> We don’t require an email, login, or payment to use our terminal (it is free as in speech and as in beer). This excites me. I was excited to try a new terminal last week and I had to sign up. I wouldn't do that, so I went back to the default macOS one. I'll give Wave Term a try! It's clear you have put a lot of thought into the product and its delivery after reading your message above -- it is noted and appreciated…
> so I went back to the default macOS one I find iTerm to be the standard among macOS developers.
That said, my terminal usage is nowhere near as heavy as it is for some.
I think I ran into this same bug: https://github.com/wavetermdev/waveterm/issues/161 I try to cd and it just leaves me in ~. Using on mac. Looks cool, but obviously pretty limited use when you can't cd. :-)
i'd love to figure out what is causing this as we haven't been able to repro it. if you don't mind adding a comment to the issue with anything novel or interesting in your .bashrc / .bash_profile or your machine setup it would be much appreciated.
Looks neat. A screenshot or video would be much appreciated.
https://waveterm.dev has some screenshots. Also checkout our twitter feed https://twitter.com/wavetermdev . I couldn't post the homepage as the main link because of a dup check on HN (someone unaffiliated with the company posted the link last week).
Honest question, why does everyone uses discord for community space nowadays? What happened to product forums that could be easily found in a web search?
Earlier quoted context omitted.
> […] I ssh'd to another machine and was slightly disconcerted to see it installing software on first connection? That sounds really disturbing and immediately turns me off this project (as well as not having the need for a VC-backed terminal).
the helper program is completely open source (waveshell) it is similar to the shell scripts or additions to your rc files that other modern terminals might add when connecting to a remote machine to support advanced features. the helper does not need any additional permissions, does not open any ports, runs only for the duration of the connection, and communicates exclusively via stdout/stdin over your standard ssh c…
Earlier quoted context omitted.
the helper program is completely open source (waveshell) it is similar to the shell scripts or additions to your rc files that other modern terminals might add when connecting to a remote machine to support advanced features. the helper does not need any additional permissions, does not open any ports, runs only for the duration of the connection, and communicates exclusively via stdout/stdin over your standard ssh c…
It absolutely should not be running commands on a remote host without prompting first!
Would love to get any suggestions for what people would like to see rendered inline in the terminal. Things like graphs, audio/video streams, filesystem view (that supports drag&drop from your local machine), graphviz, pdfs. Maybe a graphical way to view a JIRA or Github issue and add a comment? Visual diff? Let me know what you think?
I wonder if we could render html inline now as you can do images and other others? Same thing for Markdown for example. My dream would be to basically move everything into the console, but I need graphical applications these days for interacting with others at work etc.
Would love to get any suggestions for what people would like to see rendered inline in the terminal. Things like graphs, audio/video streams, filesystem view (that supports drag&drop from your local machine), graphviz, pdfs. Maybe a graphical way to view a JIRA or Github issue and add a comment? Visual diff? Let me know what you think?
Earlier quoted context omitted.
It absolutely should not be running commands on a remote host without prompting first!
agree in principle, but i will split some hairs here. if you type "ls" into your local terminal, there's an implicit agreement that it will run the remote "ls" program. the helper program facilitates that in the same way that any other terminal + ssh + shell combo does. it only runs commands in response to your activities in the terminal.