<commit_before># erlenv (v0.4) #

## do you like rbenv? you'll love erlenv ##

used to [rbenv][rbenv]? erlenv is
*almost* exactly the same thing. use erlenv to setup and switch between
multiple erlang releases effortlessly. ok maybe some tiny amount of
effort required

erlenv is a fork of [rbenv][rbenv] and all credit belongs to
[<NAME>][sstephenson] and the other contributors to [rbenv][rbenv]


## index ##

* [introduction](#introduction)
* [quickstart](#quickstart)
* [usage](#usage)
  - [global](#global)
  - [local](#local)
  - [shell](#shell)
  - [release](#release)
  - [releases](#releases)
  - [rehash](#rehash)
  - [which](#which)
  - [whence](#whence)
* [license](#license)


## introduction ##

erlenv allows multiple erlang releases to coexist peacefully, and makes it easy
to switch between them on a systemwide, per user or per directory basis

each directory under the directory `~/.erlenv/releases` is considered a release.
you might have `~/.erlenv/releases/r14b04`, `~/.erlenv/releases/r15b01` and
`~/.erlenv/releases/github_head` for example

each release is it's own working tree with it's own binaries and applications.
erlenv creates _shim_ binaries - simple wrapper scripts - that redirect execution
to the currently active release

because of this shim approach, all you need to use erlenv is `~/.erlenv/shims`
in your `$PATH`


## quickstart ##


check out erlenv into `~/.erlenv`:

```bash
$ cd
$ git clone https://github.com/talentdeficit/erlenv.git .erlenv
```

add `~/.erlenv/bin` to your `$PATH` for access to the `erlenv` command-line
utility

```bash
$ echo 'export PATH="$HOME/.erlenv/bin:$PATH"' >> ~/.bash_profile
```

**zsh note**: modify your `~/.zshenv` file instead of `~/.bash_profile`

add erlenv init to your shell to enable shims and autocompletion

```bash
$ echo 'eval "$(erlenv init -)"' >> ~/.bash_profile
```

**zsh note**: modify your `~/.zshenv` file instead of `~/.bash_profile`

restart your shell so the path changes take effect. you can now begin using
erlenv

```bash
$ exec $SHELL
```

install releases into `~/.erlenv/releases`. for example, to install OTP R15B01,
download and unpack the source, then run:

```bash
$ ./configure --prefix=$HOME/.erlenv/releases/r15b01
$ make
$ make install<commit_msg>Update README.md for fish shell<commit_after># erlenv (v0.4) #

## do you like rbenv? you'll love erlenv ##

used to [rbenv][rbenv]? erlenv is
*almost* exactly the same thing. use erlenv to setup and switch between
multiple erlang releases effortlessly. ok maybe some tiny amount of
effort required

erlenv is a fork of [rbenv][rbenv] and all credit belongs to
[<NAME>][sstephenson] and the other contributors to [rbenv][rbenv]


## index ##

* [introduction](#introduction)
* [quickstart](#quickstart)
* [usage](#usage)
  - [global](#global)
  - [local](#local)
  - [shell](#shell)
  - [release](#release)
  - [releases](#releases)
  - [rehash](#rehash)
  - [which](#which)
  - [whence](#whence)
* [license](#license)


## introduction ##

erlenv allows multiple erlang releases to coexist peacefully, and makes it easy
to switch between them on a systemwide, per user or per directory basis

each directory under the directory `~/.erlenv/releases` is considered a release.
you might have `~/.erlenv/releases/r14b04`, `~/.erlenv/releases/r15b01` and
`~/.erlenv/releases/github_head` for example

each release is it's own working tree with it's own binaries and applications.
erlenv creates _shim_ binaries - simple wrapper scripts - that redirect execution
to the currently active release

because of this shim approach, all you need to use erlenv is `~/.erlenv/shims`
in your `$PATH`


## quickstart ##


check out erlenv into `~/.erlenv`:

```bash
$ cd
$ git clone https://github.com/talentdeficit/erlenv.git .erlenv
```

add `~/.erlenv/bin` to your `$PATH` for access to the `erlenv` command-line
utility

```bash
$ echo 'export PATH="$HOME/.erlenv/bin:$PATH"' >> ~/.bash_profile
```

**zsh note**: modify your `~/.zshenv` file instead of `~/.bash_profile`

**For fish shell**

```fish
$ echo 'set PATH ~/.erlenv/bin $PATH' >> ~/.config/fish/config.fish
```

add erlenv init to your shell to enable shims and autocompletion

```bash
$ echo 'eval "$(erlenv init -)"' >> ~/.bash_profile
```

**zsh note**: modify your `~/.zshenv` file instead of `~/.bash_profile`

**For fish shell**

```fish
$ echo '. (erlenv init -|psub)' >> ~/.config/fish/config.fish
```

restart your shell so the path changes take effect. you can now begin using
erlenv

```bash
$ exec $SHELL
```

**For fish shell**

```fish
$ eval $SHELL
```

install releases into `~/.erlenv/releases`. for example, to install OTP R15B01,
download and unpack the source, then run:

```bash
$ ./configure --prefix=$HOME/.erlenv/releases/r15b01
$ make
$ make install
{'fraction_non_alphanumeric': 0.14303612445186886, 'fraction_numerical': 0.007517226978492378, 'mean_word_length': 4.328142380422692, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 17, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2779748', 'n_tokens_mistral': 1737, 'n_tokens_neox': 1591, 'n_words': 556}