I'm cc'ing the list again because this error is bizzarre. Unfortunately,
there don't seem to be too many (non-lurking) Perl experts on this list (or
I never would have been picked to write reLyX :) but maybe someone has a
clue.
On Wed, Feb 10, 1999 at 04:26:48PM +0100, Jean-Michel Barbet wrote:
>
> I have checked reLyX/BUGS and man page and have not found anything
> related to the problem I have.
Darn. It's nice that you're responsible, but that makes the problem more
difficult :)
> -d switch does not provide more information except the path of
> the LaTeX command syntax file used.
>
> I don't think this is something with my .tex file since :
>
> - (it is very primitive)
>
> - it happens as well with the test file in lyx/share/lyx/reLyX/test.ltx
>
> - the old reLyX that comes with LyX V0.12 works with both the test file
> test.ltx and my first test.
>
Wow. This is very ugly. As I'm sure you can imagine, this problem doesn't
happen for me, and I'm running Perl 5.005_02. I'm on an SGI, but I could've
sworn that perl is supposed to do the same thing on different platforms. And
as I said, from the error it seems like reLyX is managing to open and start
reading the file. In fact, it seems like reLyX is even able to read a few
tokens before it chokes, in which case platform issues seem even *less*
likely. And yet I can't imagine what else it is if noone else has seen this
problem. If it happens with any latex file, then you can be sure *someone*
else would have reported it! And since it' happening while reading the
syntax.default file, which is something that reLyX does no matter what the
input file is...
(One thing to check: I assume the file you're reading is in fact the
standard syntax.default file. If it's not that still doesn't explain things
but might be a hint.)
(Rich Fields did have a problem getting reLyX running on an HP, but there it
seemed to be some weird problem with the shell. He never actually got it to
run, but clearly here the wrapper is correctly calling the various
subroutines.)
The other weirdness is that I checked, and Text::TeX::Group *does* have a
exact_print method. We don't even need to do any fancy inheritance or
anything; there's an explicit Text::TeX::Group::exact_print.
Obviously, if it's a platform issue, I can't do stuff here. Would you be
willing to do some bug-hunting over there? For example, as a first step you
could uncomment (remove the '#' sign; I don't know how perl-aware you are so
excuse me if you knew that and/or a lot more already) line 110, which says:
#print $token->exact_print, unless $type eq "Paragraph";
Then run reLyX and send me the printout. (It may or may not choke with the
same error on line 110 as you had before on line 144. If so, try changing
"exact_print" to "print" which seems to be working.)
If anyone else has ideas, feel free to send them.
-Amir
