ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Aditya Mahajan <adityam@umich.edu>
Subject: Re: follow up
Date: Tue, 2 Apr 2019 18:24:22 +0200	[thread overview]
Message-ID: <d986eebe-d3f7-b390-49d1-90442e92ce23@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.76.44.1904021140310.1605@nqv-guvaxcnq>

On 4/2/2019 5:56 PM, Aditya Mahajan wrote:

> To me, it seems like an error in pgfplots (I think that instead of 
> \mostrecent, the error message should use 
> `\pgfkeysvalueof{/pgfplots/compat/mostrecent}`) and is easily fixable by 
> setting `\let\mostrecent=\relax` before loading pgfplots.

if i grep the pgf path then indeed there are files with forward slashes 
and in few plaes with backslashes

> What is interesting is that for some reason the error message does not 
> show up in ConTeXt MkIV. I couldn't make a minimal example to show the 
> difference between the two.
maybe a different file is loaded based on some check ... hard to see 
with so many files loaded

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-04-02 16:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 12:56 Hans Hagen
2019-04-01 13:18 ` Floris van Manen
2019-04-01 13:31   ` Mojca Miklavec
2019-04-01 19:41 ` Henning Hraban Ramm
2019-04-02 15:56 ` Aditya Mahajan
2019-04-02 16:24   ` Hans Hagen [this message]
     [not found] <mailman.557.1554137032.1194.ntg-context@ntg.nl>
2019-04-02 11:49 ` Jeong Dal
2019-04-02 12:25   ` Hans Hagen
2019-04-02 12:40     ` Floris van Manen
2019-04-02 12:50       ` Hans Hagen
2019-04-02 13:12         ` Floris van Manen
2019-04-02 13:23           ` Hans Hagen
2019-04-02 13:58             ` Floris van Manen
2019-04-02 14:18               ` Ulrike Fischer
2019-04-02 14:50                 ` Hans Hagen
2019-04-02 15:11                 ` Hans Hagen
2019-04-02 18:38                   ` Taco Hoekwater
2019-04-02 19:29                     ` Floris van Manen
2019-04-02 20:16                     ` Hans Hagen
2019-04-03  5:58                       ` Christoph Reller
2019-04-03  7:06                         ` Hans Hagen
2019-04-02 14:42               ` Hans Hagen
2019-04-04 22:17 ` Jeong Dal
2019-04-04 22:28   ` Hans Hagen
2019-04-05  6:49   ` Otared Kavian
     [not found] <mailman.1.1554458401.26589.ntg-context@ntg.nl>
2019-04-05 14:30 ` Jeong Dal
2019-04-08  8:32   ` Otared Kavian
     [not found] <mailman.769.1554712325.1194.ntg-context@ntg.nl>
2019-04-08 13:32 ` Jeong Dal

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=d986eebe-d3f7-b390-49d1-90442e92ce23@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=adityam@umich.edu \
    --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).