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

lambda bug when i install clink #212

Closed
melck opened this issue Jun 25, 2014 · 8 comments
Closed

lambda bug when i install clink #212

melck opened this issue Jun 25, 2014 · 8 comments

Comments

@melck
Copy link

melck commented Jun 25, 2014

When I install CLINK globally and locally, I have a display problem of lambda and git.
I use clink 0.4.1 and the last full cmder.

How can I fix it?

Thank you in advance.

2014-06-25 12_04_15-cmder

@melck melck changed the title lambda bug when i installed clink lambda bug when i install clink Jun 25, 2014
@MartiUK
Copy link
Member

MartiUK commented Jun 25, 2014

Change this line:
https://github.com/bliker/cmder/blob/master/vendor/init.bat#L17

To the location of your own install of clink and remove the clink install in the vendor folder.

@Ep0chalypse
Copy link

I'm experiencing the lambda issue, however I'm not installing CLINK globally.

@melck
Copy link
Author

melck commented Jun 26, 2014

If I understood correctly, CLINK is installed with CMDER.
So if you check the option in the settings CLINK, CLINK is overloaded and lambda bug?

How have the same completion with CLINK in CMDER while avoiding change CMDER?

@isimmons
Copy link

isimmons commented Jul 5, 2014

I had this issue after upgrade because I only copied over files manually so as not to overwrite any of my own custom settings, aliases, etc. The problem was I was missing cmder/config/prompt.lua because I had not copied it over.

BTW is there a better way to stay up to date than manually copy/pasting without over writing customized files?

@elsassph
Copy link

Only solution I found was to unstall clink globally, which is not cool.

@Ep0chalypse
Copy link

Any further updates on this? I've since done a few clean installs of windows 8.1 and I still have this issue. I have never manually installed clink. On a clean install of windows 8.1 x64 I download cmder and unpack it and start it and I get the same thing as in melck's picture.

@MartiUK
Copy link
Member

MartiUK commented Apr 25, 2015

It may be an anti virus program preventing clink from running, check and
make sure cmder is on a whitelist

On Sun, 26 Apr 2015 00:10 Wicked0ne [email protected] wrote:

Any further updates on this? I've since done a few clean installs of
windows 8.1 and I still have this issue. I have never manually installed
clink. On a clean install of windows 8.1 x64 I download cmder and unpack it
and start it and I get the same thing as in melck's picture.


Reply to this email directly or view it on GitHub
#212 (comment).

@Ep0chalypse
Copy link

I'm using BitDefender free edition and I just completely disabled it tried to open cmder. It did not fix the issue.

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

6 participants