How does it find the .vim language syntax file for - say - Ruby?
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
On 12/28/06, [EMAIL PROTECTED] wrote:
How does it find the .vim language syntax file for - say - Ruby?
When you start vim and say set syntax=ruby, vim should find the
syntax file automatically. For example under:
/usr/share/vim/vimXX/syntax/ruby.vim
c:/programs/vim/vimXX/syntax/ruby.vim
attached example file helps you.
To give you a better results give us a specification about the rules
how the explanations should be written.
Can you also take a look at the following pages if there is what you
want as result:
- http://www.w3.org/TR/ruby/
- http://www.w3.org/International/questions/qa
texexec and get tex out of it instead of a pdf/dvi? Or are there
stats about this kind of thing somewhere that I can lookup?
Thanks,
paul
You can load only the format files from context and it will run faster
than the ruby and perl version. I can do this on my machine with
\type{pdftex -fmt
if there is what you
want as result:
- http://www.w3.org/TR/ruby/
- http://www.w3.org/International/questions/qa-ruby
- http://www.w3.org/International/tutorials/ruby/
- http://www.w3.org/TR/css3-ruby/
Wolfgang
___
ntg-context mailing list
ntg-context
the result:
German Umlauts: ??SS
hm, can you check if regi-8859-1 is loaded ?
I do the following:
\setupoutput[pdftex]
That should be the default if you manage to make the new ruby variant
of texexec to work.
\installlanguage[german][de]
(I ask because I don't know
'
LONG TIME (about 1 min)
kpse : direct (forced)
using 'kpsewhich' to locate 'texexec' in suffix space 'rb' (1)
registering 'texexec' as 'C:/texmf/scripts/context/ruby/texexec.rb'
registering 'THREAD' as 'C:/texmf/scripts/context/ruby'
starting texexec
using 'system' call: ruby C
from the old perl scripts to new
ruby texmfstart), new releases of ConTeXt don't work any more on
MikTeX 2.4. (texmfstart requires a feature that is not present in
MikTeX 2.4)
I had other problems than the ones you describe, but try to see if
upgrading helps.
The standalone version should
the
author made our wish true (to move from the old perl scripts to new
ruby texmfstart), new releases of ConTeXt don't work any more on
MikTeX 2.4. (texmfstart requires a feature that is not present in
MikTeX 2.4)
I had other problems than the ones you describe, but try to see if
upgrading helps
: cont-en
--8bit: unknown option
TeXExec | runtime: 0.063
The perl and ruby versions:
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 33 registered patches, see perl -V for more detail)
Binary build 819 [267479] provided by ActiveState http://www.ActiveState.com
Built Aug 29 2006 12:42
| tex engine: pdfetex
TeXExec | tex format: cont-en
--8bit: unknown option
TeXExec | runtime: 0.063
The perl and ruby versions:
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 33 registered patches, see perl -V for more detail)
Binary build 819 [267479] provided by ActiveState
format: cont-en
--8bit: unknown option
TeXExec | runtime: 0.063
The perl and ruby versions:
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 33 registered patches, see perl -V for more detail)
Binary build 819 [267479] provided by ActiveState
http://www.ActiveState.com
Built Aug
: pdfetex
TeXExec | tex format: cont-en
--8bit: unknown option
TeXExec | runtime: 0.063
The perl and ruby versions:
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 33 registered patches, see perl -V for more detail)
Binary build 819 [267479] provided by ActiveState
http
Don't use MikTeX 2.4.
I can confirm that latest releases of ConTeXt (since the introduction
of ruby-based executables) have problems with MikTeX 2.4. Do you have
any chances to upgrade MikTeX to 2.5?
Mojca
___
ntg-context mailing list
ntg-context
false, and I get two ruby remarks/errors:
TeXExec | processing graphic 'textext-mpgraph.mp'
TeXExec | processing graphic 'textext-mpgraph.mp'
/home/taco/texmf/scripts/context/ruby/base/tex.rb:1522:in `runmp'TeXExec
| option 'nomprun' is set to 'true'
TeXExec | option 'nobackend' is set to 'true
scripts/context/ruby/mtxtools.rb
11706 11-17-06 20:24 scripts/context/lua/luatools.lua
---
2674107 85 files
-
Hans Hagen | PRAGMA
4030 09-12-06 17:39 tex/context/base/context.css
15870 11-15-06 15:02 scripts/context/ruby/mtxtools.rb
11706 11-17-06 20:24 scripts/context/lua/luatools.lua
---
2674107 85 files
At least I would hope that char-def
`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
curiosity ;- )
the choice for lua was made purely on my experience with perl, ruby and ... lua
(embedded into skype)
one big advantage of lua is that it has a long history, has reached a point of
stability, is developped in an academic atmosphere, is rather clean, very
lightweight, etc
anyhow
Hans Hagen wrote:
J. R. Capablanca wrote:
Hello everyone!
I'm trying to get started with ConText. I've setup a stand alone
install with perl and ruby on windows (last version).
I was quite impressed with the This way magazine layout... and was
trying to compile the example code
Does the job, thanks. AucTeX assumes
--passon=-interaction=nonstopmode, which doesn't work.
It worked with the perl (=older) texexec, but the ruby version doesn't
have a --passon switch.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell
Sanjoy Mahajan schrieb:
Does the job, thanks. AucTeX assumes
--passon=-interaction=nonstopmode, which doesn't work.
It worked with the perl (=older) texexec, but the ruby version doesn't
have a --passon switch.
I guess it would be best if it would be compatible with both versions.
I
Sanjoy Mahajan wrote:
Does the job, thanks. AucTeX assumes
--passon=-interaction=nonstopmode, which doesn't work.
It worked with the perl (=older) texexec, but the ruby version doesn't
have a --passon switch.
We should get that back, in my opinion.
Taco
Hello everyone!I'm trying to get started with ConText. I've setup a stand alone install with perl and ruby on windows (last version). I was quite impressed with the This way magazine layout... and was trying to compile the example code that comes in the 000 edition.
But the result is nothing like
J. R. Capablanca wrote:
Hello everyone!
I'm trying to get started with ConText. I've setup a stand alone
install with perl and ruby on windows (last version).
I was quite impressed with the This way magazine layout... and was
trying to compile the example code that comes in the 000 edition
of the
texmf-local/scripts/context/ruby/ directory into the texmf-linux/bin/
one.
I've found the mistake. I've forgotten to run setuptex or equivalent
before running texexec --make --alone.
I'll update the wiki in consequence.
Bye
-AJ
___
ntg-context
:
TeXUtil | parsing file translation.tui
TeXUtil | fatal error in plugin (processing): undefined method
`rjust' for 0:Fixnum
/usr/local/teTeX/share/texmf.local/scripts/context/ruby/base/
texutil.rb:619:in `build'
maybe adding a .to_s to that line helps, but i'm still puzzled
Hi,
is it possible that the ruby script version numbers are not always updated?
I am getting a 648 line diff file when I compare two different 1.3.3
versions of the ctxtools.rb file.
One of them, the smaller and older one, had some problems with quotes
around environment variables
Or is there a way to call texmfstart.rb from the unix stub files without
giving it execute permissions?
i dunno, but ruby pathtotexmfstart ... should work since then we're talking
about text files
Hans
translation.tui
TeXUtil | fatal error in plugin (processing): undefined method
`rjust' for 0:Fixnum
/usr/local/teTeX/share/texmf.local/scripts/context/ruby/base/
texutil.rb:619:in `build'
/usr/local/teTeX/share/texmf.local/scripts/context/ruby/base/
texutil.rb:845:in `processor'
/usr/local
this
Aditya
Thanks for the reply, Aditya. Your fix appears to work; now, I get a
proper index again.
Did you try texexec.rb? The message looks to be coming from ruby.
I am, in fact, using the ruby script; I just find the --version
output of the perl variant much clearer; that's why I use
of the run, I get these errors:
TeXUtil | parsing file translation.tui
TeXUtil | fatal error in plugin (processing): undefined method
`rjust' for 0:Fixnum
/usr/local/teTeX/share/texmf.local/scripts/context/ruby/base/
texutil.rb:619:in `build'
/usr/local/teTeX/share/texmf.local/scripts
' to locate 'metafun-p' in suffix space 'pdf' (2)
checking E:\isoimage\usr\local\context\tex\texmf-mswin\BIN for
metafun-p
checking E:\isoimage\usr\local\context\bin for metafun-p
checking E:\Ruby\bin for metafun-p
checking E:\Python24\ for metafun-p
checking E:\Perl\bin for metafun-p
checking E
On Mon, 30 Oct 2006, Thomas A. Schmitz wrote:
I have a number of grave problems with the latest beta
texmfstart texexec.pl --version
Did you try texexec.rb? The message looks to be coming from ruby.
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texexec : TeXExec 5.4.3
: direct (forced)
using 'kpsewhich' to locate 'metafun-p' in suffix space 'pdf' (2)
checking E:\isoimage\usr\local\context\tex\texmf-mswin\BIN for
metafun-p
checking E:\isoimage\usr\local\context\bin for metafun-p
checking E:\Ruby\bin for metafun-p
checking E:\Python24\ for metafun-p
ont-ja.tex and defined the default language, default encoding etc. in them. And created new formats. But I had to add these new formats into scripts/ruby/base/tex.rb in order to generate and use them. In case of ConTeXt update, I have to do this change again and again. That's the reason why I've sugges
that calls ruby with the right path
to texmfstart.rb.
- Forwarded message from Mike Bird [EMAIL PROTECTED] -
From: Mike Bird [EMAIL PROTECTED]
Subject: New texexec very confused
To: [EMAIL PROTECTED]
Date: Tue, 24 Oct 2006 20:52:30 -0700
The new ruby texexec is very confused. The problem
, add a texmfstart stub that calls ruby with the right path
to texmfstart.rb.
- Forwarded message from Mike Bird [EMAIL PROTECTED] -
From: Mike Bird [EMAIL PROTECTED]
Subject: New texexec very confused
To: [EMAIL PROTECTED]
Date: Tue, 24 Oct 2006 20:52:30 -0700
The new ruby texexec
On 10/25/06, Hans Hagen wrote:
Command:texexec --output=dvips foo
Should produce: foo.dvi
Actually produces: foo.pdf
hm, i need to check that, maybe there is no dvips option
Command:texexec --dvi foo
Should produce: foo.dvi
Actually produces:
# ctxtools --update
and that fetches the zip file(s) from the pragma site (or a mirror),
unpacks them, and updates the various perl and ruby scripts that come
with ConTeXt.
You have to be root for this when you want to update the global install,
otherwise you have a few extra caveats, see
, it would be probably more elegant and context-like to not have
texexec and texexec-sys, but rather a commandline switch - in this case
the handling would have to be done in the perl (or ruby?) scripts, which
is somewhat trickier.
concerning fmtutil: there was a time that texexec could call
a relatively
modern context installed, you say
# ctxtools --update
and that fetches the zip file(s) from the pragma site (or a mirror),
unpacks them, and updates the various perl and ruby scripts that come
with ConTeXt.
When this is done on a system where ConTeXt first came with a TeXlive
passes
some info to underlying progs/scripts so that redundant kpsewhich calls
don't take place; it's teh context way of dealing with non-downward
compatible texlives; (it has an embedded kpsewhich written in ruby but
this is disabled by default; it can also act as kpse servlet [serving
and that fetches the zip file(s) from the pragma site (or a mirror),
unpacks them, and updates the various perl and ruby scripts that come
with ConTeXt.
You have to be root for this when you want to update the global install,
otherwise you have a few extra caveats, see below.
After
Hello Hans,I'm still wondering why there are certain formats hardcoded in your scripts and how the "make all formats" feature does (not work).See scripts/ruby/base/tex.rb:Lines 131-137:Here are a few languages predefined which texexec "knows". If I want to add a format for
Richard Gabriel wrote:
Lines 131-137:
Here are a few languages predefined which texexec knows. If I want
to add a format for another language, I have to add a new line here.
such as ...? (adding a user inferface is more that adding something to
texexec)
Line 339:
Here are the default TeX
-like to not have
texexec and texexec-sys, but rather a commandline switch - in this case
the handling would have to be done in the perl (or ruby?) scripts, which
is somewhat trickier.
the only
way to figure that out is to check all format paths and take the first
one that fits; unfortunalty
contents as straight text - is there a way to override this
behaviour and specify this as an error? (This is rather like the Ruby
duck-typing approach - if an XML element is mapped, process it, else
it is an error).
\startXMLignore
\stopXMLignore
in xtag-pre you can see
seems to automatically
type
out its contents as straight text - is there a way to override
this
behaviour and specify this as an error? (This is rather like
the Ruby
duck-typing approach - if an XML element is mapped, process it,
else
it is an error).
\startXMLignore
\stopXMLignore
text - is there
a way to override this behaviour and specify this as an error? (This is
rather like the Ruby duck-typing approach - if an XML element is mapped,
process it, else it is an error).
Michael
NOTICE
This e-mail and any attachments are intended for the addressee(s) only and may
On Fri, 29 Sep 2006, Hans Hagen wrote:
[EMAIL PROTECTED] wrote:
I don't agree that lack of a current manual is a big problem for
potential users of ConteXt. In my experience, the biggest problem is
with the 3rd party tools (perl, ghostscript, ruby) on Win32 and legacy
commercial unix (where
# mkdir /usr/local/share/texmf
# cd /usr/local/share/texmf
# unzip /path/to/fresh/cont-tmf.zip
# chmod 755 scripts/context/ruby/texmfstart.rb
# texexec --make
# mv conte-en.fmt cont-nl.fmt metafun.mem mptopdf.fmt web2c/
# texhash
I don't understand
On Thu, 5 Oct 2006, Sanjoy Mahajan wrote:
# mkdir /usr/local/share/texmf
# cd /usr/local/share/texmf
# unzip /path/to/fresh/cont-tmf.zip
# chmod 755 scripts/context/ruby/texmfstart.rb
# texexec --make
Why not use texmfstart texexec --make to make sure
$@
and a link
ln -s ~/texmf/scripts/context/ruby/texmfstart.rb texmfstart
That's the proper way ;)
Heureka - that was it! Umlauts, special chars in typing environments
etc. are fine with the new texexec, even if the system wide format
files are created with the old texexec !?!
texexec only
to the differences (see ruby/tex.rb), but
someone may need to
search out the bugs and report them.
But then it has to be fixed, not thrown away ... I bet that the main
reason is one of the many if (MikTeX) switches in the source code
assuming that MikTeX is running on windows. Are there any MikTeX/Lunux
: 0 seconds
warning : use 'texmfstart texexec' instead
Hmm. Again the warning. What is this texmfstart thing anyway? In
~myuser/scripts/context/ruby/texmfstart.rb
~myuser/scripts/context/stubs/lib/texmfstart
there is something, but maybe it is not (yet?) needed
are created. I
sent quite a few requests, so that now finally the ruby scripts are
used instead of the old perl-based ones. But I don't have the
slightest idea how they work under Linux.
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl
Renaud AUBIN wrote:
Taco Hoekwater a écrit :
And all you need now is the latest pdftex -)
http://sarovar.org/project/showfiles.php?group_id=106release_id=752
Taco
Is it normal that pdfetex.pool is no more built ?
Yes. There is now only one executable, pdftex. It contains all code
width, different height doesn't affect the
aspect of the 3D Artwork.
\defineiiidartworkprojection[name][type=perspective|orthographic ,
nf=automatic|explicit , near=number, far=number, fov=number.]
try to use existing ones: auto instead of automatic
ok
I'll use ruby
ruby and a magic | (see [NTG-context] run a ruby script and
use the standard output ???) to calculate C2W and CO...
best is to make that pluggable, so that we can optimize such computations
What do you mean by pluggable ? Do you mean that we can turn this
feature on or off
of ConteXt. In my experience, the biggest problem is
with the 3rd party tools (perl, ghostscript, ruby) on Win32 and legacy
commercial unix (where ruby is not provided and the system perl will
be a very old version).
You can write simple LaTeX documents without working 3rd party tools
(MikTeX-2.5
latest versions of pdftex support this (i\ve forgotten the syntax, but taco who wrote the patch may remember)
piping syntax:
\input "|ruby ./myscript.rb \vartest X"
the magic trick is the | symbol. With your current tex:
\writ18{ruby ./myscript.rb \vartest X
Renaud AUBIN wrote:
\starttext
\input |ls
\stoptext
leads to
(/usr/share/texmf-tetex/tex/latex/tools/.tex File ignored)
Runaway argument?
ls
! Paragraph ended before \next was complete.
to be read again
\par
???
The pipe symbol has to be non-active
that lack of a current manual is a big problem for
potential users of ConteXt. In my experience, the biggest problem is
with the 3rd party tools (perl, ghostscript, ruby) on Win32 and legacy
commercial unix (where ruby is not provided and the system perl will
be a very old version).
Interesting
Taco Hoekwater a crit:
The
pipe symbol has to be non-active (\catcode`\|=12 )
Taco
\starttext
\catcode`\|=12
\input "|ls -l"
\stoptext
! I can't find file `"|ls -l"'.
l.7 \input "|ls -l"
___
ntg-context mailing list
ntg-context@ntg.nl
Renaud AUBIN wrote:
\starttext
\catcode`\|=12
\input |ls -l
\stoptext
! I can't find file `|ls -l'.
And all you need now is the latest pdftex -)
http://sarovar.org/project/showfiles.php?group_id=106release_id=752
Taco
___
ntg-context
Taco Hoekwater a écrit :
And all you need now is the latest pdftex -)
http://sarovar.org/project/showfiles.php?group_id=106release_id=752
Taco
Thanks
Yes, I finally realized that... ;) I'm now on my way to upgrade it...
___
ntg-context
Taco Hoekwater a écrit :
And all you need now is the latest pdftex -)
http://sarovar.org/project/showfiles.php?group_id=106release_id=752
Taco
Is it normal that pdfetex.pool is no more built ?
___
ntg-context mailing list
ntg-context@ntg.nl
[EMAIL PROTECTED] wrote:
I don't agree that lack of a current manual is a big problem for
potential users of ConteXt. In my experience, the biggest problem is
with the 3rd party tools (perl, ghostscript, ruby) on Win32 and legacy
commercial unix (where ruby is not provided and the system perl
Renaud AUBIN wrote:
Hi all,
Is it possible to run a ruby script from a context document during its
processing (I already know how to do that using \write18 but there is
maybe a better way...) then get the output of the script to display or
use it into the document. It's a little bit hard
Hans Hagen wrote:
piping: the latest versions of pdftex support this (i\ve forgotten the
syntax, but taco who wrote the patch may remember)
piping syntax:
\input |ruby ./myscript.rb \vartest X
the magic trick is the | symbol. With your current tex:
\writ18{ruby ./myscript.rb
I'll use ruby and a magic | (see [NTG-context] run a ruby script and
use the standard output ???) to calculate C2W and CO...
3. ... I need to define a macro to setup the 3D annot before to use it
by \externalfigure or with another brand new macro...
That's it for the moment..
= idem, up=idem]
I'll use ruby and a magic | (see [NTG-context] run a ruby script and
use the standard output ???) to calculate C2W and CO...
best is to make that pluggable, so that we can optimize such computations
3. ... I need to define a macro to setup the 3D annot before to use
\stoptext
[EMAIL PROTECTED]:~/tmp$ ~/texmf/scripts/context/ruby/texmfstart.rb texexec
t.tex -- result bla.pdf
TeXExec | processing document 't.tex'
TeXExec | no ctx file found
TeXExec | tex processing method: context
TeXExec | TeX run 1
TeXExec | writing option file t.top
TeXExec | using randomseed 1402
I'm not sure if your command got mangled by the mailer disliking long
lines, but it looks like you have this line:
[EMAIL PROTECTED]:~/tmp$ ~/texmf/scripts/context/ruby/texmfstart.rb texexec
t.tex -- result bla.pdf
i.e. something like texexec t.tex -- result bla.pdf
The texexec man entry, I
Sanjoy Mahajan wrote:
I'm not sure if your command got mangled by the mailer disliking long
lines, but it looks like you have this line:
[EMAIL PROTECTED]:~/tmp$ ~/texmf/scripts/context/ruby/texmfstart.rb texexec
t.tex -- result bla.pdf
i.e. something like texexec t.tex -- result
that -)
when i started using ruby there was no proper command line handler so i
wrote one myself; that one also hooks nicely into other pieces of the
system now
By the way, I use these two executable scripts to shorten the command
lines:
$ cat /home/sanjoy/bin/texmfstart
#!/bin/bash
ruby
$ cat /home/sanjoy/bin/texmfstart
#!/bin/bash
ruby `kpsewhich --format=texmfscripts texmfstart.rb` $@
$ cat /home/sanjoy/bin/texexec
#!/bin/sh
texmfstart texexec.rb $@
Thanks, I'm using them too, but I remember there was some confusion
about $@ versus $@ in this command
Hi all,
Is it possible to run a ruby script from a context document during its
processing (I already know how to do that using \write18 but there is
maybe a better way...) then get the output of the script to display or
use it into the document. It's a little bit hard to describe so I have
Hi all,
the ruby version of texexec is missing some command line switches I have
been using. I'm missing --result (however, I could live without that)
and especially --mode and --passon. Are there any workarounds?
Also, texexec doesn't complain when given a command line switch, which
it doesn't
Ralf Schmitt wrote:
Hi all,
the ruby version of texexec is missing some command line switches I have
been using. I'm missing --result (however, I could live without that)
and especially --mode and --passon. Are there any workarounds?
hm, mode and result should work (TeXExec | version
Ralf Schmitt wrote:
Hi all,
the ruby version of texexec is missing some command line switches I have
been using. I'm missing --result (however, I could live without that)
and especially --mode and --passon. Are there any workarounds?
Apparently I'm a bit mistaken:
--mode is working
Ralf Schmitt wrote:
Ralf Schmitt wrote:
Hi all,
the ruby version of texexec is missing some command line switches I have
been using. I'm missing --result (however, I could live without that)
and especially --mode and --passon. Are there any workarounds?
Apparently I'm a bit
Hans Hagen wrote:
Ralf Schmitt wrote:
Ralf Schmitt wrote:
Hi all,
the ruby version of texexec is missing some command line switches I have
been using. I'm missing --result (however, I could live without that)
and especially --mode and --passon. Are there any workarounds
/teTeX/bin/powerpc-apple-darwin-current/epstopdf }
\def\PDF{\TU --figures --epstopdf } % --figures not yet in Ruby
version
\ifeof18
\installprogram{\LP \bufferprefix lilypond-\the\lily!figures.tmp}%
\doif\jobsuffix{pdf}{%
\installprogram{\PDF
/local/teTeX/share/texmf.local/scripts/context/perl/
texutil.pl }
%\def\PDF{/usr/local/teTeX/bin/powerpc-apple-darwin-current/epstopdf }
\def\PDF{\TU --figures --epstopdf } % --figures not yet in Ruby
version
use texmfstart!
texmfstart whateverscript whateverargs
, not sure if that's what you are running).
I have noticed that --passon hasn't been working since I switched from
perl to ruby texexec. I used to use to turn on -file-line-error to get
an error output format that more closely matches what a C compiler
produces, and is therefore easier for Emacs
versions. 4.log says
that write18 ran
texmfstart --ifchanged=4-fig.mp texexec --mpstatic 4-fig.mp
I ran it by hand omitting the --ifchanged:
$ texmfstart texexec --mpstatic 4-fig.mp
/home/sanjoy/texmf/scripts/context/ruby/texexec.rb:101:in `mpstatic'TeXExec |
option 'randomseed' is set to '1131
);
and then ruby running:
system(texmfstart --ifchanged=dc2-fig.mp texexec --mpstatic dc2-fig.mp),
which eventually makes the larger file texexec-mpgraph.mp and then does:
mpost -mem=metafun -translate-file=natural.tcx texexec-mpgraph.mp
which produces the same error.
Hmm
/web2c
/usr/local/teTeX/share/texmf.gwtex/web2c
/usr/local/teTeX/share/texmf.tetex/web2c /usr/local/teTeX/share/texmf/web2c
TeXExec | start of analysis
/usr/local/teTex/share/texmf.local/scripts/context/ruby/texexec.rb:17:
command not found: texmfstart texexec --help
/usr/local/teTex/share
''
which allows it to work, that is, the line should be the same under
windows and linux.
~$ ruby --version
ruby 1.8.4 (2005-12-24) [i486-linux]
Regards, Johan
--
Johan Sandblom N8, MRC, Karolinska sjh
t +46851776108 17176 Stockholm
m +46735521477 Sweden
What is wanted
/web2c /usr/local/teTeX/share/texmf/web2c
TeXExec | start of analysis
/usr/local/teTex/share/texmf.local/scripts/context/ruby/texexec.rb:17:
command not found: texmfstart texexec --help
/usr/local/teTex/share/texmf.local/scripts/context/ruby/texexec.rb:17:
command not found: texmfstart texutil
`natural.tcx'.This is pdfTeX, Version 3.141592-1.40.0-beta-20060213 (Web2c 7.5.5) (INITEX)\write18 enabled.entering extended mode! I can't find file `cont-en'.* *cont-enPlease type another input file name:Any help will be apreciated ...Greetings from a shiny BrazilMarcus ViniciusBy the way :Ruby is ok
Hello,
for those, you like rpm, there is now a TeX-live source rpm with the
following features:
- support for easy ConTeXt update (command updateConTeXt.sh)
- support for URW Garamond
- support for Adobe eurofont
- support for ruby versions of ConTeXt scripts
- latest TeX-live
- latest ConTeXt
Hans Hagen wrote:
And, a small point of disagreement with the old man entry for texexec:
'texexec --output=dvi' produces pdf.
line 116 in tex.rb in the ruby base path can be adapted:
['dvips','ps','dvi'] .each do |b|
@@backends[b] = 'dvips' end
Sanjoy Mahajan wrote:
Hans Hagen wrote:
And, a small point of disagreement with the old man entry for texexec:
'texexec --output=dvi' produces pdf.
line 116 in tex.rb in the ruby base path can be adapted:
['dvips','ps','dvi'] .each do |b
/ the folders goodies, gs, perl, ruby and xmlib are
empty. Ergo, the stand-alone for Windows doesn't seem to contain unzip.exe
and thus the excellent context update feature won't work without
fiddling.
[I know, I know, I'm being a pain in the *. But the standalone is so close
to being
equivalent to running 'texexec --dvips'.
And, a small point of disagreement with the old man entry for texexec:
'texexec --output=dvi' produces pdf.
line 116 in tex.rb in the ruby base path can be adapted:
['dvips','ps','dvi'] .each do |b|
@@backends[b] = 'dvips
to switch to the usage of
new ruby scripts.
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
--purge [--all]
(texutill --purge[all] if you don't have the ruby variant installed yet)
although I know that that's not quite the same. (I know some people in
LaTeX world who use make files to copy/remove files.)
Mojca
___
ntg-context mailing list
ntg
701 - 800 of 1321 matches
Mail list logo
