Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

powerline appears on top of the default tmux status #151

Closed
roseperrone opened this issue Mar 4, 2013 · 18 comments
Closed

powerline appears on top of the default tmux status #151

roseperrone opened this issue Mar 4, 2013 · 18 comments

Comments

@roseperrone
Copy link

I'm on mac OS 10.8 running the latest tmux. The default tmux status has a bright green background, and this color and its title are visible underneath the powerline status.

@erikw
Copy link
Owner

erikw commented Mar 4, 2013

Strange, screenshot? Similar/same as this issue?

@roseperrone
Copy link
Author

Wow, thanks for the quick reply! There is no Preferences -> Settings -> Advanced in iTerm2. Where can I find the East Asian characters option?

On Mar 3, 2013, at 7:52 PM, Erik Westrup [email protected] wrote:

Strange, screenshot? Similar/same as this issue?


Reply to this email directly or view it on GitHub.

@erikw
Copy link
Owner

erikw commented Mar 4, 2013

I don't have access to my mac so I can't check this out my self. Maybe I misunderstood @narze and he meant Terminal.app? In that thread iTerm2 was mentioned before his answer so I assumed that he used it too. Mess around with the iTerm options and see if you can find something :-)

@roseperrone
Copy link
Author

The character encoding is UTF-8, and a search through the prefs and google turned up nothing. Do you have other ideas? I'm using bash and xterm.

On Mar 3, 2013, at 8:00 PM, Erik Westrup [email protected] wrote:

I don't have access to my mac so I can't check this out my self. Maybe I misunderstood @narze and he meant Terminal.app? In that thread iTerm2 was mentioned before his answer so I assumed that he used it too. Mess around with the iTerm options and see if you can find something :-)


Reply to this email directly or view it on GitHub.

@roseperrone
Copy link
Author

Do you thinx tmux-powerline depends on another dot file that has an option that's not being overridden?

On Mar 3, 2013, at 8:00 PM, Erik Westrup [email protected] wrote:

I don't have access to my mac so I can't check this out my self. Maybe I misunderstood @narze and he meant Terminal.app? In that thread iTerm2 was mentioned before his answer so I assumed that he used it too. Mess around with the iTerm options and see if you can find something :-)


Reply to this email directly or view it on GitHub.

@erikagnvall
Copy link
Collaborator

Strange indeed, could you provide a screenshot? Also, a Gist with the contents of ~/.tmux-powerlinerc and ~/.tmux.conf would be helpful.

If you're running iTerm2, make sure that Preferences>Profiles>Text>"Treat ambiguous-width characters as double width" is unchecked because that caused some strange issues for me.

@roseperrone
Copy link
Author

Where can I find the .tmux-powerline.conf? Here's my .tmux.conf:

unbind some default keybindings

unbind C-b

set prefix key to ctrl-a

#set -g prefix Home
#set -g prefix End
set -g prefix C-a
#bind-key Home C-a

lower command delay

set -sg escape-time 1

start first window and pane at 1, not zero

set -g base-index 1
set -g pane-base-index 1

bind r to reloading the config file

bind r source-file ~/.tmux.conf ; display "Reloaded tmux config file."

pass through a ctrl-a if you press it twice

bind C-a send-prefix

better mnemonics for splitting panes!

bind | split-window -h
bind - split-window -v

#set-option -g status on
#set-option -g status-interval 2
#set-option -g status-utf8 on
#set-option -g status-justify "centre"
#set-option -g status-left-length 60
#set-option -g status-right-length 90
#set-option -g status-left "#(/usr/local/Cellar/tmux-powerline/powerline.sh left)"
#set-option -g status-right "#(/usr/local/Cellar/tmux-powerline/powerline.sh right)"
#set-window-option -g window-status-current-format "#[fg=colour235, bg=colour27]⮀#[fg=colour255, bg=colour27] #I ⮁ #W #[fg=colour27, bg=colour235]⮀"
#bind C-[ run '/path/to/tmux-powerline/mute_powerline.sh left' # Mute left statusbar.
#bind C-] run '
/path/to/tmux-powerline/mute_powerline.sh right' # Mute right statusbar.

On Mar 4, 2013, at 12:34 AM, Erik Jansson [email protected] wrote:

Strange indeed, could you provide a screenshot? Also, a Gist with the contents of ~/.tmux-powerlinerc and ~/.tmux.conf would be helpful.

If you're running iTerm2, make sure that Preferences>Profiles>Text>"Treat ambiguous-width characters as double width" is unchecked because that caused some strange issues for me.


Reply to this email directly or view it on GitHub.

@erikw
Copy link
Owner

erikw commented Mar 4, 2013

If you followed the steps in the README the conf generator script should have put it in ~.tmux.-powerlinerc.default. Check that part of the readme again :-)

@mikesplain
Copy link

If I'm understanding you correctly, I'm experiencing the same issue right now... things looked fine on friday and now my tmux is messed up... rebooted so I may have had something set in my env previously.

Screen Shot 2013-03-04 at 2 26 43 PM

@erikagnvall
Copy link
Collaborator

I found what I believe is the problem. I compared your conf to mine and tried yours (with the same result as you had). I then began adding things from my conf and the problem disappeared once I added the line sourcing tmux-colors-solarized/tmuxcolors.conf. Try installing tmux-colors-solarized and sourcing it from .tmux.conf with the following line:

source /path/to/tmux-colors-solarized/tmuxcolors-256.conf

@mikesplain
Copy link

Ahh, I just took the lines from that file and put them in my .tmux.conf file and that fixed the problem. Good find!

@roseperrone
Copy link
Author

Thanks. That worked. The only issue now is that it looks bad. I turned off all segments but a few, and parts of the status are unreadable.
Screen Shot 2013-03-04 at 8 18 40 PM

@ajongsma
Copy link

ajongsma commented Mar 5, 2013

@roseperrone I have been struggling with the same exact thing for many days now on OS X 10.8:

First I checked the install, please read step 1 to 3 (https://github.com/Lokaltog/vim-powerline/tree/develop/fontpatcher#os-x)

Step 4 still caused python errors so I decided to brew with another formula:
$ brew install --use-gcc https://raw.github.com/ummels/homebrew/fontforge/Library/Formula/fontforge.rb
$ brew linkapps

After this step I was able to successfully patch a random selected font:
$ /usr/local/bin/fontforge -lang=py -script $HOME/Github/vim-powerline/fontpatcher/fontpatcher /Library/Fonts/Verdana.ttf
$ open Verdana-Powerline.ttf

PS: After this step all powerline fonts suddenly seemed to work oddly enough, further investigation is required but I figured above might help you out

@supernullset
Copy link

Hi all; I think I may have tracked this one down.

I'm using Zsh, the usual caveats apply

After having the GIANT GREEN BAR ISSUE for 2 days I could not take it anymore. I figured that something was getting botched in my .tmux.conf; the offending option is status-bg, it does not matter if you have it set or not. By setting status-bg to colour235(default powerline background color), the green bar will go away into the mist. You may need to have set -g default-terminal "screen-256color" in the conf as well.

If you have changed the default background color in your powerline theme, substitute it for colour235

tl;dr:

set -g default-terminal "screen-256color"
set -g status-bg colour235

Screen Shot 2013-03-08 at 9 14 41 AM

@erikw
Copy link
Owner

erikw commented Mar 10, 2013

Does that help you other guys too?

@jtuz
Copy link

jtuz commented Mar 26, 2013

Hey @supernullset and @erikw this works for me, Thanks a lot!

@supernullset
Copy link

@jtuz No problem! Glad that I could help!

@elbo-01
Copy link

elbo-01 commented Sep 5, 2014

@supernullset thank you very much for the tip: set -g status-bg colour235

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants