ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: buffer names in MKII
Date: Fri, 19 Aug 2011 09:53:41 +0200	[thread overview]
Message-ID: <4E4E1685.3090101@wxs.nl> (raw)
In-Reply-To: <CALBOmsZTjF-OFC13+Akbb5S4e5oFe7QDMHME0sdHL2MC057cOQ@mail.gmail.com>

On 19-8-2011 00:32, Mojca Miklavec wrote:
> Dear Hans,
>
> something broke backward compatibility in MKII.
>
> When using buffers like in
>
> \startbuffer[buffername]
> hello world
> \stopbuffer
>
> the code now creates buffername.tmp instead of \jobname-buffername.tmp.
>
> This breaks the gnuplot module in weird ways. I can probably fix it in
> one way or another, but I'm not sure why the behaviour would change.
> To fix the vim module? :) :) :)
>
> OK, I need to take some time and try to use Aditya's code in the
> background anyway, but I still wonder if the change was intentional or
> not.

Probably a side effect of some cleaning up of filename code deep down. 
Normally in mkiv buffers are not saved on disk (as with mkii).

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      parent reply	other threads:[~2011-08-19  7:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 22:32 Mojca Miklavec
2011-08-18 21:29 ` Aditya Mahajan
2011-08-19  7:53   ` Henning Hraban Ramm
2011-08-19 15:08     ` Lilypond (Re: buffer names in MKII) Aditya Mahajan
2011-08-19 20:18       ` Lilypond Henning Hraban Ramm
2011-08-20  8:19         ` Lilypond Aditya Mahajan
2011-08-21  1:22           ` Lilypond David Wooten
2011-08-21 12:07           ` Lilypond Henning Hraban Ramm
2011-08-21 18:25             ` Lilypond Henning Hraban Ramm
2011-08-21 22:14             ` Lilypond Aditya Mahajan
2011-08-21 22:24               ` Lilypond Hans Hagen
2011-08-21 22:32                 ` Lilypond Aditya Mahajan
2011-08-22  1:53               ` Lilypond Aditya Mahajan
2011-08-22 13:59                 ` Lilypond Henning Hraban Ramm
2011-08-22 15:18                   ` Lilypond Aditya Mahajan
2011-08-19  0:09 ` buffer names in MKII Aditya Mahajan
2011-08-19  7:53 ` Hans Hagen [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=4E4E1685.3090101@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mojca.miklavec.lists@gmail.com \
    --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).