-
Notifications
You must be signed in to change notification settings - Fork 0
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
Docs regarding Cmder integration #12
Comments
Moved from cmderdev#15 here: A couple of issues : •
This workaround currently isn't needed, but the official VS Code documentation mentions it, which means we have to make sure • There is the issue of Cmder being designed with ConEmu in mind, as stated by @daxgames. IMO we need to extend the logic of Cmder to be able to work without ConEmu. This means extended • Hyper at the moment has some issues for These require porting configuration including the tasks, path and monkai skin to the Hyper, VS Code and other Terminal hosts/IDEs. Most of these currently exist and is doable, but hey the sole purpose of Cmder is to gather them all and put 'em in a repo, otherwise what's the point of it? 😁 – and putting them in the repo is exactly what I plan to do. So, if Cmder is able to run on ConEmu, Hyper and VS Code with the same or near the same user-experience, I intend to make it happen, document each step (especially for newbies, or users who just aren't comfortable spending time to configure it themselves) – which should be easy to follow and work, and link them on the main website. |
Hopefully these will be merged into th Wiki as discussed in cmderdev/cmder#1751. |
I'm working to make sure Cmder runs as well in Hyper and VS Code as it's running in ConEmu, so I'll document them on the website. With the Zeit team incorporating
xterm.js
into Hyper, it'd work as great as VS Code.The text was updated successfully, but these errors were encountered: