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

Support for github.dev and vscode.dev #304

Closed
knu opened this issue Dec 1, 2023 · 1 comment
Closed

Support for github.dev and vscode.dev #304

knu opened this issue Dec 1, 2023 · 1 comment
Labels

Comments

@knu
Copy link

knu commented Dec 1, 2023

Description and repro

Thanks for this amazing piece of software! I've been using it every day and recently started to wonder if it is possible for GhostText to support github.dev and vscode.dev.

I can imagine that VS Code Web browser edition has complicated internals that may prevent GhostText from working without special treatment, but when I try to activate GhostText on github.dev (you could use https://github.dev/fregante/GhostText/blob/main/readme.md as an example) it at least detects the text area and says "Connected! You can switch to your editor". However, there seems to be no sign of any new file opened on the editor. I tested with VS Code with the GhostText Official extension and Emacs with the atomic-chrome package.

Browser(s) tried

Chrome, Edge

Editor(s) tried

VS Code, Emacs

@knu knu added the bug label Dec 1, 2023
@fregante
Copy link
Owner

fregante commented Jan 3, 2024

The field or field.value is not available it seems:

Screen.Recording.mov

This is likely the same issue as #283, which also uses Monaco editor internally.

In any case, I don’t think this use case should be supported for a few reasons:

  • you can already natively connect those pages to your own local editor (VS Code)
  • that editor in the browser is already fully-featured, GhostText brings only a little improvement
Screenshot 2

If your preferred editor is emacs, it looks like there are other solutions too:

@fregante fregante closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants