From: linguafalsa--- via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: linguafalsa@gmail.com
Subject: Re: [NTG-context] All NUL files in the Context distribution
Date: Sat, 17 Jun 2023 07:06:18 -0400 [thread overview]
Message-ID: <ncey3i4qw2lgmhugmcpj7fhmm7nxnchjdik77257m2b5uhr65b@kohuq2ow4oey> (raw)
In-Reply-To: <83490df6-6ee2-3f92-a8f3-66a68c78119f@leliseron.org>
On Sat, Jun 17, 2023 at 10:06:09AM +0200, Alain Delmotte via ntg-context wrote:
> Hi,
>
> Le 14/06/2023 à 17:13, Leah Neukirchen via ntg-context a écrit :
> > Hi,
> >
> > I was looking into the SciTE setup when I found that
> > tex/texmf-context/context/data/scite/context/scite-context-internal.properties
> > only contained NUL bytes.
> >
> > Deleting and reinstalling doesn't fix it.
> >
> > I have now checked the other files there and these files seem to have
> > gotten corrupted at some point. Does anyone have a working copy to
> > restore them?
> >
> > tex/texmf-context/context/data/scite/context/scite-context-internal.properties
> > tex/texmf-context/context/data/scite/context/lexers/scite-context-lexer-web-snippets.lua
> > tex/texmf-context/doc/context/sources/general/manuals/start/en/ma-cb-en-commands.tex
> >
> > Thanks,
>
> Same for me:
> tex/texmf-context/doc/context/sources/general/manuals/start/en/ma-cb-en-commands.tex
> contains NUL characters.
>
> > system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.13 int:
> english/english
not only that version but also
ConTeXt ver: 2023.04.27 17:04 MKIV fmt: 2023.5.4 int: english/english
no bueno.
>
> --
>
> Alain
>
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
--
As long as there are ill-defined goals, bizarre bugs, and unrealistic
schedules, there will be Real Programmers willing to jump in and Solve
The Problem, saving the documentation for later.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-06-17 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 15:13 Leah Neukirchen via ntg-context
2023-06-14 15:48 ` Henning Hraban Ramm via ntg-context
2023-06-14 17:19 ` Leah Neukirchen via ntg-context
2023-06-17 8:06 ` Alain Delmotte via ntg-context
2023-06-17 11:06 ` linguafalsa--- via ntg-context [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=ncey3i4qw2lgmhugmcpj7fhmm7nxnchjdik77257m2b5uhr65b@kohuq2ow4oey \
--to=ntg-context@ntg.nl \
--cc=linguafalsa@gmail.com \
/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).