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

auto create new file #2

Closed
tjx666 opened this issue Nov 20, 2022 · 3 comments
Closed

auto create new file #2

tjx666 opened this issue Nov 20, 2022 · 3 comments

Comments

@tjx666
Copy link

tjx666 commented Nov 20, 2022

chekweitan.compare-view: v0.9.0
Version: 1.73.1 (Universal)
Commit: 6261075646f055b99068d3688932416f2346dd3b
Date: 2022-11-09T02:08:38.961Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 22.1.0
Sandboxed: No
2022-11-21.02.08.12.mov
@tanchekwei
Copy link
Owner

Hi @tjx666 , that is the default behaviour when the new file gets dirty. But I am not sure why this behaviour didn't happen in VS Code for the Web https://vscode.dev/.

I have added a setting to close the new file after the compare view tab / diff tab is closed as a workaround. You can enable it after updating the extension.

close related tab setting

Since the file is dirty, a close confirmation dialog will show.

close confirmation dialog

@tjx666
Copy link
Author

tjx666 commented Nov 25, 2022

that is the default behaviour when the new file gets dirty. But I am not sure why this behaviour didn't happen in VS Code for the Web https://vscode.dev/.

@tanchekwei So, this may be a vscode issue ?

@tanchekwei
Copy link
Owner

@tanchekwei So, this may be a vscode issue ?

@tjx666 ya, I think so.

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

No branches or pull requests

2 participants