-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Tlmgr returning error in Linux #1
Comments
You need to It seems that |
I appreciate a clear mention of this in docs. I haven't tried it yet. Once, I tried it and confirm I will close this issue. |
To be honest, this is the first time I have discovered it over the several years of using |
Yes, what you said worked. I tried the below command and it worked without any errors. cd .TinyTeX/bin/x86_64-linux && ./tlmgr path add |
If you want to install TinyTeX on Linux, you can use the method here: https://yihui.org/tinytex/#installation which essentially runs this script: https://github.com/yihui/tinytex/blob/master/tools/install-bin-unix.sh |
I am closing this as this is fixed. Also, why not publish to |
That might be a good idea, but I'm not interested in it. Users have too little freedom with a Debian package (which may make sense for other packages but not for TeX Live in my opinion): https://yihui.org/tinytex/pain/ If I were to make this a package at all, I'd probably consider Homebrew instead (which works for both macOS and Linux), so users can |
I downloaded https://github.com/yihui/tinytex-releases/releases/download/v2020.09/TinyTeX-1.tar.gz in Linux.
I extracted it using the below command
tar -xvzf "TinyTeX-1.tar.gz"
At first, I could find my extracted folder. Later I found it was
.TinyTeX
(Hidden). Then I wanted to create symlinks to start using it. So I typed the below commandThen it returned a weird error.
Looks like the way it was build was the issue. I think @yihui . Could you try and verify whether this works?
Here, I attached a Google Colab copy of what happened.
https://gist.github.com/naveen521kk/3fe9f54a4e82efef97903a272380e541
Note: Their all bash command should start with
!
.The text was updated successfully, but these errors were encountered: