Comments (6)
Could you try replacing %{\E[0m%} with %f and see if that fixes the issue?
Yup! That did it :~)
Thank you and very happy to have caught it @ericbn !
from minimal.
Could not reproduce with a new installation of Zim replacing duration-info + git-info + asciiship by git-info + prompt-pwd + minimal.
Also could not reproduce with a new installation of Zim using your .zimrc, because TAB opens fzf and then SPACE does not select the completion. Even if doing TAB ENTER SPACE, I still cannot see the last character turn green.
Maybe this is related to one of the plugins you're using? Have you tried disabling one by one?
from minimal.
hmm damn. thanks for checking. I did try disabling what the main culprits should probably be (completion / syntax highlighting). But will have a more thorough go.
from minimal.
so I looked further and I've got new hints, but no answers...
I uninstalled all plugins except the minimal theme (I'm only using zim and no external plugins).
It looks like the text is inheriting the color of the lambda symbol, which is being set dependent on whether a command was executed with/without fail.
The thing is that I was using the s1ck94 theme, which also took the color of a successful / failed command, and it did not color the text.
I'll keep looking, but it seems that it's not to do with any other zim / zsh plugin.
This occurs in kitty and iterm.
maybe its a macos thing.
from minimal.
I guess this might be due to the colour for the prompt character never being reset via %f
:
Line 54 in 08fcfda
The colour is set, the user character is printed, but colour is not reset. I haven't looked into it, but this suggests that colour in prompts is scoped - as in each %F
creates a colour scope and the caret character gets its own colour scope to be printed in grey, but once it uses %f
it exits its colour scope and we're back in the scope of the user character (green/red respectively in the above example).
Could you try replacing %{\E[0m%}
with %f
and see if that fixes the issue?
from minimal.
@PatTheMav is correct. Just fixed that. The %{\E[0m%}
is needed to clear the mode previously set by %{\E[${MNML_BGJOB_MODE}m%}
, but that was not clearing the foreground color set by %F{%(?.${MNML_OK_COLOR}.${MNML_ERR_COLOR})}
. Added the extra %f
.
Good catch @tjex!
from minimal.
Related Issues (3)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from minimal.