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

Suppress: "The editor could not be opened due to an unexpected error" #217

Open
edreamleo opened this issue Oct 6, 2021 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@edreamleo
Copy link
Collaborator

edreamleo commented Oct 6, 2021

I get this message during startup. It goes away after the server starts. Yes, this message is a nit, but imo, it would be smoother not to see this message.

Apparently this is a vs-code error. No part of the error message appears in leoInteg itself.

@edreamleo edreamleo added the enhancement New feature or request label Oct 6, 2021
@boltex boltex self-assigned this Oct 26, 2021
@boltex
Copy link
Owner

boltex commented Aug 27, 2022

Yes, those opened panels stating the last body pane address can not be opened, is a remnant of the last leointeg session that vscode tries to reopen. but the leo-body filesystem has not started yet...

The new leointeg 1.0.8 now closes those old panels upon startup.

I'll try to make sure i remove that last opened body pane from the vscode's 'recent documents list' on the 'vscode-is-closing' event, so that it does not try to open it on startup.

I'll comment more on this after doing some more tests and verification about that issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants