Closed hasparus closed 4 years ago
Noob question here. How can I quit huncwot? I tried Ctrl+C, Ctrl+D, :q
.
@hasparus Awesome!
Regarding the port problem, I simply forgot about it. :) Thanks for this!
I imagine you start on CLI with huncwot start
. In that case, it starts a tmux
emulation using stmux. By default, the trigger key is CTRL-a
. If you try CTRL-a ?
, it will show you all commands available. However, this package has some issues with properly handling the kill signal.
In long term, I wanted to rewrite it from scratch, as it's just a thin layer on the blessed (an ncurses equivalent in JavaScript). We don't need the full tmux experience here, just a vertical split. This way it would be simple.
Also, in the recent Huncwot version, there is a better integration with VS Code. I'm thinking about deprecating this huncwot start
in favor in VS Code. If you generate a project, it creates a .vscode
directory with a predefined set of commands to start and manage Huncwot apps directly from VS Code. You need to trigger the Run Tasks
from the command palette. I have bound this to CTRL-T
in my private config for convenience and then select Start
to start both the server and the client, or Server
/ Client
to start each part separately.
There is still a lot of things to improve here. I appreciate your help!
Wow, this is such a pro answer 😍 What did you use to record the screencast?
Well, I tried ctrl+b+x but I understand why the activator character needs to be different than tmux's. Then I just closed the window.
So it is ctrl+a+k. Thanks!
Hey 👋
I've just generated new huncwot project and encountered a mismatch between README and what happens. I believe that the port comes (leaks?) from the defaults of rollup-plugin-serve.
A long term fix might be to override the port in /config/client/rollup.config.js#L27.