From b1eee388c1c70656aca947902a83a9d71b040080 Mon Sep 17 00:00:00 2001 From: Pablo Santiago Blum de Aguiar Date: Thu, 2 Feb 2017 22:43:54 -0200 Subject: [PATCH] Docs on how to set variables in `init.fish` (#328) Fix #328 --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index be4ae01..583a898 100644 --- a/README.md +++ b/README.md @@ -140,6 +140,18 @@ It's highly recommended that your custom startup commands go into `init.fish` fi If you need startup commands to be run *before* Oh My Fish begins loading plugins, place them in `before.init.fish` instead. If you're unsure, it is usually best to put things in `init.fish`. +#### Setting variables in `init.fish` + +One of the most common startup commands used in `init.fish` is variables definition. Quite likely, such variables need to be available in any shell session. To achieve this, define them globally. For example: + +```fish +# Golang developers might need this one +set -xg GOPATH $HOME/gocode + +# Python developers otherwise +set -xg PYTHONDONTWRITEBYTECODE 1 +``` + #### About the bundle Every time a package/theme is installed or removed, the `bundle` file is updated. You can also edit it manually and run `omf install` afterwards to satisfy the changes. Please note that while packages/themes added to the bundle get automatically installed, a package/theme removed from bundle isn't removed from user installation.