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

Version 1.3.15.1010: The command line does not display the "λ" symbol #2347

Closed
alexinea opened this issue Jul 12, 2020 · 13 comments
Closed
Labels
👆 clink Upstream issue in clink.

Comments

@alexinea
Copy link

image

My configuration in init.bat is:

@prompt $E[1;32;40m$P$S{git}{hg}$S$_$E[1;30;40m{lamb}$S$E[0m

My Tasks startup commands is:

cmd /k ""%ConEmuDir%\..\init.bat" -new_console:d:%USERPROFILE% "

I can't get the effect like in the screenshot of cmder.net.

Is there something wrong with my configuration?

@alexinea
Copy link
Author

I refer to #2166 and #2167. I didn't find --nolog under init.bat.

@daxgames
Copy link
Member

@alexinea did you edit init.bat to add some custom prompt config? If so you shouldn't ever edit anything inside the vendor folder because every thing in that folder is overwritten on updates.

Custom prompt config should be added to a %cmder_root%\config\*.lua file and be written in lua.

@alexinea
Copy link
Author

Thank you very much @daxgames for your reply.

I only added one line of code:

@prompt $E[1;32;40m$P$S{git}{hg}$S$_$E[1;30;40m{lamb}$S$E[0m

I added this line of code (which used to appear in the old version of cmder) to make my cmder interface color.

Now after deleting this line of code, my colored text and the "λ" symbol are gone.

image

And in the git folder, you can not prompt git branch information. (In previous versions of cmder there was no such problem.)

Even if the pure version of cmder-mini is downloaded from cmder.net, it will be different from the following picture after startup:

image

Am I missing a lot of caring information? Is it because of different versions?

@daxgames
Copy link
Member

The screenshot you refer to is VERY old. I am running the current version of Cmder on Microsoft Windows [Version 10.0.19041.329] and the prompt looks like:

image

The line of code may have worked, but I doubt it, in a Cmder version from many years ago but would not work in the init.bat because it depends on clink and lua in any of the versions I have been associated with and that is at least the last 10-12 releases.

The clink output at the top is odd and should not be seen. Do you have clink installed separately?

What version of Windows are you running please provide output of ver command. There is an open issue that clink is not compatible with the latest Windows Insider version of Windows and we have no control over that. See: #2341 and mridgers/clink#543

@alexinea
Copy link
Author

Yes, I installed clink separately.
My OS is Windows 10 Insider 20161.

After I uninstalled clink, the information about clink at the top when cmder started was no longer displayed. The picture below is the information I got after uninstalling clink.

image

@daxgames daxgames added the 👆 clink Upstream issue in clink. label Jul 12, 2020
@daxgames
Copy link
Member

You are experiencing mridgers/clink#543. Nothing I can do to help.

You might want to contribute to the referenced bug report.

@daxgames
Copy link
Member

Duplicate of #2341

@daxgames daxgames marked this as a duplicate of #2341 Jul 12, 2020
@nikitalita
Copy link

Well, if nothing can be done about this, then cmder is going to be broken and useless when these changes in Insider start rolling to Windows stable.

@daxgames
Copy link
Member

daxgames commented Oct 3, 2020

@chrisant996 is actively working on a fork of Clink 1.x.x. Hopefully he can address this.

@nikitalita
Copy link

@kamenminkov
Copy link

kamenminkov commented Oct 26, 2020

Wow, so nice to be able to use cmder again. Thank you for the workaround!

Edit: just to note, what's working for me is just dropping the contents of this into cmder\vendor\clink of my current 1.3.16 install. It's a bit slow at first launch (like it was before), hopefully the 1.x.x improves on that.

@chrisant996
Copy link
Contributor

It's a bit slow at first launch (like it was before), hopefully the 1.x.x improves on that.

Clink 1.x installed separately, started by itself -- starts almost instantly on my machine.
Clink 1.x installed separately, started inside Cmder -- starts almost instantly on my machine.
Clink 0.4.9 installed with Cmder -- starts slowly on my machine.

That suggests the slowness is related to how Cmder integrates with Clink. As I get Clink 1.x nearer to release, I'll profile the startup and see if there are inefficiencies in Clink itself, and see if there are any suggestions I can offer to the Cmder team for how to make Clink startup faster.

There are enough changes in Clink 1.x that it's unlikely to be a simple drop-in replacement; lua scripts will need to be updated, but it should be fairly straightforward.

@kamenminkov
Copy link

kamenminkov commented Oct 27, 2020

Cool, looking forward to that! Thank you for your work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👆 clink Upstream issue in clink.
Projects
None yet
Development

No branches or pull requests

5 participants