Skip to content
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

Merged
merged 4 commits into from
Dec 22, 2021
Merged

scala support #16

merged 4 commits into from
Dec 22, 2021

Conversation

SCdF
Copy link

@SCdF SCdF commented Dec 17, 2021

No description provided.

README.md Outdated Show resolved Hide resolved
@@ -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.
Copy link
Author

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

Copy link
Member

@pokey pokey Dec 17, 2021

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

Copy link
Member

@pokey pokey left a 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

README.md Outdated Show resolved Hide resolved
@@ -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.
Copy link
Member

@pokey pokey Dec 17, 2021

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

SCdF and others added 3 commits December 17, 2021 15:03
Co-authored-by: Pokey Rule <pokey.rule@gmail.com>
@SCdF
Copy link
Author

SCdF commented Dec 21, 2021

okey dokey this is ready to go @pokey when you are

@pokey pokey merged commit 5c64acf into cursorless-dev:main Dec 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants