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

Find a way to track UUIDs on VS Code editor objects #13

Open
phillco opened this issue Oct 8, 2022 · 0 comments
Open

Find a way to track UUIDs on VS Code editor objects #13

phillco opened this issue Oct 8, 2022 · 0 comments
Labels
splits For supporting splits

Comments

@phillco
Copy link
Member

phillco commented Oct 8, 2022

For splits, we're currently planning to use the editor path as the primary key for now, but eventually we would like to support having the same file open in multiple splits.

To do this most reliably, we will need to have UUIDs to represent editors that would be the same on both sides. Storing this information should be pretty trivial on the Emacs/JetBrains side, but we need a way to do so inside of Visual Studio Code.

@phillco phillco added the splits For supporting splits label Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
splits For supporting splits
Projects
None yet
Development

No branches or pull requests

1 participant