Add support for inheriting Clink Profile from globally installed Clink
Open
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
Cmder should somehow recognize if Clink is already injected and inherit the profile path instead of using %CMDER_CONFIG_DIR%.
Use case
If Clink is injected globally on cmd, the history should available if using cmder while maintaining the the Cmder [rompt.
Extra info/examples/attachments
No response
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating Cmder’s handling of globally injected Clink and the %CMDER_CONFIG_DIR% profile path; done means the global Clink history is available in Cmder while the Cmder prompt remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100