-
Notifications
You must be signed in to change notification settings - Fork 391
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
Purpose of the white cross at the beginning of the prompt #44
Comments
Wes probably just wanted to use it as a symbol, it's an emoji that you can change yourself. It's on the end of this line 🙂 https://github.com/wesbos/Cobalt2-iterm/blob/master/cobalt2.zsh-theme#L52 |
Okay, it's been awhile, but stumbled across this will updating my dotfiles. The cross appears when you are ssh to a different users on the same machine, or when you ssh into a different machine that also has the cobalt2 setup. |
I'm using Terminal on macOS, and I used https://github.com/jabranr/cobalt2-like to setup the cobalt2 theme in Terminal. The instructions there have us do your installation first, then some additional steps. When I open a Terminal window, I get the cross at the start of the prompt. $DEFAULT_USER is not set nor is $SSH_CLIENT. I have seen some examples where there is a home icon or folder icon at the start of the prompt depending on what directory you are in. Any suggestions for getting that setup? Somewhere, someone suggested doing this: You could write a function like this, replacing 'home' and 'not home' with your icons
then add $(zsh_prompt_home_indicator) to your PROMPT where you want the icons to appear. I tried the following in ~/.oh_my_zsh/themes/cobalt2.zsh-theme:
That "works" somewhat: the icons are displayed correctly at the start of the prompt, but they are not on a blue background. As a test, I used the cross character in the else branch of |
What is the purpose of the white cross with the black background at the beginning of the prompt?
It doesn't seem to change at all. Can I change it to an emoji or something else?
The text was updated successfully, but these errors were encountered: