I have backups of my ~/.slickedit and ~/slickedit directories. My ~/.slickedit directory actually contains several past release configs (18.0.1, 19.0.[012], 20.0.[0123]). I install SE into ~/slickedit, letting the new installation upgrade.
However, as I mentioned, I have backed these directories up before the installation onto another machine with the same structure (cd ~; rsync -aSHP --delete .slickedit slickedit backupmachine:). I reverse it when I restore my environment back to a working 20.0.3 installation.
To reproduce the SE, from 20.0.3, I execute the following:
cd ~
tar xzvf se_21000002_linux64_beta1.tar.gz
cd se_21000002_linux64_beta1
./vsinst
After getting the previously reported complaints and apparently corrupt error messages, I finally get the installed license and attempt to execute vs +new -sc /tmp/config (as previously noted in this thread).
Neither the prior, nor the upgraded /slickedit/plugins/com_slickedit.base/language directory has a process subdirectory. But contains the following:
$ ls ~/slickedit/plugins/com_slickedit.base/language/
c/ coffeescript/ cs/ googlego/ java/ lua/ pl/ py/ ruby/ swift/
Moreover, the list ~/slickedit/plugins/*.cfg.xml (via 20.0.3) provides the following output (see attached text file as forum griped about too many characters), which I was able to successfully (and tediously) open all 188 files via the list command/enter with 20.0.3 SE.