From: Jonas Stein <news@jonasstein.de>
To: ntg-context@ntg.nl
Subject: Re: howto start with presentations?
Date: Mon, 10 Jan 2011 03:01:46 +0100 [thread overview]
Message-ID: <at5qv7-in7.ln1@news.jonasstein.de> (raw)
In-Reply-To: <alpine.LNX.2.01.1101091934170.3769@ybpnyubfg.ybpnyqbznva>
>> # whereis mpost
>> mpost: /usr/bin/mpost /usr/share/man/man1/mpost.1.gz
>
> Does it work? That is if you compile
>
> beginfig(1)
> draw fullcircle scaled 3cm ;
> endfig ;
> end ;
>
> using `mp file.mp` do you get a correct file.1 file (open it using a ps
> viewer).
$ mpost file.mp && okular file.1
shows me a nice circle.
mp is not available on my system, but mpost claims to be metapost:
$ mpost -version
MetaPost 1.208
does context expect it as 'mp'? I could create a alias mp --> mpost
> Otherwise I don't know why you are getting erratic behavior with metapost.
> Sometimes, an extra run helps.
i tried it several times and deleted the .pdf files before.
I wonder why context is so quiet if errors occour.
If something fails it should always break with errorcode != 0
> As explained on http://wiki.contextgarden.net/Running_Mark_IV you need to
> run
>
> luatools --generate.
i suppose its a bug of the debian package if i have to run it
after installation via .deb system.
as user i did now:
$ luatools --generate
MTXrun | forcing cache reload
MTXrun | resolvers: warning: no lua configuration files found
MTXrun | resolvers
MTXrun | resolvers
MTXrun | the resolver databases are not present or outdated
MTXrun | resolvers: using suffix based filetype 'lua'
MTXrun | resolvers: using suffix based filetype 'lua'
MTXrun | resolvers: remembering file 'mtx-base.lua'
MTXrun | resolvers: using suffix based filetype 'lua'
MTXrun | unknown script 'base.lua' or 'mtx-base.lua'
=========
seems something goes wrong here too.
Kind regards and thank you a lot for your help.
--
Jonas Stein <news@jonasstein.de>
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-01-10 2:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 16:40 Jonas Stein
2011-01-08 17:08 ` Wolfgang Schuster
2011-01-08 17:48 ` Thomas A. Schmitz
2011-01-08 18:00 ` Jonas Stein
2011-01-08 18:08 ` Aditya Mahajan
2011-01-08 23:10 ` Jonas Stein
2011-01-09 0:21 ` Aditya Mahajan
2011-01-09 3:50 ` Jonas Stein
2011-01-09 17:15 ` Jonas Stein
2011-01-09 17:37 ` Wolfgang Schuster
2011-01-09 17:57 ` Aditya Mahajan
2011-01-09 18:15 ` Jonas Stein
2011-01-09 18:56 ` Aditya Mahajan
2011-01-09 19:45 ` Jonas Stein
2011-01-09 20:15 ` Aditya Mahajan
2011-01-09 22:01 ` Jonas Stein
2011-01-09 22:28 ` Aditya Mahajan
2011-01-10 0:27 ` Jonas Stein
2011-01-10 0:41 ` Aditya Mahajan
2011-01-10 2:01 ` Jonas Stein [this message]
2011-01-08 18:12 ` Marco
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=at5qv7-in7.ln1@news.jonasstein.de \
--to=news@jonasstein.de \
--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).