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

CLink completions for npm increase cmder startup time for one second #750

Closed
koteq opened this issue Dec 3, 2015 · 3 comments
Closed

CLink completions for npm increase cmder startup time for one second #750

koteq opened this issue Dec 3, 2015 · 3 comments

Comments

@koteq
Copy link

koteq commented Dec 3, 2015

I've just updated from 1.2 to 1.2.9 and I'm noticed increased startup time. After some research I've find that npm competitions for clink have call to npm config get cache 2>nul which executes for one second on my system (I've measured it with ptime utility). Maybe this competition module could be rewritten to call npm only when it really needed?

@koteq
Copy link
Author

koteq commented Dec 3, 2015

Didn't notice that there is another repo for clink competitions, I'll move this issue to proper place then.

@koteq koteq closed this as completed Dec 3, 2015
@vladimir-kotikov
Copy link
Contributor

@TheKoT, the issue exists already (vladimir-kotikov/clink-completions#36) and fixed 😄

@koteq
Copy link
Author

koteq commented Dec 3, 2015

@vladimir-kotikov, aye, thank you, I've already updated to latest version of clink-completions manually.

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

2 participants