From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: cannot update LMTX
Date: Wed, 4 Nov 2020 20:56:53 +0100 [thread overview]
Message-ID: <ba61232b-8aa0-fe54-effb-e1470a193c8e@gmx.es> (raw)
In-Reply-To: <A907EFFA-8F88-4DAE-98FB-DA3A6B4DC585@gmail.com>
On 11/4/20 8:41 PM, Otared Kavian wrote:
> Hi Pablo,
>
> For some unknown reason despite having tried to update lmtx several
> times, I still have version 2020.09.20 23:02.
Hi Otared,
this is exactly the same version I have.
> Indeed I do a backup before any update in order to be able to go
> back to a working version…
It is a reasonable practice, as one never knows what could go wrong.
> What did you do in order to get version 2020.11.04 09:40 ?
I did a fresh install (as Sylvain suggested). Although I only wanted to
test that a fresh install was working.
I’m going to wait until I upgrade my local version. The backup is
already done.
Many thanks for your reply,
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-11-04 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 15:10 Pablo Rodriguez
2020-11-04 15:13 ` Sylvain Hubert
2020-11-04 15:18 ` Otared Kavian
2020-11-04 15:38 ` Pablo Rodriguez
2020-11-04 19:41 ` Otared Kavian
2020-11-04 19:56 ` Pablo Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba61232b-8aa0-fe54-effb-e1470a193c8e@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).