You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -141,7 +141,7 @@ bind C-] run '~/path/to/tmux-powerline/mute_powerline.sh right' # Mute right st
141
141
142
142
Some segments e.g. cwd and cvs_branch needs to find the current working directory of the active pane. To achieve this we let tmux save the path each time the shell prompt is displayed. Put the line below in your `~/.bashrc` or where you define you PS1 variable. zsh users can put it in e.g. `~/.zshrc` and may change `PS1` to `PROMPT` (but that's not necessary).
@@ -158,30 +158,30 @@ If you have a recent version of tmux (≥ 2.1), there is no need to redefine th
158
158
159
159
The default segments that are shown are defined in `themes/default.sh`. You will probably want to change those to fit your needs. To do so you can edit that file directly but preferable, for easier updating of the repo, you can make a copy and edit that one (or see how to use custom themes directory below). A palette of colors that can be used can be obtained by running the script `color_palette.sh`.
160
160
161
-
```console
162
-
$ cp themes/default.sh themes/mytheme.sh
163
-
$$EDITOR themes/mytheme.sh
161
+
```shell
162
+
cp themes/default.sh themes/mytheme.sh
163
+
$EDITOR themes/mytheme.sh
164
164
```
165
165
Now generate a default configuration file by doing
166
166
167
-
```console
168
-
$ ./generate_rc.sh
169
-
$ mv ~/.tmux-powerlinerc.default ~/.tmux-powerlinerc # or to $XDG_CONFIG_HOME/tmux-powerline/config.sh
170
-
$$EDITOR~/.tmux-powerlinerc
167
+
```shell
168
+
./generate_rc.sh
169
+
mv ~/.tmux-powerlinerc.default ~/.tmux-powerlinerc # or to $XDG_CONFIG_HOME/tmux-powerline/config.sh
170
+
$EDITOR~/.tmux-powerlinerc
171
171
```
172
172
and change theme to use and values for segments you want to use. If you want to keep the repo checkout clean you can set custom segment and theme paths in the general section and then store your files outside the repo.
173
173
174
174
# Debugging
175
175
176
176
Some segments might not work on your system for various reasons such as missing programs or different versions not having the same options. To find out which segment is not working it may help to enable the debug setting in `~/.tmux-powerlinerc`. However this may not be enough to determine the error so you can inspect all executed bash commands (will be a long output) by doing
177
177
178
-
```console
179
-
$ bash -x powerline.sh (left|right)
178
+
```shell
179
+
bash -x powerline.sh (left|right)
180
180
```
181
181
182
182
To debug smaller portions of code, say if you think the problem lies in a specific segment, insert these lines at the top and bottom of the relevant code portions e.g. inside a function:
183
183
184
-
```console
184
+
```bash
185
185
set -x
186
186
exec2>/tmp/tmux-powerline.log
187
187
<code to debug>
@@ -190,7 +190,7 @@ set +x
190
190
191
191
and then inspect the outputs like
192
192
193
-
```console
193
+
```shell
194
194
less /tmp/tmux-powerline.log
195
195
tail -f /tmp/tmux-powerline.log # or follow output like this.
196
196
```
@@ -206,8 +206,8 @@ The issue is probably that the update of the current directory in the active pan
206
206
### Nothing is displayed
207
207
You have edited `~/.tmux.conf` but no powerline is displayed. This might be because tmux is not aware of the changes so you have to restart your tmux session or reloaded that file by typing this on the command line (or in tmux command mode with `prefix :`)
208
208
209
-
```console
210
-
$ tmux source-file ~/.tmux.conf
209
+
```shell
210
+
tmux source-file ~/.tmux.conf
211
211
```
212
212
### Multiple lines in bash or no powerline in zsh using iTerm (OS X)
213
213
If your tmux looks like [this](https://github.com/erikw/tmux-powerline/issues/125) then you may have to in iTerm uncheck [Unicode East Asian Ambiguous characters are wide] in Preferences -> Settings -> Advanced.
0 commit comments