From 2855401ff01bcdfc74cfaf1e290e25ebafed1dd1 Mon Sep 17 00:00:00 2001 From: Knox Lively Date: Wed, 21 Feb 2024 19:43:37 -0700 Subject: [PATCH] =?UTF-8?q?added=20zsh=20support,=20removed=20zsh=20compab?= =?UTF-8?q?ility=20stuff=20from=20the=20faq=20and=20fro=E2=80=A6=20(#12)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- mint.json | 1 - reference/faq.mdx | 2 +- reference/zsh.mdx | 38 -------------------------------------- 3 files changed, 1 insertion(+), 40 deletions(-) delete mode 100644 reference/zsh.mdx diff --git a/mint.json b/mint.json index 781fb3a..8fdb330 100644 --- a/mint.json +++ b/mint.json @@ -71,7 +71,6 @@ "reference/faq", "reference/keyboard", "reference/slashcommands", - "reference/zsh", "reference/waveshell" ] } diff --git a/reference/faq.mdx b/reference/faq.mdx index cace08d..9a5c157 100644 --- a/reference/faq.mdx +++ b/reference/faq.mdx @@ -12,7 +12,7 @@ Wave telemetry is very minimal, anonymized, completely optional, and you can opt ## What shells does Wave Terminal support? -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. +We currently support `bash` and `zsh`. Your environment (including variables, functions, and aliases) is read from the standard bash and zsh startup files (.bash_profile and .zshrc). In order to customize Wave's environment at startup Wave will set the environment variable `WAVESHELL`. ## How do I specify SSH options such as PubkeyAcceptedKeyTypes? diff --git a/reference/zsh.mdx b/reference/zsh.mdx deleted file mode 100644 index 79e73a7..0000000 --- a/reference/zsh.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Using Wave Terminal with zsh ---- - -Wave Terminal currently only supports `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 have Wave pick up your path and other environment settings. - -> Note that supporting zsh is high on our technical roadmap and we expect to have have at least partial (if not full) zsh support in the next couple of months. - -## How do I get brew commands to work? - -If using brew, get brew commands to work by running the `brew shellenv` command in a Wave Terminal tab session. This will update the current tab session. To update all sessions in Wave Terminal, add the `shellenv` command to your .bashrc file. See below for further instructions. - - - - Use codeedit inside Wave Terminal to modify your bashrc e.g. - ``` - /codeedit .bashrc - ``` - copy and paste this into your ./bashrc then save the file. - ``` - eval "$(/opt/homebrew/bin/brew shellenv) - ``` - - - Run the following command in a terminal to update your .bashrc - ``` - echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.bashrc - ``` - - - - - Run brew command ```brew help shellenv``` for more information on managing brew setup. - - -## How do I get nvim to work in Wave Terminal? - -Any applications installed with brew will likely need a PATH update, see the previous FAQ for further details on how to do this. \ No newline at end of file