4 ms·
I'm in the same boat as many -- not particularly excited by the idea of a new terminal, but curious enough to take a look and (unusually) a smidge interested af
by andrewaylett 3y ago
I'm in the same boat as many -- not particularly excited by the idea of a new terminal, but curious enough to take a look and (unusually) a smidge interested after seeing the website. Well done, you've got further with me than most "reinvent the terminal" projects :).
Issue 88 is a blocker, though, I'm afraid. I may be monolingual, but I still need to be able to use "international" characters.
In the interests of being interested, I did install the cask and I have some feedback :P.
I have four symbols printed on my (Macbook Pro, UK) keyboard that don't render in the output: "±§€£". Curiously, they do render in the input.
My profile files are apparently too big for Wave to process. So I ssh'd to another machine and was slightly disconcerted to see it installing software on first connection? Not something I expected, I'm afraid.
In conclusion: I can't use it, and I'm not sure I want to if it's going to automatically install software on other machines.
- sawka 3y agozsh support and international character support are our top two issues right now. I know the intl chars can work, we just didn't do enough international testing before launch. sorry to hear that it didn't work out of the box for you (the big profile files are also on our radar).
- andrewaylett 3y agoI'm not sure "international" is the right characterisation (sorry, not sorry). "Non-ASCII", perhaps? Or explicitly list which codepages you do support? It's not like there are no people in the US who use characters with accents. Or, indeed, that everyone reading your comment considers themselves to be "international".
- elaus 3y ago> […] 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).
- sawka 3y agothe 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 connection.
- smcleod 3y agoIt absolutely should not be running commands on a remote host without prompting first!
- sawka 3y agoagree 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.
- karmakaze 3y agoOh so we're holding it wrong. Does 'modern' mean pre-enshittified?
- binary132 3y agoyes if ls is installed on the remote host and if it is not, the command should fail this appears to be about telemetry, pure and simple
- sawka 3y agoabsolutely no telemetry in the helper, full stop. you can inspect the code yourself. we do hear the feedback though and are working on a popup/notification that will prompt you before we push the helper program for the next release.