that stage.
On Sat, Mar 17, 2012 at 9:31 AM, Vincent van Ravesteijn wrote:
> Op 17-3-2012 16:06, Nathan Becker schreef:
>
>> Hi,
>>
>> I am not certain if this is a bug or if I am using LyX incorrectly.
>> Since the behavior changed between 2.0.2 and 2.0.3 I susp
Hi,
I am not certain if this is a bug or if I am using LyX incorrectly.
Since the behavior changed between 2.0.2 and 2.0.3 I suspect that it
may be a bug, so I'm reporting it here. Please let me know if there
is something that I'm supposed to change in my document to fix this.
I have created a s
Thank you for the advice on binutils. I managed to get LyX to compile
and run by rolling back to a pre10.2 Slamd64 of binutils which was
binutils-2.15.92.0.2-x86_64-2.tgz
Hope this helps anyone else who runs into this problem. Apparently
the newer version of binutils (2.16.92) does not like so
Hi,
I'm trying to compile LyX 1.4.3 on Slamd64 11.0. I used to be able to do
this on Slamd64 10.1 and I recently did a reformat/reinstall of my
system.
It seems to get through the entire compile process and then barf on
the final linking. I've tried forcing library paths to /usr/lib64 and
so o
Hi,
Here is what I think is a bug in LyX 1.1.6fix1 (the current stable version at
this time).
I was trying to insert the Angstrom symbol into an equation. While in math
mode I embedded \textrm{\AA}. The resulting postscript output looks correct.
However after saving the .lyx file and coming b
test.lyx
Export the document to postscript. LyX should warn the user or suggest a
changed name for the exported postscript file.
-Nathan Becker