From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: klerer@sxmail.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt update issue
Date: Thu, 07 Jan 2016 17:48:47 +0100 [thread overview]
Message-ID: <568E96EF.1030701@gmail.com> (raw)
In-Reply-To: <d9a4d2e7c244f479a1b6e508b60625a2@www.sxmail.de>
[-- Attachment #1.1: Type: text/plain, Size: 1551 bytes --]
> klerer@sxmail.de <mailto:klerer@sxmail.de>
> 7. Januar 2016 um 17:35
> Dear list,
>
> I have experienced a problem updating the ConTeXt version I use on a
> current Linux operating system flavour beginning ca. two months ago.
> By that time, as was successfully applied several times before within
> the past year of me using ConTeXt, I initiated the update process on
> the bash console via one command recommended on the corresponding
> ConTeXt page: "sh ./first-setup.sh --context=current".
> Then, and on two other ocassions very recently, ConTeXt got stuck
> (after data had indeed been received and some actions concerning the
> usual update had been executed, too) giving back the following lines
> in the bash console that puzzled me a lot:
> "...
> This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/dev) (INITEX)
> system commands enabled.
> (/home/ichhalt/context/tex/texmf-context/tex/context/base/cont-nl.mkiv
> (/home/ichhalt/context/tex/texmf-context/tex/context/base/context.mkiv
> (/home/ichhalt/context/tex/texmf-context/tex/context/base/syst-ini.mkiv
> ! Undefined control sequence.
> l.1020 pdfoutput
> zerocount"
> I admit that this code example is quite short, but it is definitely
> the last that the whole ConTeXt update process returns-otherwise it
> stood still.
> What-except for uninstalling and re-installing ConTeXt-could help now?
> If ever possible, a conservation of my current ConTeXt installation
> appeared preferable to me.
Do you use Tikz in your document?
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2585 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-07 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 16:35 klerer
2016-01-07 16:48 ` Wolfgang Schuster [this message]
2016-01-07 17:35 ` Hans Hagen
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=568E96EF.1030701@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=klerer@sxmail.de \
--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).