From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: Bug ?!? \protectbufferstrue
Date: Wed, 18 Jul 2001 11:43:54 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010718114121.029e5470@server-1> (raw)
In-Reply-To: <200107171022.MAA04046@sol.cs.uni-dortmund.de>
At 12:22 PM 7/17/2001 +0200, Patrick Gundlach wrote:
>Hi,
>
>it seems that a missing \protectbufferstrue causes a lot of
>malfunctioning. It happened to at least three people I know of
>:-) It might be worth (?) looking closer at this.
Indeed, so what exactly is the problem; mpgraph.mp is file that makes
troubles, and it happens that there can be a mpgraph.mp on a full tex
system. This means that teh [often unfortunate default global] search of
kpse finds the wrong file. This is why i make a dummy always as well as
test for the length. Now, the first question to answer is: does it happen
in the latest context?
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-18 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Tue, 17 Jul 2001 12:02:57 +0200." <5.1.0.14.0.20010716194521.00aa1610@public.uni-hamburg.de>
2001-07-17 10:22 ` Patrick Gundlach
2001-07-18 9:43 ` Hans Hagen [this message]
[not found] <Your message of "Wed, 18 Jul 2001 11:43:54 +0200." <5.1.0.14.1.20010718114121.029e5470@server-1>
2001-07-18 13:59 ` Patrick Gundlach
2001-07-18 14:36 ` Hans Hagen
[not found] <Your message of "Wed, 18 Jul 2001 16:36:14 +0200." <5.1.0.14.1.20010718163541.02210d38@server-1>
2001-07-18 15:28 ` Patrick Gundlach
2001-07-18 15:47 ` 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=5.1.0.14.1.20010718114121.029e5470@server-1 \
--to=pragma@wxs.nl \
--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).