Install MacTeX which will include every package, and work.How nice! On MacOS, however, your options are to either accept bloat or tedious, tedious pain. If you’re on Windows, you can simply use MiKTeX, and any dependencies will be automatically downloaded as you need them. At the time of this article, there are 5,178 packages available for download depending on the functionality you want. That being said, LaTeX (and its parent, TeX) is a relic of times past. (If you’re still using Microsoft Word to do formulas, please stop.) It’s used in the first sentence in this paragraph to display the logo, and it is probably what was used to write any research paper that you have run across containing a formula. But just in case you’re not quite sure, LaTeX is the industry and academy standard for typesetting technical documents. If you’re here, you probably know what \(\LaTeX\) is. All I want to express in this post is that when you are in trouble, you may try to upgrade first.Installing (La)TeX on Mac, the Sane Way Aug 21, 2016 Newer versions may have new bugs or changes that you hate. This is not necessarily a good choice or the right thing to do, and I don’t have evidence about whether newer or older versions are better or worse in general. Personally I prefer using the latest versions of software packages, and I upgrade whenever possible (kind of obsessive), because I don’t want to run into old bugs that have been fixed. Go to the Start menu, find MikTeX, and click any buttons that sound like “update me” (clicking buttons and seeing what happens). Still in doubt? Run fmtutil-sys -all, whatever it means (again, may require sudo, depending on where you installed LaTeX).įor Windows users, updating MikTeX may require you to update both LaTeX packages and refresh the filename database (whatever it means). When in doubt, tlmgr update -self -all (requires sudo on macOS). For macOS users, MacTeX seems to be fine. Then you can enjoy (or suffer from) tlmgr instead of waiting for years for the official repo to have a recent version of TeXLive. 4 I’m not going to rant more, but just point out that updating LaTeX (and LaTeX packages) could be trickier than you imagined.įor Linux users, I recommend installing TeXLive from source and either add the bin path to PATH or sudo tlmgr path add. Almost everything is painful on every platform. 3 I dislike the installation, maintainence, syntax, and debugging process of LaTeX. LaTeX: I think everybody knows that I dislike everything about LaTeX except the PDF output. This is something I have waited for long, and I think the future of Homebrew R is brighter than the CRAN binaries of R and R packages. I’m seriously looking forward to Jeroen’s project on building R packages with Homebrew. 2 It is so awesome and convenient, and is exactly how I expect how system package manager to work: allow the community to help manage packages via Github pull requests. Homebrew is one of the two most important reasons why I switched from Linux to macOS a few years ago. It is a conservative choice, which may waste you a few more minutes to reinstall packages that actually still work well under the new version of R, but I prefer safty over time. from R 3.3.x to 3.4.0), but don’t worry, the solution is simple: update.packages(ask = FALSE, checkBuilt = TRUE) This can cause you (serious) problems after you upgrade R because some old R packages can be broken (e.g. This means all versions of R will use the same library path, e.g., R_LIBS_USER=~/R. For example, when you set R_LIBS_USER in ~/.Renviron, do not include the version number %V or %v. R and R packages: Unless you are a developer who cares a lot about different versions of R and has to install multiple versions of R, 1 do not use or configure a versioned library path for R packages. You may replace “Changing Stuff” with “Upgrading Stuff” above.Ī few notes from my personal experience just for your reference and also for my future self ( not meant to be a guide): Although it sounds like a joke, actually has a very good point: It is even more helpful if you could also install the development version of the software and see if the problem has gone. It is a little exaggerative and certainly not a universal rule, but it helps a lot if you could try to upgrade everything before you report a software issue. I have said this many times in several Github issues and it is also the very first FAQ of knitr.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |