-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Knit RMarkdown to PDF not working #82
Comments
Interesting. If you don't have the internet connection, how did you install TinyTeX? Are you behind a proxy like #81? |
Yes, i have the same problem like #81, but i am not allowed to use a flashdrive. |
So your sysadmin/IT installed TinyTeX for you? |
No, i installed TinyTeX. I used tinytex::install_tinytex(), but this provides tinytex:::is_tinytex() <- False. |
Ok, i solve the problem: And now it is working... |
... but i would like to use the xcolor package on my working-computer. How can i do it without admin-rights? If i use the xcolor package at my header-includes i get the same problem as stated above. Do u know any possibility without flashdrive yihui? |
@yihui Sorry to butt in but I suggested @DuGamla open an issue to try to resolve his problem, I tried testing AS Standard User (NOT admin NO proxy) I use portable R (should not be different in this case ?) tlmgr.pl: package repository http://anorien.csc.warwick.ac.uk/mirrors/CTAN/systems/texlive/tlnet (not verified: gpg unavailable) So I DO NOT have a problem, what is the key difference (I DO know I don't have a proxy) Questions so for example if user sees they need xcolor |
@GitHubRulesOK For users behind the proxy, it is possible to make TinyTeX work. It depends on if the proxy server can be accessed via a standard form like |
Thanks I was aware of that (and that it could be added to update scripts environment if known) So simple users need a very simple test to confirm it is a proxy firewalling their attempt to update I don't understand which protocol the initial install is used by R studio call (which seems to work for all users) but is NOT available for the tex wget to update without jumping through extra hoops I am not sure if there are any user right problems with %appdir% however since IT department gave the user right to the R studio directories could we benefit from moving Tiny Tex there as a subfolder? You say wget is using http does rstudio command tinytex::install_tinytex() use ftp ? I don't understand why there may be a proxy difference between tinytex:::install and TLmgr update ? I don't want to go down the route of unpackaging ctan files to texmf, I would like to just tell them where the latest package that Tiny Tex calls can be downloaded and where to add to users TinyTex folder (as if it had been fetched) so it can be installed by simply running recompile For a few packages it is possibly the easiest solution rather than upset the company IT guys. (if it is a larger number then best to have IT department involved, that's is what they are paid for) |
I guess what i'm looking for is something that expands the install to include xcolor like this how does the extra packages work ? tinytex::reinstall_tinytex(packages = TRUE, dir = tinytex_root(), repository = "ctan", extra_packages = xcolor) |
For others coming to this thread.
I ran into a similar issue as reported by @DuGamla above. I work on a windows X laptop. When knitting the Rmd file to pdf, I ended up with
Going back to the R console, I could launch
which ran nicely echoing the following:
I had to do this for the following packages (xcolor, multirow, wrapfig, colortbl, pdflscape, tabu, varwidth, threeparttable, threeparttablex, environ, trimspaces, ulem, makecell, epstopdf-pkg). I know too little about how this all works, however, I have the feeling that the attempt to install the packages automatically might have a typo in the repo address or something like this. In my case installing the missing packages by hand was ok, although I would have loved to be able to avoid the tedious process: (i) knit --> check error for missing package (ii) install by hand and go back to (i). |
Still no joy: Unable to install tlper.win32 tlmgr.pl: Fundamental package tlperl.win32 not present, uh oh, goodbyeShould not happen, tlperl.win32 not found at C:\Users\Robert\AppData\Roaming\TinyTeX\texmf-dist\scripts\texlive\tlmgr.pl line 7439. |
Thanks! Was running OS X Monterey 12.2 and R 4.1.2 plus the latest version of R Studio with all other packages up to date, thinking everything would simply be fine, and then this cropped up. A project that would ordinarily knit to PDF quickly started to take hours to knit, then it kept throwing back these errors, each time citing a seemingly random .sty file. Spent days looking for a fix, trying everything out there and nothing worked until the above. But as painful as it was (having to knit, wait an eternity, find the missing package, install manually, then repeat), this finally did the trick. Knitting still takes some time, but at least it generates a PDF. Everything worked smoothly before, so I'd second that notion that there's a glitch somewhere inhibiting the native process of searching for, finding and installing missing components automatically which could also account for why it takes forever to knit to PDF. Thanks again. |
I had similar issue, which was solved through your instruction. Thank you for sharing the solution. |
Hi yihui,
i have an issue with knit rmarkdown to pdf in RStudio. I am using TinyTex and try to knit following rmarkdown example:
Selection of "Knit to PDF" provides :
I am not using the xcolor-package anywhere... What can i do to fix that problem? I am an simple user on my work-computer (not an admin).
I see a possible solution at ur website https://yihui.name/en/2018/08/tinytex-flash-drive/. But I am not able to use Dropbox on my computer.
By the way: I started this thread at https://tex.stackexchange.com/questions/459113/problem-with-knit-r-markdown-to-pdf too.
The text was updated successfully, but these errors were encountered: