more general installation readme instructions

README.md

@@ -232,12 +232,26 @@ easy to fork and contribute any changes back upstream.
 3. **Add `pyenv init` to your shell** to enable shims and autocompletion.
    Please make sure `eval "$(pyenv init -)"` is placed toward the end of the shell
    configuration file since it manipulates `PATH` during the initialization.
-    ```sh
+
+   - For **bash**:
+     ~~~ bash
      echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n  eval "$(pyenv init -)"\nfi' >> ~/.bash_profile
-    ```
+     ~~~
-    - **Zsh note**: Modify your `~/.zshrc` file instead of `~/.bash_profile`.
+
-    - **fish note**: Use `pyenv init - | source` instead of `eval (pyenv init -)`.
+   - For **Ubuntu Desktop** and **Fedora**:
-    - **Ubuntu and Fedora note**: Modify your `~/.bashrc` file instead of `~/.bash_profile`.
+     ~~~ bash
+     echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n  eval "$(pyenv init -)"\nfi' >> ~/.bashrc
+     ~~~
+
+   - For **Zsh**:
+     ~~~ zsh
+     echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n  eval "$(pyenv init -)"\nfi' >> ~/.zshrc
+     ~~~
+
+   - For **Fish shell**:
+     ~~~ fish
+     echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n  eval "$pyenv init - | source"\nfi' >> ~/.bash_profile
+     ~~~
 
     **General warning**: There are some systems where the `BASH_ENV` variable is configured
     to point to `.bashrc`. On such systems you should almost certainly put the above mentioned line