Re: [NTG-context] does metafun require texexec --final?

2006-09-27 Thread Patrick Gundlach
Hi, > If I try to edit the top level of a page by clicking the edit tab at > the top, then I get a dialog box from Firefox (on Linux). I just > tried it with and got > "You have chosen to open index.php which is a: PHP script. What > should Firefox do

Re: [NTG-context] does metafun require texexec --final?

2006-09-26 Thread Sanjoy Mahajan
> sure, that's an option, but up to the user (maybe wikify this > suggestion) Patrick: Not sure if it's a firefox-only problem or one that the contextgarden wiki can help with by sending more detailed mime types, but... If I try to edit the top level of a page by clicking the edit tab at the top

Re: [NTG-context] does metafun require texexec --final?

2006-09-26 Thread Hans Hagen
� wrote: > On Sun, 24 Sep 2006, Hans Hagen wrote: > > >>> Oh, that's not a good idea, because the next context update will >>> overwrite cont-sys.rme. So I should copy cont-sys.rme to cont-sys.tex >>> first, then uncomment the lines in cont-sys.tex. But then a context >>> update will overwrite

Re: [NTG-context] does metafun require texexec --final?

2006-09-25 Thread Peter Münster
On Sun, 24 Sep 2006, Hans Hagen wrote: > > Oh, that's not a good idea, because the next context update will > > overwrite cont-sys.rme. So I should copy cont-sys.rme to cont-sys.tex > > first, then uncomment the lines in cont-sys.tex. But then a context > > update will overwrite cont-sys.rme, an

Re: [NTG-context] does metafun require texexec --final?

2006-09-24 Thread Hans Hagen
Sanjoy Mahajan wrote: > Wolfgang, > > Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme > has these lines > > % \runMPgraphicstrue > % \runMPTEXgraphicstrue > > The .rme extension meant I'd missed it when I ran grep on the .tex > files. I'll uncomment them. > > Oh, that's not

Re: [NTG-context] does metafun require texexec --final?

2006-09-24 Thread Taco Hoekwater
Mojca Miklavec wrote: > On 9/23/06, Sanjoy Mahajan wrote: > >>So maybe the best approach is to edit cont-sys.rme directly, then >>merge changes (using a revision control system like mercurial or git) >>that arrive with the new context distributions. > > > Changes in cont-sys.rme don't happen tha

Re: [NTG-context] does metafun require texexec --final?

2006-09-24 Thread Mojca Miklavec
On 9/23/06, Sanjoy Mahajan wrote: > So maybe the best approach is to edit cont-sys.rme directly, then > merge changes (using a revision control system like mercurial or git) > that arrive with the new context distributions. Changes in cont-sys.rme don't happen that often. You can safely create con

Re: [NTG-context] does metafun require texexec --final?

2006-09-23 Thread Wolfgang Schuster
On Sat, 23 Sep 2006 17:46:56 +0100 Sanjoy Mahajan <[EMAIL PROTECTED]> wrote: > Wolfgang, > > Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme > has these lines > > % \runMPgraphicstrue > % \runMPTEXgraphicstrue > > The .rme extension meant I'd missed it when I ran grep on

Re: [NTG-context] does metafun require texexec --final?

2006-09-23 Thread Sanjoy Mahajan
Wolfgang, Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme has these lines % \runMPgraphicstrue % \runMPTEXgraphicstrue The .rme extension meant I'd missed it when I ran grep on the .tex files. I'll uncomment them. Oh, that's not a good idea, because the next context upda

Re: [NTG-context] does metafun require texexec --final?

2006-09-23 Thread Wolfgang Schuster
On Sat, 23 Sep 2006 15:03:57 +0100 Sanjoy Mahajan <[EMAIL PROTECTED]> wrote: > [Hans: Feature suggestion for figure inclusion at the end...] > > I wrote: > > So, is --final a requirement when using metafun, or am I hacking > > around a problem I've caused by leaving something out? > > An answer

Re: [NTG-context] does metafun require texexec --final?

2006-09-23 Thread Sanjoy Mahajan
[Hans: Feature suggestion for figure inclusion at the end...] I wrote: > So, is --final a requirement when using metafun, or am I hacking > around a problem I've caused by leaving something out? An answer is that I should set \runMPgraphicstrue. I thought it was automatically set, half-rememberi