I have installed texlive in ubuntu 20.04 using sudo apt-get install texlive-full. But it's TeX Live 2019 which is not the latest version of texlive. Is it possible to update the latex packages to their latest versions?

~$ tlmgr --verify-repo=none update --all
(running on Debian, switching to user mode!)
TeX Live 2019 is frozen forever and will no
longer be updated.  This happens in preparation for a new release.

If you're interested in helping to pretest the new release (when
pretests are available), please read tug.org/texlive/pretest.html.
Otherwise, just wait, and the new release will be ready in due time.
tlmgr: package repository tug.org/historic/systems/texlive/2019/tlnet-final (not verified: gpg unavailable)

@raf Not without a bit of pain. I recommend you install the vanilla TeX Live instead: tug.org/texlive. Works like a charm

I am confused. Why doesn't give apt-get provide the updated version?

@raf This happens for everything you install with apt-get: it gives you a frozen version at the time your version of Ubuntu was released.

oh

before installing "vanilla", I need to uninstall the current one, right?

Should I follow this procedure: tex.stackexchange.com/a/95373/114006 ?

@raf I think I had once the packaged version installed along with vanilla without problems, but I'm not completely sure

@raf Yeah, that's the one

 :58570178 in the answer, it is said to do:
      export PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH
      export INFOPATH=$INFOPATH:/usr/local/texlive/2021/texmf-dist/doc/info
      export MANPATH=$MANPATH:/usr/local/texlive/2021/texmf-dist/doc/man

but I forget to do it, the installation of the packages has started. What can go wrong for not using the 3 command lines?

while installing vanilla tex live, I have got this error:

Installing [4214/4214, time/total: 02:17:40/02:17:51]: zztex [147k]
Retrying to install: easybook [593k]
TeXLive::TLUtils::check_file_and_remove: checksums differ for /tmp/u9n3YhMSp1/XnjetrUXQk/easybook.tar.xz:
TeXLive::TLUtils::check_file_and_remove:   tlchecksum=24dda9b13cefffedcc080643cea6082506f190f286eec442f2484bc40712db94a80891787a82ed9a7cda5d63ec006a5067970e75df945017240924736336ada7, arg=2aa281a24c43a74a7013f42f00a5664b6a7be94f810f76095aac5ec31a4f3960a4fc49ccdf126f8d650e263e60f8e80359b070a9e6e3fd55933dd91511af349a

What should I do now?

@raf No, don't do that unless you are worried about the disk space waste

I just install a "portable version" under my home dir, and then prepend the binary directory to the path @raf

@raf if you remove the apt-installed packages the rest of the system thinks you do not have LaTeX installed. You can use fake-packages, but that's a pain in the back. So I normally have both installed (hard disk is cheap).

@raf A lot of things, because now for example when you call tlmgr you will use the "stock" one instead of the old one. Believe me, installing a portable version in your home dir is much easier.

old -> new in the message above. Sorry

Now, I want to have a fresh install of vanilla texlive.

@raf What I did is following the instruction to install a portable texlive: tug.org/texlive/doc/texlive-en/texlive-en.html#tlportable in ~/texlive2021. After that, I just added this in my .profile (code following):

function select_texlive {
        TEXDIR=$(realpath $1)
        if [ ! -r "$TEXDIR/texmf.cnf" ]; then
                 echo "$TEXDIR is not a TeXLive portable root!"  1>&2
        else
                platform=$($TEXDIR/install-tl --print-arch)
                export PATH=$TEXDIR/bin/$platform:~/bin:$PATH
                export MANPATH=$TEXDIR/texmf-dist/doc/man:$MANPATH
                export INFOPATH=$TEXDIR/texmf-dist/doc/info:$INFOPATH
                export TEXMFHOME=$HOME/texmf
                export TEXDOCS=$(kpsewhich -var-value TEXDOCS | sed 's%,/home/romano/texmf%%' | sed 's%{}%{}…

@DavidCarlisle oh no

@Skillmon @barbarabeeton twitter.com/rabbitdoingwork/status/1413220025918492674

@DavidCarlisle twitter.com/capuanogio/status/1413246808575385606?s=19

@Rmano I'm not sure whether the TikZ subpath-thingy is worth developing. I don't see much of an advantage over pics (except for the pseudo-anchor stuff, but that's something I can create with pics as well: tex.stackexchange.com/questions/185279/anchoring-tikz-pics)

@Skillmon yes, I'm also doubtful. For normal circuits usage, what I have is sufficient, although having parameters for labels etc would be nicer (but I have a simple workaround in the manual, so it's not a show-stopper)

BTW I forgot to make the macro protected, will do in the next step. Do you know if there is a kind \pgfutil@protected@def which is format-independent? Just if you know it already, otherwise I'll look around later

I wonder if one could train arxiv.org/abs/2107.03374 with xii.tex :)

Has anyone tried out atom.io with linter-spell-latex to spellcheck multilanguage latex files? I wonder whether this editor would be of any help to parse babel's \foreignlanguage and switch the spellchecking dictionary accordingly. And how about “Spell Right” for Visual Studio?

Or, is there ANY spellchecker for LaTeX at all (except Heslin's old flyspell-babel.el and ispell-multi.el which I never managed to get to work and which seem to got defunct as emacs evolved) that can parse babel's \foreignlanguage (and, preferrably, \otherlanguage) commands and switch the dictionary accordingly?

@GeekestGeek In emacs, one can actually use polymode for this to set up multiple LaTeX environments for different languages and switch when encountering babel environments (I needed language-based switches in a larger documents so I only implemented it for the environments, surely one could use something like this for commands as well). But that's probably overkill for switching only dictionaries.

@TeXnician Thanks. Do you mean the otherlanguage environment? I have 5 of them spread around two .tex files. As for \foreignlanguage, I have a total of 231 of them spread around 46 .tex files.

@GeekestGeek Yes, I only used that environment back then when I implemented a setup with different LaTeX setups per language. That is very easy to realize using the polymode emacs package. I don't actually know if you can switch major modes (which is what polymode internally does) within a line so I don't know if one could apply a similar approach to the commands. But given your numbers you should probably look into a solution that focuses on a solution that prioritizes the commands.

@TeXnician Given polymode.github.io/usage, I see that it provides commands for navigating between various portions of the text and doing something to them I don't quite understand. As opposed to this, I wish to invoke only a few commands similar to the current spellchecking ones; e.g., we can name them ispell-multilingual-buffer, ispell-multilingual-region, and ispell-multilingual-continue. Even for otherlanguage only, do you think polymode would be the right tool to do this?

@GeekestGeek Well, no, even for otherlanguage only, polymode would treat each otherlanguage environment as a separate block so you could benefit from per-language underlining/other highlighting (which would be what a snippet within polymode could look like when flyspell is enabled) but commands run on the whole buffer would not properly take the polymode changes into account so for these it would not work properly. Sorry, I misunderstood the use case here (I rarely use the flyspell commands).

@TeXnician Ah, I see. I've never used flyspell-mode so far (except when trying to make Heslin's old packages work), but I could try again if it helps. What I find disturbing about flyspell-mode is that it underlines all my tikz stuff red whenever I click into a tikz environment (since my main document language is NOT English), whereas ispell commands somehow skip most of tikz. So, with flyspell-mode, I get distracted by the red underlining.

@GeekestGeek Yes, that's one major problem with flyspell and LaTeX editing. It's one reason why I do not turn it on most of the times. Unfortunately, I'm out of ideas but I wish you good luck looking for a solution and maybe you could post it as a Q&A on the main site when you found something that works, would definitely be interesting :)

@TeXnician Thanks anyway! As of now, it would be not a Q&A but rather a plain Q. :-) I asked the maintainer of babel via e-mail; maybe they are aware of something usable. As for now, I experiment with the “atom” editor, and I look into how to turn linter‑spell‑latex on.

@PauloCereda -- Poor bunny!

I followed this procedure: tex.stackexchange.com/a/95373/114006

Now, when I command:

sudo tlmgr update --self

It shows:

sudo: tlmgr: command not found

@raf then you have not set your PATH to include the texlive bin directory (or rather you have not set the path used by sudo)

how should I set it?

@raf do not change the "sudo" path.

sudo /complete/path/to/vanilla/tlmgr update --self will work

@Rmano why?

@Rmano it would but only if you are sure that tlmgr never executes any process called by its path, eg sudo /complete/path/to/vanilla/pdflatex myfile may or may not work depending if pdflatex decides to call epstopdf or maketfm or any other script. Seems safer to add it to the sudo path (or install texlive as non-sudo) in a use directorry

@DavidCarlisle yes, that's true, you're right.

This is one of the reasons why I prefer to install locally.

@raf well, I normally prefer doing the least possible changes to root shell configuration.

@Rmano as this is a single user machine I gave myself write access to /usr/local/texlive so then do a non-sudo default install under my account

@DavidCarlisle Probably a better strategy, yes.

In /home/username/.bashrc:

export PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH
export MANPATH=$MANPATH:/usr/local/texlive/2021/texmf-dist/doc/man
export INFOPATH=$INFOPATH:/usr/local/texlive/2021/texmf-dist/doc/info

@raf as it says in the answer I just linked to sudo PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH tlmgr update --self should work

still not working

@DavidCarlisle ;-). But as you removed your comment I better remove mine too.

@UlrikeFischer wasn't fair on the new user really. And anyway you are not supposed to be mean to old people.

@DavidCarlisle what else can I do to fix this issue?

@raf say what the issue is: "not working" does not give many clues.

@DavidCarlisle oh, thanks for the reminder, you got mail.

~$ sudo PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH tlmgr update --self
[sudo] password for raf:
sudo: tlmgr: command not found

do it in stages to test sudo su then you will be root then export PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH then tlmgr update --self

@raf it could be that sudo is set up to filter out PATH changes, you know, security. Try sudo -i, you'll have a root prompt, then ` PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH tlmgr update --self` (remember to exit when finish)

@PauloCereda Ping?

@AlanMunn ooh pong (just a minute)

@PauloCereda ping (you got a week)