-
Notifications
You must be signed in to change notification settings - Fork 963
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
Evermeet theme #257
Evermeet theme #257
Conversation
…y overlap with the following character)
Hi, Tried the theme, and it worked well. A note about code standard: You should use the colors defined in prompt-colors.sh - makes the code easier to read. You don't have to override variables defined in Default.bgptheme that you don't change (i.e The naming standard used in the other themes for low-res themes are the suffix So, |
Thank you for your reply. It's not I'll also look into using color names. You are right, it is easier to read, but I created that prompt with my own color definitions and the escape sequences were the result. I haven't thought of going back and use the project's color names. But I can do that. With regards to overriding variables: usually I agree, but I have learned years ago that explicitly defining values can solve many, many problems. What happens, if the default ever changes? Believe me, I've seen this more often than you might think. When I think of it, I have even missed a few that I should've explicitly set - even though they are the same as the default. So if you don't mind, I'd rather add a few variables that are the current default. I'm gonna make te changes tomorrow. |
Sorry about the name mixup. You can checkout the other |
I've replaced the escape sequences with color names and renamed |
GIT_PROMPT_SEPARATOR="|" # separates each item | ||
|
||
GIT_PROMPT_BRANCH="${Magenta}" # the git branch that is active in the current directory | ||
GIT_PROMPT_STAGED="${Cyan}●" # the number of staged files/directories |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one needs and extra space in Ubuntu
The GIT_PROMPT_STAGED circle needs a training space in EDIT: I have tested the theme in Ubuntu and found three charachters that need an extra trailing space. Otherwise it looks good to me. |
GIT_PROMPT_CHANGED="${Cyan}✚ " # the number of changed files | ||
|
||
GIT_PROMPT_UNTRACKED="${Cyan}…" # the number of untracked files/dirs | ||
GIT_PROMPT_STASHED="${Magenta}⚑" # the number of stashed files/dir |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one needs an extra space in Ubuntu
@ogr3 You haven't specified line numbers. This one needs an extra space doesn't really help. But it seems that a prompt for lowres screens and Ubuntu are different after all. If I don't add the space to So how do you want to handle this? Shall I create another one that works on my MacBook 2008 lowres (non-retina) screen? |
Sorry, I added a line note in github, but I see that the actual lines might not be easily readable. The lines that need extra space in Ubuntu are:
If there are differences between Ubuntu and mac low res we could just as well add the suffix |
No worries. Usually highlighted lines are yellow, but I don't see any. Maybe something wrong with gh. Yes, these lines also have unicode characters, but for some reason I don't need the extra space for these 3 on my non-retina MacBook screen. The problem with the extra space (if not needed) is that it looks even worse when you connect to that machine on a high res display. I'll add the spaces and create a _Lowres as well. The file is not big anyway. |
@ogr3 everything in order? |
I tried the Ubuntu variant on Ubuntu 16.04 and it works fine. Looks good to me. |
Thanks a lot for the har work. |
I've created 2 theme files, because on low resolution screens, unicode characters might overlap with the following character. Thus there has to be an extra space after the unicode character.
For high res (retina) screens (which are more and more the standard these days) an extra space looks very unprofessional.