cmderdev / cmderdev/cmder

[Feature request] Allow terminal to accept and run commands before cmder is fully loaded

Open
#2,915 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🛠 Type: Feature Request
Dominant language
PowerShell
Stars
27k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Description

Suggestion

I am on Windows and the work computer I am using is really old and slow. Like CPU at 100% utilization 24/7 kind of slow.

I have integrated cmder with vscode and whenever a new instance is created it can sometimes take up to 30-60 seconds before I am able to type commands. Usually this is about 10 seconds which I can deal with.

I'm not sure if it is technically feasible, but it would be nice for the terminal to accept input immediately and execute them in an underlying cmd prompt (or something of that nature) while cmder is still loading so that basic commands like "cd" and "npm run xyz" can still be executed while clink is being injected and other features are being initialized. Most of the time when I open a new terminal, I am running the same 3 commands over and over and not using all of the features, but I can't even type anything until it has fully loaded which can take a very long time as mentioned above. #2816

As an alternative maybe allow the terminal to accept commands immediately but they instead enter a queue until its loaded and ready. I think either one would make the performance issues less frustrating.

Use case

No response

Extra info/examples/attachments

Cmder Full (with Git)
cmder Version 1.3.24.236
clink 1.6.1.c7c448
git version 2.41.0.windows.3

Windows 10 Enterprise 21H2
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz 1.90 GHz
RAM: 32.0 GB
1TB SSD

Antivirus: Trellix

vscode_init_args.txt

Checklist
  • I have read the documentation and made sure this feature doesn't already exist.
  • I have searched for similar issues and found none that describe my feature request.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the VS Code integration context and attached vscode_init_args.txt, then trace the startup sequence around clink injection and feature initialization. Define whether input should execute through an underlying cmd prompt or queue until loading completes; done means basic commands can be entered without waiting for full initialization.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell, vscode
Domain
cli, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.