From: Taco Hoekwater via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@bittext.nl>
Subject: Wiki's ConTeXt updated
Date: Fri, 29 Oct 2021 10:24:05 +0200 [thread overview]
Message-ID: <8A85E082-E7C6-402C-AAAD-2546F0964240@bittext.nl> (raw)
In-Reply-To: <f3e8c51c-66b1-2631-5f94-e87edc6d7ef4@xs4all.nl>
Hi,
Since yesterday wiki.contextgarden.net, live.contextgarden.net, and source.contextgarden.net all use
ConTeXt 2021.10.28 10:19 LMTX
as the installed ConTeXt.
I have also tried to reset all the “<context>” output images so that they will be automatically
regenerated with this new ConTeXt, but sometimes that reset does not work properly, and the wiki
has to be ‘helped' manually.
If you see a ‘broken image’ icon (or no output at all) from a “<context>” demonstration block, do this:
* right click on the ‘Edit’ link of the page so it opens in a new tab,
* go to the new tab and press ’Show preview’,
* close the tab.
The ’Show preview' will force the wiki to refresh the cached images. ’Save changes’ is not needed.
Best wishes,
Taco
—
Taco Hoekwater E: taco@bittext.nl
genderfluid (all pronouns)
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-10-29 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 9:24 new upload, new trickery Hans Hagen via ntg-context
2021-10-29 8:24 ` Taco Hoekwater via ntg-context [this message]
2021-11-16 13:52 ` Marcus Vinicius Mesquita via ntg-context
2021-11-16 17:44 ` Hans Hagen via ntg-context
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=8A85E082-E7C6-402C-AAAD-2546F0964240@bittext.nl \
--to=ntg-context@ntg.nl \
--cc=taco@bittext.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).