rstudio/tufte

nul file

schneiderpy opened this issue · 7 comments

Hello,

a few days ago I installed a few new r packages to improve my r skills while doing a new project (ebook).
I decided to install: bookdown, tufte, tufte handout and pandoc on my Windows 7 pro notebook. After installing and some trying to set up an ebook (I used the tufte template file) I wanted to delete an older folder, but was not able to do so. Instead, it appeared an error message: "MS DOS function not valid". After two painful days of searching in the web I came across a comment on stackoverflow that the issue might be a nul file. It is not possible to delete that file even in the R studio environment. I deleted everything except the tufte package and started again. Today I found out that this nul file is been created while knitting / rendering to pdf / handout.
Probably not a big bug, but pretty annoying ..


By filing an issue to this repo, I promise that

  • [x ] I have fully read the issue guide at https://yihui.name/issue/.
  • [x ] I have provided the necessary information about my issue.
    • If I'm asking a question, I have already asked it on Stack Overflow or RStudio Community, waited for at least 24 hours, and included a link to my question there.
    • If I'm filing a bug report, I have included a minimal, self-contained, and reproducible example, and have also included xfun::session_info('tufte'). I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version: remotes::install_github('rstudio/tufte').
    • If I have posted the same issue elsewhere, I have also mentioned it in this issue.
  • [ x] I have learned the Github Markdown syntax, and formatted my issue correctly.

I understand that my issue may be closed if I don't fulfill my promises.

cderv commented

Hi,

Thanks for the report. I am glad someone report this - It happened to me in the past but I thought it was something with my system. It seems it is not. It was not specific with tufte though and it was link to TeX Live and its usage with tinytex package.
Also I am using the TinyTeX distribution.

Workaround for me was to use bash (e.g git bash) to run a rm -f nul so I could remove the file named nul

However, I don't encounter this anymore so I was not able to reproduce, and I still can't even with tufte. The only thing that have changed for me is an update to the package tinytext and to the TinyTeX distribution.

Is this something you can do ?

I will look out for next time I am encountering this and look into this closer. Thanks !

Hello,
merci for the prompt reply.

Of course it is possible that this issue is caused by TinyTex and the tinytex package (I am not an expert), however, I have already used TinyTeX (and also MiKTex) in combination with the tinytex package to render an rmd to a normal pdf, however, I could not (and still can't) find any nul file ..
I was able to delete the nul file with git bash here...
What package /distribution versions are you using? (tinytex ver. 0.36)

cderv commented
packageVersion("tinytex")
#> [1] '0.36'
packageVersion("rmarkdown")
#> [1] '2.11.4'
packageVersion("knitr")
#> [1] '1.37'
packageVersion("tufte")
#> [1] '0.10'

But as I said I can't reproduce this anymore. I had the nul file in the past and now does not have it. So maybe a new version of TeX Live fixed this.

Do you still have this with tufte ?

Hello,
yes, I still have the same bug issue .. (yesterday and today again). It doesn't occur all the time .. but this time I paid attention when rendering the document (tufte handout). I accidently wrote Pericle (instead of Pericles), so the rendering process interrupted and the nul file appeared (Name: nul; Size: 0B; Modified: Dec. 31, 1969, 9:00 p.m). This time a made a copy of the log file and sessioninfo (see attached).
sessioninfo_040122.txt
erm.log

cderv commented

Thanks that is helpful information ! I'll look into this.

cderv commented

I'll close this and we'll follow in rstudio/tinytex#354

It seems it was an issue in TeX Live.

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.