Hi, Again a new lmtx upload. As these days are all about counting and numbers ... of the 19K visible macros some 14K are now flagged. Question: do we really need all these 'named characters' or can we at some point ditch many .. I assume that users who key in greek and cyrillic use unicode nowdays (no hurry, just wondering). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On 11/6/20 8:42 PM, Hans Hagen wrote:
Hi,
Again a new lmtx upload. As these days are all about counting and numbers ... of the 19K visible macros some 14K are now flagged.
Many thanks for the new release, Hans. I’m afraid that I cannot update unless I remove tex/texmf*.tma. I’m on Linux-64bit and I wonder whether I’m the only user affected by this issue.
Question: do we really need all these 'named characters' or can we at some point ditch many .. I assume that users who key in greek and cyrillic use unicode nowdays (no hurry, just wondering).
As for Greek enconding, I never used anything else than UTF-8. Many thanks for your help, Pablo -- http://www.ousia.tk
On 11/6/2020 16:03, Pablo Rodriguez wrote:
On 11/6/20 8:42 PM, Hans Hagen wrote:
Hi,
Again a new lmtx upload. As these days are all about counting and numbers ... of the 19K visible macros some 14K are now flagged. Many thanks for the new release, Hans.
I’m afraid that I cannot update unless I remove tex/texmf*.tma.
I’m on Linux-64bit and I wonder whether I’m the only user affected by this issue.
Question: do we really need all these 'named characters' or can we at some point ditch many .. I assume that users who key in greek and cyrillic use unicode nowdays (no hurry, just wondering). As for Greek enconding, I never used anything else than UTF-8.
Many thanks for your help,
Pablo -- http://www.ousia.tk ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
Same problem on WIndows 10. I have taken to simply doing a fresh install to get updates. Minor frustration. -- Rik
Il 06/11/20 22:03, Pablo Rodriguez ha scritto:
I’m afraid that I cannot update unless I remove tex/texmf*.tma.
I’m on Linux-64bit and I wonder whether I’m the only user affected by this issue.
I can confirm that on my Debian 10 64bit: no update until I removed texmf-context.tma texmf-linux-64.tma texmf.tma in the tex subdir. Massi
On 11/7/20 12:02 AM, mf wrote:
[...] I can confirm that on my Debian 10 64bit: no update until I removed
texmf-context.tma texmf-linux-64.tma texmf.tma
in the tex subdir.
I had to remove these files to update from LMTX from 2020.10.20 to version from 2020.11.05. But I had to remove these files again to upgrade from 2020.11.05 to 2020.11.06. I wonder whether the same happens in Windows (I haven’t checked it yet). Just in case it helps, Pablo -- http://www.ousia.tk
this is my script for a daily update check which seems to do the job #!/usr/bin/env bash cd ~/context context --version | grep "current version" echo "------------" mtxrun --script cache --erase >ctx.log rm tex/*.tma sh ./install.sh >ctx.log context --version | grep "current version"
Hi Pablo, I had the same issue as the one you were reporting (on MacOS 10.14.6). I removed the three files texmf-context.tma texmf-osx-64.tma texmf.tma before issuing the command sh install.sh Now I am getting fetching 'http://lmtx.pragma-ade.com/install-lmtx//texmf-context.zip on my Terminal window and I think I will get the new version uploaded by Hans (my internet connection is very slow…). Thank you for the hint… Best regards: Otared
On 7 Nov 2020, at 00:12, Pablo Rodriguez
wrote: On 11/7/20 12:02 AM, mf wrote:
[...] I can confirm that on my Debian 10 64bit: no update until I removed
texmf-context.tma texmf-linux-64.tma texmf.tma
in the tex subdir.
I had to remove these files to update from LMTX from 2020.10.20 to version from 2020.11.05.
But I had to remove these files again to upgrade from 2020.11.05 to 2020.11.06.
I wonder whether the same happens in Windows (I haven’t checked it yet).
Just in case it helps,
Pablo -- http://www.ousia.tk ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
On 11/7/20 10:48 AM, Otared Kavian wrote:
Hi Pablo,
I had the same issue as the one you were reporting (on MacOS 10.14.6). I removed the three files
texmf-context.tma texmf-osx-64.tma texmf.tma
[...] and I think I will get the new version uploaded by Hans (my internet connection is very slow…).
Hi Otared, I don’t know which one, but I think the LMTX installer may have a bug that prevents updating the installation in all platforms (at least, it seems to be so in Windows, macOS and Linux). I thnk that removing the tex/texmf-*.tma files, allows a new installation. It may overwrite all files (modified or not). But it might be that this doesn’t remove deprecated files.
Thank you for the hint…
It was by pure chance that I discovered that this might work. But I’m glad to see that this may help, Pablo -- http://www.ousia.tk
Dear Hans, Would it be possible to have a simple text file with the latest release version (or date) tag in it? Next to the folder containing the actual install script files? In that case it is easy to check that version tag by comparing with the local copy and decide if a further download and install is needed. m.vr.gr. Floris
On 11/7/20 11:40 AM, Floris van Manen wrote:
Dear Hans,
Would it be possible to have a simple text file with the latest release version (or date) tag in it? Next to the folder containing the actual install script files? In that case it is easy to check that version tag by comparing with the local copy and decide if a further download and install is needed.
Dear Floris, I have a simpler approach that might help you: curl -I http://pragma-ade.com/context/latest/cont-tmf.zip I added a file with that to $HOME/bin/ and it works fine when invoking it. To check which version you have installed on your computer: export PATH=$PATH:$HOME/context/tex/texmf-linux-64/bin/ && context --version && luametatex --version Of course, you might need no export or adapt $PATH accordingly to your ConTeXt directory. Just in case it helps, Pablo -- http://www.ousia.tk
On 11/7/20 12:53 PM, Pablo Rodriguez wrote:
[...] I have a simpler approach that might help you:
Improved message: echo "" && curl -I http://pragma-ade.com/context/latest/cont-tmf.zip 2>&1 | grep Last-Modified && echo "" So you don’t mix access time with last modification. Just in case it helps, Pablo -- http://www.ousia.tk
On 07/11/2020 13:11, Pablo Rodriguez wrote:
Improved message:
echo "" && curl -Ihttp://pragma-ade.com/context/latest/cont-tmf.zip 2>&1 | grep Last-Modified && echo ""
So you don’t mix access time with last modification.
Just in case it helps,
That helps. Thx
On 07/11/2020 13:11, Pablo Rodriguez wrote:
echo "" && curl -Ihttp://pragma-ade.com/context/latest/cont-tmf.zip 2>&1 | grep Last-Modified && echo ""
So you don’t mix access time with last modification.
this seems to work: #!/usr/bin/env bash cd ~/context OLD=`stat -c "%w" context-linux-64.zip` echo "current: " $OLD curl -s -O http://lmtx.pragma-ade.nl/install-lmtx/context-linux-64.zip NEW=`stat -c "%w" context-linux-64.zip` if [[ "$OLD" != "$NEW" ]] ; then echo " new: " $NEW mtxrun --script cache --erase >ctx.log unzip -q -o context-linux-64.zip rm tex/*.tma sh ./install.sh >ctx.log context --version | grep "current version" fi
Hi, a version mismatch normally comes from the fact that i generate an lmtx update (for wolfgang to check, posted elsewhere) but nor a mkiv one and then upload to the website (as happened) also, the update script itself doesn't get updated so when that gets adapted one has to get it from the bare install (keep in mind that doing a fresh install doesn't hurt the system because texmf-projects and texmf-fonts are not affected) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On 07/11/2020 12:19, Hans Hagen wrote:
a version mismatch normally comes from the fact that i generate an lmtx update (for wolfgang to check, posted elsewhere) but nor a mkiv one and then upload to the website (as happened)
also, the update script itself doesn't get updated so when that gets adapted one has to get it from the bare install
(keep in mind that doing a fresh install doesn't hurt the system because texmf-projects and texmf-fonts are not affected)
The version check is just to prevent the extra data from being downloaded and installed when there was no need for it, because the current installed version is the same. (it saves the coal to be burned for the electricity)
participants (6)
-
Floris van Manen
-
Hans Hagen
-
mf
-
Otared Kavian
-
Pablo Rodriguez
-
Rik Kabel