quarto-dev / quarto-dev/quarto-cli

open a quarto web project on internal network harddrive fails

Open
#1,774 7 comments 0 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since Aug 11, 2022.

bug file-systems windows
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

hello,
In office, I have an rdp windows server.
when I open a quarto web project on the local server everything is fine but when I try to open a quarto web project
on another hard drive where data should be stored RStudio fails to create the .yml, .qmd and .css files. only the .Rproj file
is created and there is an error that says the system can not find the file specified.
so, for now we can't use the quarto projects outside the hosting server of the RStudio session.
The server is new and I'm installing everything from scratch, so everything is updated.

quarto check Output

No response

quarto tools check Output

No response

Checklist
  • formatted your issue so it is easier for us to read?
  • included a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • documented the quarto version you're running, by pasting the output from running quarto check in the "Quarto Check Output" text area?
  • documented the version of the quarto tools you're running, by providing the output from running quarto tools check in the "Quarto Tools Check Output" text area?
  • documented the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • documented which operating system you're running? If on Linux, please provide the specific distribution as well.
  • upgraded to the latest version, including your versions of R, the RStudio IDE, and relevant R packages?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.