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

Lamba prompt and git status scripts not running #126

Closed
josh-nz opened this issue Jan 29, 2014 · 5 comments
Closed

Lamba prompt and git status scripts not running #126

josh-nz opened this issue Jan 29, 2014 · 5 comments

Comments

@josh-nz
Copy link

josh-nz commented Jan 29, 2014

Hi,

I've tried both the light and full versions with the same behaviour.
The git status prompt reads {git} and the lamba prompt reads {lamb}.

Refer to this image:
2014-01-24_16h08_58

I've tried to trace the loading sequence. It seems the launcher just calls vendor\conemu-maximus5\ConEmu.exe with some args for the icon, title, and the config file config\ConEmu.xml

Somehow I believe vendor\init.bat gets called, which sets the prompt with the {git} and {lamb} placeholders then loads clink using the profile in the config folder.

The config folder has git and lamba lua files, which I understand to be extension points for clink, having checked the docs. They appear to be named and written correctly. These scripts should replace the placeholders accordingly, but do not do so for me.

Any suggestions?

@BrendanThompson
Copy link

I am having the exact same thing on mine! I just pulled down a fresh copy of cmder :(

@jorisvddonk
Copy link

This seems to happen whenever you have a local installation of clink already, outside of cmder. Your own local installation somehow interferes with the installation bundled with cmder. Uninstalling clink seems to solve this issue, although I don't think that's really a proper solution for this bug (I like my clink in vanilla cmd.exe!)

@josh-nz
Copy link
Author

josh-nz commented Feb 1, 2014

I can confirm that I'm running clink outside of cmder. I'll remove it on Monday and see if that fixes the issue. I'm happy to do this, as I don't plan on using cmd.exe anymore!

@samvasko
Copy link
Contributor

samvasko commented Feb 1, 2014

When injecting clink it checks if there is already something. If it is it will not inject our clink with the settings to turn the keys into values.
One way would be to check if clink is present and unload it or load it with out settings.

Current fix is: remove clink from global autorun for cmd.exe by doing clink autorun --uninstall or something like that.

Also I will check if there is way to display some informative error.

@mirceanis
Copy link

I solved the {git} & {lamb} bug by upgrading the clink version to 0.4.4
( overwriting the /vendor/clink folder contents )

@MartiUK MartiUK closed this as completed Feb 25, 2015
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