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

Don't default to exporting HTML and PDF files to the root (/) directory of the user's machine #3991

Closed
SiddhanthUnnithan opened this issue Nov 20, 2020 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@SiddhanthUnnithan
Copy link

Currently when you export to PDF or HTML, the location of the exported file is the root of the user's machine (e.g. /filename.pdf)

Users working on remote hosts (e.g. Azure ML compute, Azure VM) are sometimes unable to write to the root of their host. They have to manually change the export path to a directory that they can write to.

Ideally the exported path defaults to either the root of the user's workspace, current working directory, or the directory in which their Notebook is in.

@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Nov 20, 2020
@DonJayamanne
Copy link
Contributor

DonJayamanne commented Nov 20, 2020

Bug - as this breaks simple HTML in AML (the export doesn't work with default directory & it needs to be changed to workspace) - could be permissions or the like.
Either way, not the best default experience even though there's a work around (not obvious either)

@greazer
Copy link
Member

greazer commented Nov 30, 2020

This more seriously affects remote scenarios.

@IanMatthewHuff
Copy link
Member

Validated. Didn't default to Mac home directory anymore and tested from Native Notebooks, old webviews, and custom editors.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

5 participants