removed international character issue from faqs

This commit is contained in:
Knox Lively
2024-02-21 16:19:34 -07:00
parent a345067af8
commit 446778f773
+2 -6
View File
@@ -14,10 +14,6 @@ Wave telemetry is very minimal, anonymized, completely optional, and you can opt
We currently only support `bash`. Your environment (including variables, functions, and aliases) is read from the standard bash startup files (.bash_profile). In order to customize Wave's environment at startup Wave will set the environment variable `WAVESHELL`. If you are currently using `zsh`, you might have to transfer some of your `.zprofile` setup into your `.bash_profile`. See [Using Wave Terminal with zsh](https://docs.waveterm.dev/reference/zsh) for more information.
## Why do international characters appear as question marks?
It is a known issue that Wave Terminal does not support international unicode characters yet. We are investigating a solution and tracking the issue [here](https://github.com/wavetermdev/waveterm/issues/88)
## How do I specify SSH options such as PubkeyAcceptedKeyTypes?
Currently there is no way to specify these option in the Connections UI. A workaround is to add the options to your ~/.ssh/config file. Wave Terminal uses ssh natively under the hood and so any options set in your ssh config will be picked up by Wave directly.
@@ -50,7 +46,7 @@ Wave loads your bash configuration by executing bash with the -l and -i options
No, it is not required. You can use Wave as a normal terminal by just executing a traditional `ssh` command at the Wave prompt. That will create a command block that runs your remote ssh session. When running ssh like this mshell/waveshell will not be installed on your remote machine.
For more information see [WaveShell Helper](/reference/waveshell)
For more information see [WaveShell Helper](/reference/waveshell)
## What is mshell/waveshell, why does it need to be installed on machines I connect to?
@@ -64,4 +60,4 @@ Yes (must have Wave v0.6.0 or later). If you run `/reset shell=zsh` or `/reset s
When building v0.6.0 we noticed some irregularities in how we were storing bash shell state. Specifically if your rcfiles produced any spurious output (invalid aliases was a common culprit), the shell state might be saved, but in a broken way. While migrating to v0.6.0 we flagged any of these invalid states and show this message.
Clicking "reset shell state" (or running the slash command `/reset`) will force Wave to re-read your bash config files and produce a new valid state. Note that after running the reset, your cwd and environment will be reset as if this was a new session.
Clicking "reset shell state" (or running the slash command `/reset`) will force Wave to re-read your bash config files and produce a new valid state. Note that after running the reset, your cwd and environment will be reset as if this was a new session.