-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
scala support #16
scala support #16
Conversation
@@ -41,7 +41,7 @@ When working with WSL, the host vscode instance connects to a vscode server on t | |||
|
|||
- Install the `pokey.command-server` extension on the host vscode | |||
- Clone the extension in the WSL side. | |||
- If you're adding language support to `vscode-parse-tree`, you need to clone that as well, build it, and link it into the `vscode-server` extension folder: `ln -s ~/.vscode-server/extensions/vscode-parse-tree ~/git/vscode-pars-tree` for instance. | |||
- If you're adding language support to `vscode-parse-tree`, you need to clone that as well, build it, and link it into the `vscode-server` extension folder: `ln -s ~/your/code/vscode-parse-tree ~/.vscode-server/extensions/parse-tree` for instance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get this wrong literally every time I use ln -s
, glad to see I'm not the only one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fwiw the way I remember it is that it's the same order as mv
or cp
: source to destination
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; will pull it locally to test and then release it alongside #15
@@ -41,7 +41,7 @@ When working with WSL, the host vscode instance connects to a vscode server on t | |||
|
|||
- Install the `pokey.command-server` extension on the host vscode | |||
- Clone the extension in the WSL side. | |||
- If you're adding language support to `vscode-parse-tree`, you need to clone that as well, build it, and link it into the `vscode-server` extension folder: `ln -s ~/.vscode-server/extensions/vscode-parse-tree ~/git/vscode-pars-tree` for instance. | |||
- If you're adding language support to `vscode-parse-tree`, you need to clone that as well, build it, and link it into the `vscode-server` extension folder: `ln -s ~/your/code/vscode-parse-tree ~/.vscode-server/extensions/parse-tree` for instance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fwiw the way I remember it is that it's the same order as mv
or cp
: source to destination
Co-authored-by: Pokey Rule <pokey.rule@gmail.com>
okey dokey this is ready to go @pokey when you are |
No description provided.