AmrEldib / cmder-powerline-prompt

Custom prompt for Cmder on Windows
715 stars 154 forks source link

Setup not working #59

Closed samayo closed 4 years ago

samayo commented 4 years ago

I don't know what I am exactly missing, but I did everything according to the readme and also checked another guide but I can't get it to work or show anything differently.

I have downloaded the AnonymousPro from https://github.com/powerline/fonts/tree/master/AnonymousPro and installed all .ttf fonts

And setup cmder

cmder2

I put all the .lua from this repo to /cmder/config

cmder3

But I don't see anything different at all.

cmder

Anyone know how to fix this?

Muadiv commented 4 years ago

Hi @samayo , I installed and is working for me. Check my config on the font part that have a couple of options different, maybe that will help.

image

Best regards Muadiv.

Leslie307 commented 4 years ago

win10 system,I have the same problem. I reinstalled the cmder ,the problem is solved.

testworksau commented 4 years ago

I also had the same issue. I think the issue occurs due to some old & incompatible files / configuration settings that may have been placed in various directories over time.

With no changes to the fonts at all, a fresh install of Cmder, and copying of the *.lua files into the config directory you should see something like this on first startup of Cmder:

image

lucknaumann commented 4 years ago

@samayo Your issue appears to be using another shell and not the Window's Command prompt. You'll notice at the top of the README there's a link for a version of the Powershell prompt.

If you want bash/MINGW64 check out this powerline-shell repo. You may need to add this additional line to your Cmder's .bashrc export PYTHONIOENCODING="utf-8". If you also want it in the non-Cmder external bash shell you'll need to add those lines to your non-Cmder .bashrc file and change MINGW64/mintty shell Options> Text to utf-8.

samayo commented 4 years ago

Thanks I will check again

shiwen commented 4 years ago

@samayo I had the same issue that the setup procedure have absolutely no effect on my cmder sessions. After a long time of frustration, I have found the root cause. Before I try out cmder, I installed clink manually via chocolatey. I believe that instance of clink was installed in a somewhat global manner which cmder session refer to during initialization, other than the instance of clink packed with cmder in the 'vendor' folder. And the 'global' clink does not honor lua scripts in the cmder configuration folder. After I uninstalled the 'global' clink via chocolatey, the powerline style prompt worked like a charm. Hope that helps if you are in the same situation.

samayo commented 4 years ago

@shiwen I gave up on it a long time ago, but thank for the info. If I ever decided to try again I will follow your comment 👍