-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Hyper CLI #2288
Comments
I spent some time to figure out how to do this. And here are my thoughts. TL;DR Embedding How VSCode works?
Javascript CLI-ToolAfter an amd-boostraping in src/cli.js (copied to This entry point is responsible to parse args and to intercept/deal with some options like Shell commandHow shell can execute this javascript file The right command is moved at build time to PathHow these scripts can be found by shell? macOSAt run time, when user executes the dedicated command in WindowsAt installation time (InstallShield), DebianAt installation time, How to achieve that in Hyper?CLI toolWe should the same as PathI didn't find how to modify user PATH in a postinstall step with |
Due to directory organization on Windows, we should unlink old path and link new path after each update. |
Sounds like a plan @chabou 👍 |
@chabou I like it 👍 |
Looks good to me! Thanks @chabou ❤️ But to be clear, the command will be called What I'm not sure on is whether or not we should also release the CLI on npm. But I don't think that makes any sense. Because even if people want to use it outside of Hyper, they can just do that, because it's in the However, it might make sense when it comes to keeping it updated. I could imagine that some people might want to have a fresher version of Hyper CLI than the one their Hyper comes with. But all in all, I don't think that's a great idea since other versions of Hyper might support different configurations, etc. - so having a independently updated CLI doesn't sound good to me. So feel free to add any additional opinions on that, but I think we should only have it inside Hyper (like @chabou suggested - no npm package). |
@leo I'm totally agree with you and thank you for your clarification about As explained, we'll need to ship different boostrap script that depend on platform. Until now, we have managed to not have a build script and to only depend on If we need a build script: |
That's easy! Options like these (look close, there are several different ones on this page - one of them will definitely work) allow us to copy files over to a directory of our choice in the bundle.
I used this property in my electron-next-skeleton example project... 😊 |
OMG... How could I miss this 😱 ??!! Thanks for your input @leo ❤️ |
Any chance the Hyper CLI will let you create new tabs in Hyper that are started with arbitrary shells/arguments? |
That sounds like a great idea @elijahgagne, not in the first release but after that I don't see a reason not to. PR's welcome 🤗 |
Great idea yes. With first release it will only be possible to create new tab with a specified path: |
Fixed by #2375 |
Awesome work with the CLI! This issue is resolved. Let's open new ones for future development of it |
As started in #282, we will in 2.0 have a way to manage hyper via the CLI.
The text was updated successfully, but these errors were encountered: