ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: overlay problem with textext
Date: Thu, 23 Nov 2006 05:08:43 +0100	[thread overview]
Message-ID: <6faad9f00611222008sb3ada18q26bc03225f850dd2@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00611221803x75b9f1f4j67bb2b79944a52f3@mail.gmail.com>

On 11/23/06, Mojca Miklavec wrote:
> On 11/22/06, Peter Rolf wrote:
> > Hi all,
> >
> > the attached example works with the version from 17.11.|20.11., but not
> > with the current (22.11.06, 11:02) one. The problem seems to be in the
> > use of textext, as it 'works' (background is visible) when I exchange

Not only textext ... here the whole \startMPcode ... \stopMPcode seems
to be broken here (where's the old good tool "ctxtools --install
20061120" ?).

One of the problems that appeared with new files:

TeXExec | processing graphic '07-svd-mpgraph.mp'
sh: -c: line 1: syntax error near unexpected token `newline'
sh: -c: line 1:
`>/usr/local/teTeX/share/texmf.local/scripts/context/ruby/texmfstart.rb<'

(And I have no idea what it's supposed to mean.)

I saw some changes in tex.rb renaming filename into mpname during mp
runs, but I'll test after I finish writing my report, not before.

I seem to be very grateful for Taco's archives on
https://foundry.supelec.fr/frs/?group_id=14 in such cases ;)

Mojca

PS: I might be using slightly unstandard way of launching texmfstart,
but that approach seems to work up to the 20061120.

  reply	other threads:[~2006-11-23  4:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 14:42 Peter Rolf
2006-11-23  2:03 ` Mojca Miklavec
2006-11-23  4:08   ` Mojca Miklavec [this message]
2006-11-23  8:59     ` Taco Hoekwater
2006-11-23 10:01       ` Hans Hagen
2006-11-23 10:22         ` Peter Rolf

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=6faad9f00611222008sb3ada18q26bc03225f850dd2@mail.gmail.com \
    --to=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).