> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Ok, this is not really hard to avoid. I'll have a look.
Please tell me when you fix it so that I can apply that to 1.1.5fix
also. It would be nice if we could read files with the wrong format
too...
JMarc
Hi,
I've just loaded LyX for the first time while installing SUSE 6.4 on a
Toshiba laptop (Satellite Pro 420CDT). I am not able to get LyX to
run. When starting I get the message:
lyx: SIGSEGV signal caught
Sorry you have found a bug
I am not able to check the 'known bugs' since I
On Tue, 29 Aug 2000, David Schwellenbach wrote:
Hi,
I've just loaded LyX for the first time while installing SUSE 6.4 on a
Toshiba laptop (Satellite Pro 420CDT). I am not able to get LyX to
run. When starting I get the message:
lyx: SIGSEGV signal caught
Sorry you have found a
Hi,
I've just loaded LyX for the first time while installing SUSE 6.4 on a
Toshiba laptop (Satellite Pro 420CDT). I am not able to get LyX to
run. When starting I get the message:
lyx: SIGSEGV signal caught
Sorry you have found a bug
I am not able to check the 'known bugs' since I
On Tue, 29 Aug 2000, David Schwellenbach wrote:
> Hi,
>
> I've just loaded LyX for the first time while installing SUSE 6.4 on a
> Toshiba laptop (Satellite Pro 420CDT). I am not able to get LyX to
> run. When starting I get the message:
> lyx: SIGSEGV signal caught
> Sorry you have found a
Hi,
look at the attached lyx file. For some reason, Lyx does not print the star in
the bottom left corner.
Michael
--
==
Michael Schmittphone: +49 451 500 3725
Institute for Telematics
Michael Schmitt [EMAIL PROTECTED] writes:
| Hi,
|
| look at the attached lyx file. For some reason, Lyx does not print
| the star in
| the bottom left corner.
Put {} marked as TeX in front of it.
Lgb
On Tue, Aug 15, 2000 at 11:42:03AM +0930, David McIver wrote:
Hello,
I recently upgraded from version 1.1.4 to 1.1.5fix1. I found that a
document that worked perfectly under 1.1.4 no longer worked under
1.1.5fix1. I am using the harvard bibliography style, which triggers the
problem. I get
Hi,
look at the attached lyx file. For some reason, Lyx does not print the star in
the bottom left corner.
Michael
--
==
Michael Schmittphone: +49 451 500 3725
Institute for Telematics
Michael Schmitt <[EMAIL PROTECTED]> writes:
| Hi,
|
| look at the attached lyx file. For some reason, Lyx does not print
| the star in
| the bottom left corner.
Put {} marked as TeX in front of it.
Lgb
On Tue, Aug 15, 2000 at 11:42:03AM +0930, David McIver wrote:
> Hello,
>
> I recently upgraded from version 1.1.4 to 1.1.5fix1. I found that a
> document that worked perfectly under 1.1.4 no longer worked under
> 1.1.5fix1. I am using the harvard bibliography style, which triggers the
> problem.
Hello,
I recently upgraded from version 1.1.4 to 1.1.5fix1. I found that a
document that worked perfectly under 1.1.4 no longer worked under
1.1.5fix1. I am using the harvard bibliography style, which triggers the
problem. I get errors when I use the \citeasnoun latex command in the
caption of a
Hello,
I recently upgraded from version 1.1.4 to 1.1.5fix1. I found that a
document that worked perfectly under 1.1.4 no longer worked under
1.1.5fix1. I am using the harvard bibliography style, which triggers the
problem. I get errors when I use the \citeasnoun latex command in the
caption of a
Hi everyone,
Something has changed in the last few incarnations of lyx-1.1.6cvs.
The Literate build errors no longer show up. Does anyone know why?
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc.| Laura Isabella Sylvan |
Hi everyone,
Something has changed in the last few incarnations of lyx-1.1.6cvs.
The Literate build errors no longer show up. Does anyone know why?
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc.| Laura Isabella Sylvan |
Further to this report. Clicking on almost any (not quite all) of the layout
options causes this crash. Swapping the math macro and "h" around so that the
math macro is at the top of the document, then making "h" a title is stable.
I don't have time today to look at this.
Anyone else?
Angus
On
Further to this report. Clicking on almost any (not quite all) of the layout
options causes this crash. Swapping the math macro and "h" around so that the
math macro is at the top of the document, then making "h" a title is stable.
I don't have time today to look at this.
Anyone else?
Angus
On
Excellent bug report, Thomas.
A further note:
When cutting, moving, pasting the "BibTeX Generated References", the Database
no longer refers to "new" but to "BibTeX"! Changing this back to "new" does
not, however, prevent the crash.
This happens with cu
The following one line fix squahes this bug:
Jean-Marc could you apply this to your 1.1.5 fix branch, please.
Anyone, could you apply it to current CVS.
Many thanks again for the bug report, Thomas
Angus
Index: src/insets/insetbib.h
Using current CVS with NEW_INSERTS and NEW_TABULAR enabled I can crash lyx by
opening a read-only document. Opening a copy of the same document with write
permissions all is fine.
This is not the case with a cvs of 19 July.
Angus
Here's another one: Make LyX crash with only 2 mouse-clicks :-(
I found the following bug in lyx-1.1.5fix1-1 (Linux RPM), which makes LyX
abort with the message "lyx: SIGSEGV signal caught".
It is reproducible in the following way:
Run: /usr/bin/lyx lyxbug2.lyx
Click on format menu, then on
Excellent bug report, Thomas.
A further note:
When cutting, moving, pasting the "BibTeX Generated References", the Database
no longer refers to "new" but to "BibTeX"! Changing this back to "new" does
not, however, prevent the crash.
This happens with cu
The following one line fix squahes this bug:
Jean-Marc could you apply this to your 1.1.5 fix branch, please.
Anyone, could you apply it to current CVS.
Many thanks again for the bug report, Thomas
Angus
Index: src/insets/insetbib.h
Using current CVS with NEW_INSERTS and NEW_TABULAR enabled I can crash lyx by
opening a read-only document. Opening a copy of the same document with write
permissions all is fine.
This is not the case with a cvs of 19 July.
Angus
Here's another one: Make LyX crash with only 2 mouse-clicks :-(
I found the following bug in lyx-1.1.5fix1-1 (Linux RPM), which makes LyX
abort with the message "lyx: SIGSEGV signal caught".
It is reproducible in the following way:
Run: /usr/bin/lyx lyxbug2.lyx
Click on format menu, then on
I found the following bug in lyx-1.1.5fix1-1 (Linux RPM), which makes LyX
abort with the message "lyx: SIGSEGV signal caught".
It is reproducible in the following way:
run "/usr/bin/lyx tesi.lyx"
Menu "Insert - Lists TOC - BibTeX Reference"
In Database field, type "new", Return
Type:
Hi! I'd like to report some anomalies that appeared in yesterday's cvs.
i386/xforms-0.88.1-1
I'm using the default lyxrc and lib/ui/default.ui
-Sometimes the menu mames doesn't update (refresh) correctly. (in some
cases, they disapear when another window has appeared on top of it). I can
explain
I found the following bug in lyx-1.1.5fix1-1 (Linux RPM), which makes LyX
abort with the message "lyx: SIGSEGV signal caught".
It is reproducible in the following way:
run "/usr/bin/lyx tesi.lyx"
Menu "Insert -> Lists & TOC -> BibTeX Reference"
In Database field, type "new", Return
Type:
Hi! I'd like to report some anomalies that appeared in yesterday's cvs.
i386/xforms-0.88.1-1
I'm using the default lyxrc and lib/ui/default.ui
-Sometimes the menu mames doesn't update (refresh) correctly. (in some
cases, they disapear when another window has appeared on top of it). I can
explain
Reading an old lyx file with current CVS, I notice that protected blanks are
converted to
SpecialChar \-
rather than
SpecialChar ~
Angus
this after I'd been
editing the file for a while and saved things a few times, so my original is no
more and I've no idea what the original lyx file contained (ie what lyx code.
It was written originally to be a protected space.)
Presumably, therefore, this is now a useless bug report. It may crop up
a useless bug report. It may crop up again
in more useful guise.
Hi,
maybe it was a file, with the "temporary" protected blank?
Don't remember the exact intermediate value
(\SpecialChar \protected_separator?).
Regards
Reading an old lyx file with current CVS, I notice that protected blanks are
converted to
SpecialChar \-
rather than
SpecialChar ~
Angus
pace.) Of course, I only noticed this after I'd been
editing the file for a while and saved things a few times, so my original is no
more and I've no idea what the original lyx file contained (ie what lyx code.
It was written originally to be a protected space.)
Presumably, therefore, this is now a us
; It was written originally to be a protected space.)
>
> Presumably, therefore, this is now a useless bug report. It may crop up again
> in more useful guise.
Hi,
maybe it was a file, with the "temporary" protected blank?
Don't rememb
"Joao" == Joao Cardoso [EMAIL PROTECTED] writes:
Joao Well, it was not only the cursor blink that consumed cpu time;
Joao it was the lyxserver! As a matter of fact, the cursor blink only
Joao wasted a *very* small amount of cpu.
Yes, on some systems, the lyxserver uses a lot of CPU time
This occurs with current CVS
Attached is a small lyx file. It looks like:
para1 para1 para1
para2 para2 para2
para3 para3 para3
If I place the cursor between the first and second "para1"s and then use
Shift-Down Arrow to highlight text, then all is Ok.
If, however, I insert an extra space
> "Joao" == Joao Cardoso <[EMAIL PROTECTED]> writes:
Joao> Well, it was not only the cursor blink that consumed cpu time;
Joao> it was the lyxserver! As a matter of fact, the cursor blink only
Joao> wasted a *very* small amount of cpu.
Yes, on some systems, the lyxserver uses a lot of CPU
This occurs with current CVS
Attached is a small lyx file. It looks like:
para1 para1 para1
para2 para2 para2
para3 para3 para3
If I place the cursor between the first and second "para1"s and then use
Shift-Down Arrow to highlight text, then all is Ok.
If, however, I insert an extra space
Hi folks,
The spell checker no longer seems to highlight the found words.
---Kayvan
Hi folks,
The spell checker no longer seems to highlight the found words.
---Kayvan
| 1-lyx is always running, consuming CPU time. You can check it with
| 'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
|
| IIRC, this is a xforms problem, at least I remember to see reports
| of that.
No, this is our prolem. It is the cursor blink that uses CPU.
> | > 1-lyx is always running, consuming CPU time. You can check it with
> | > 'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
> |
> | IIRC, this is a xforms problem, at least I remember to see reports
> | > of that.
>
> No, this is our prolem. It is the cursor blink that
On Thu, Jul 06, 2000 at 03:19:36AM +0100, Joao Cardoso wrote:
Hi,
First of all, thanks for lyx!
Obrigado. ;)
In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
1-lyx is always running, consuming CPU time. You can check it with
'top'. This is a problem, as I always have lyx (and
Jose Abilio Oliveira Matos [EMAIL PROTECTED] writes:
| 1-lyx is always running, consuming CPU time. You can check it with
| 'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
|
| IIRC, this is a xforms problem, at least I remember to see reports
| of that.
No, this is
Jose Abilio Oliveira Matos wrote:
On Thu, Jul 06, 2000 at 03:19:36AM +0100, Joao Cardoso wrote:
Hi,
First of all, thanks for lyx!
Obrigado. ;)
[only to Jose] Ola! tambem em participei no lyx, nos tempos da versao
0.10.
In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
Joao Cardoso [EMAIL PROTECTED] writes:
| Hi,
|
| First of all, thanks for lyx!
|
| In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
|
| 1-lyx is always running, consuming CPU time. You can check it with
| 'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
problem or
On Thu, Jul 06, 2000 at 03:19:36AM +0100, Joao Cardoso wrote:
>
> Hi,
>
> First of all, thanks for lyx!
Obrigado. ;)
> In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
>
> 1-lyx is always running, consuming CPU time. You can check it with
> 'top'. This is a problem, as I always have
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
| > 1-lyx is always running, consuming CPU time. You can check it with
| > 'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
|
| IIRC, this is a xforms problem, at least I remember to see reports
| > of that.
No, this
Jose Abilio Oliveira Matos wrote:
>
> On Thu, Jul 06, 2000 at 03:19:36AM +0100, Joao Cardoso wrote:
> >
> > Hi,
> >
> > First of all, thanks for lyx!
>
> Obrigado. ;)
[only to Jose] Ola! tambem em participei no lyx, nos tempos da versao
0.10.
>
> > In 1.1.5, on sco-3.2v5.0.4, I detected
Joao Cardoso <[EMAIL PROTECTED]> writes:
| Hi,
|
| First of all, thanks for lyx!
|
| In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
|
| 1-lyx is always running, consuming CPU time. You can check it with
| 'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
problem or
Hi,
First of all, thanks for lyx!
In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
1-lyx is always running, consuming CPU time. You can check it with
'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
2-the screen font options in lyxrc are badly parsed. I use true type
Hi,
First of all, thanks for lyx!
In 1.1.5, on sco-3.2v5.0.4, I detected two problems:
1-lyx is always running, consuming CPU time. You can check it with
'top'. This is a problem, as I always have lyx (and xemacs) open ;-)
2-the screen font options in lyxrc are badly parsed. I use true type
"edscott" == edscott [EMAIL PROTECTED] writes:
edscott The first bug is that the .lyx file I opened, resided in a
edscott directory with *spaces* in it, (i.e. /blabla/blabla/full
edscott document). You will get the "missing \begin[document}" on any
edscott file opened or created in a directory
> "edscott" == edscott <[EMAIL PROTECTED]> writes:
edscott> The first bug is that the .lyx file I opened, resided in a
edscott> directory with *spaces* in it, (i.e. /blabla/blabla/full
edscott> document). You will get the "missing \begin[document}" on any
edscott> file opened or created in
"root" == root [EMAIL PROTECTED] writes:
root situation: A lyx file (created by 1.1.4) with 40 input lyx files
root (also 1.1.4) will not produce dvi or ps, but reports the
root following error (once):
root missing begin{document}
We would have to see the file (or a reduced version of it).
On Wed, 21 Jun 2000, Jean-Marc Lasgouttes wrote:
We would have to see the file (or a reduced version of it). Note that
1.1.4 was not as good as 1.1.5 for catching latex errors, so the
problem might have been there from the beginning.
Actually there were two bugs, yesterday. Trying to get
> "root" == root <[EMAIL PROTECTED]> writes:
root> situation: A lyx file (created by 1.1.4) with 40 input lyx files
root> (also 1.1.4) will not produce dvi or ps, but reports the
root> following error (once):
root> missing begin{document}
We would have to see the file (or a reduced
On Wed, 21 Jun 2000, Jean-Marc Lasgouttes wrote:
>
> We would have to see the file (or a reduced version of it). Note that
> 1.1.4 was not as good as 1.1.5 for catching latex errors, so the
> problem might have been there from the beginning.
>
Actually there were two bugs, yesterday. Trying
situation:
A lyx file (created by 1.1.4) with 40 input lyx files (also 1.1.4) will not
produce dvi or ps, but reports the following error (once):
missing begin{document}
Each of the included files (about 5 pages long each), will produce dvi and ps
correctly when viewed independently.
Extra
situation:
A lyx file (created by 1.1.4) with 40 input lyx files (also 1.1.4) will not
produce dvi or ps, but reports the following error (once):
missing begin{document}
Each of the included files (about 5 pages long each), will produce dvi and ps
correctly when viewed independently.
Extra
On Thu, May 25, 2000 at 12:07:58PM +0300, Baruch Even wrote:
There is a bug with the insert reference stuff, the dialog one and not the
main menu.
The problem seems to come from the fact that the buttons in the insert
reference are active even when there is no label to enter. Pressing one
Dekel Tsur [EMAIL PROTECTED] writes:
| I've done this (and also I also modified the Refs menu code to disable the
| menus when buffer is readonly etc.)
In. Lgb
There is a bug with the insert reference stuff, the dialog one and not the
main menu.
The problem seems to come from the fact that the buttons in the insert
reference are active even when there is no label to enter. Pressing one of
them say "Insert reference" will cause a core dump. Possible
On Thu, May 25, 2000 at 12:07:58PM +0300, Baruch Even wrote:
> There is a bug with the insert reference stuff, the dialog one and not the
> main menu.
>
> The problem seems to come from the fact that the buttons in the insert
> reference are active even when there is no label to enter. Pressing
Dekel Tsur <[EMAIL PROTECTED]> writes:
| I've done this (and also I also modified the Refs menu code to disable the
| menus when buffer is readonly etc.)
In. Lgb
There is a bug with the insert reference stuff, the dialog one and not the
main menu.
The problem seems to come from the fact that the buttons in the insert
reference are active even when there is no label to enter. Pressing one of
them say "Insert reference" will cause a core dump. Possible
and pasting there, then importing
ascii :-)
Message is
Sorry, you have found a bug in LyX. If possible, please read 'Known bugs'
under the Help menu and then send us a full bug report. Thanks!
lyx: Attempting to save document /usr0/dellaert/papers/mcmc/nips2000.lyx
as...
1) /usr0/dellaert/papers
and pasting there, then importing
ascii :-)
Message is
Sorry, you have found a bug in LyX. If possible, please read 'Known bugs'
under the Help menu and then send us a full bug report. Thanks!
lyx: Attempting to save document /usr0/dellaert/papers/mcmc/nips2000.lyx
as...
1) /usr0/dellaert/papers
On Thu, May 11, 2000 at 01:42:21PM +0300, Lior Silberman wrote:
The two methods for empty enumeration points are radically different.
Putting a nonbreaking space gives (in the dvi)
1.
(a)
(b)
while using an empty {} gives:
(a)
(b)
Without the 1. !
No, it should generate
Hi,
I'm a happy user of lyx hawever I think I've found a bug
when try to copy paste from two files in thr same lyx
copiying from the first file, closing the file
then pasting the copy buffer to the second file
it suddently dyes and leave this message:
ERROR (LyXParagraph::ParFromPos):
On Thu, May 11, 2000 at 01:42:21PM +0300, Lior Silberman wrote:
> The two methods for empty enumeration points are radically different.
> Putting a nonbreaking space gives (in the dvi)
> 1.
> (a)
> (b)
>
> while using an empty {} gives:
> (a)
> (b)
>
> Without the 1. !
No, it should
Hi,
I'm a happy user of lyx hawever I think I've found a bug
when try to copy paste from two files in thr same lyx
copiying from the first file, closing the file
then pasting the copy buffer to the second file
it suddently dyes and leave this message:
ERROR (LyXParagraph::ParFromPos):
Thanks for the help!
First, I wanted to report a bug. When you are start the next point in an
enumeration, I would expect the enumeration depth should remain as in the
previous point (If I have 1a it's almost certain to be followed by 1b and
not 2).
I tried debugging the code, and found the
"Lior" == Lior Silberman [EMAIL PROTECTED] writes:
Lior Thanks for the help! First, I wanted to report a bug. When you
Lior are start the next point in an enumeration, I would expect the
Lior enumeration depth should remain as in the previous point (If I
Lior have 1a it's almost certain to be
Jean-Marc Lasgouttes wrote:
So it seems to me that Return (break-paragraph) can go back in depth
_if_ it changes the layout too.
Comments?
I suppose you mean environment instead of layout there.
I remember being surprised when I first used verse. There are many more
lines than stanzas, and
Thanks for the help!
First, I wanted to report a bug. When you are start the next point in an
enumeration, I would expect the enumeration depth should remain as in the
previous point (If I have 1a it's almost certain to be followed by 1b and
not 2).
I tried debugging the code, and found the
> "Lior" == Lior Silberman <[EMAIL PROTECTED]> writes:
Lior> Thanks for the help! First, I wanted to report a bug. When you
Lior> are start the next point in an enumeration, I would expect the
Lior> enumeration depth should remain as in the previous point (If I
Lior> have 1a it's almost
Jean-Marc Lasgouttes wrote:
> So it seems to me that Return (break-paragraph) can go back in depth
> _if_ it changes the layout too.
>
> Comments?
I suppose you mean environment instead of layout there.
I remember being surprised when I first used verse. There are many more
lines than stanzas,
"Yves" == Yves Pocchiola [EMAIL PROTECTED] writes:
Yves BUG REPORT TESTED VERSION: Lyx1-1.1.5pre1
Yves DESCRIPTION: DOCUMENT LAYOUT: AMS (unnumbered) TEXT WRITTEN:
Yves Titre (Title) Introduction (Part*) Prologue (Part) REPORTED
Yves ERROR BY LyX: Missing control sequence inserted [.
BUG REPORT
TESTED VERSION: Lyx1-1.1.5pre1
DESCRIPTION:
DOCUMENT LAYOUT: AMS (unnumbered)
TEXT WRITTEN:
Titre (Title)
Introduction (Part*)
Prologue (Part)
REPORTED ERROR BY LyX:
Missing control sequence inserted
>>>>> "Yves" == Yves Pocchiola <[EMAIL PROTECTED]> writes:
Yves> BUG REPORT TESTED VERSION: Lyx1-1.1.5pre1
Yves> DESCRIPTION: DOCUMENT LAYOUT: AMS (unnumbered) TEXT WRITTEN:
Yves> Titre (Title) Introduction (Part*) Prologue (Part) REPORTED
Yves> ERRO
BUG REPORT
TESTED VERSION: Lyx1-1.1.5pre1
DESCRIPTION:
DOCUMENT LAYOUT: AMS (unnumbered)
TEXT WRITTEN:
Titre (Title)
Introduction (Part*)
Prologue (Part)
REPORTED ERROR BY LyX:
Missing control sequence inserted
"Kevin" == Kevin Atkinson [EMAIL PROTECTED] writes:
Kevin Even when aspell is set in lyxrc it will STILL use ispell. Fix,
Kevin change the line.
Kevin execvp("ispell", const_castchar * const *(argv));
Kevin to
Kevin execvp(argv[0], const_castchar * const *(argv));
Duh! I had a quick look
> "Kevin" == Kevin Atkinson <[EMAIL PROTECTED]> writes:
Kevin> Even when aspell is set in lyxrc it will STILL use ispell. Fix,
Kevin> change the line.
Kevin> execvp("ispell", const_cast(argv));
Kevin> to
Kevin> execvp(argv[0], const_cast(argv));
Duh! I had a quick look when you reported
Even when aspell is set in lyxrc it will STILL use ispell. Fix, change
the line.
execvp("ispell", const_castchar * const *(argv));
to
execvp(argv[0], const_castchar * const *(argv));
(in spellchecker.C) so that it will actually call aspell!
Otherwise it will call ispell but will look
Even when aspell is set in lyxrc it will STILL use ispell. Fix, change
the line.
execvp("ispell", const_cast(argv));
to
execvp(argv[0], const_cast(argv));
(in spellchecker.C) so that it will actually call aspell!
Otherwise it will call ispell but will look like aspell because argv[0]
Hello, I have a small bug report.
Environment: Slackware Linux, heavy hacked (mix of 3.4 and 4.0) with
egcs-2.91.66, libc.so.5.4.46, XFree86 3.3.1, XForms 0.88.1,
GNU binutils 2.9.1.0.19a, GNU gettext-0.10.35,
3.4k (with libXpm.so.4.11), teTeX-0.9-990309
LyX
Hello, I have a small bug report.
Environment: Slackware Linux, heavy hacked (mix of 3.4 and 4.0) with
egcs-2.91.66, libc.so.5.4.46, XFree86 3.3.1, XForms 0.88.1,
GNU binutils 2.9.1.0.19a, GNU gettext-0.10.35,
3.4k (with libXpm.so.4.11), teTeX-0.9-990309
LyX
ib/libxforms.so.0
#6 0x80ae8ad in LyXGUI::runTime ()
#7 0x80afcb5 in LyX::LyX ()
#8 0x80d844f in main ()
#9 0x804f9ed in _start ()
(gdb) cont
Continuing.
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. If possible, please read 'Known bugs'
under the Help menu and then send us
I found a bug that can be reproduced as shown below:
I can confirm this for a fairly recent 1.1.5cvs.
Maybe it is time to add a big warning to 1.1.4 and refer people to older
versions...
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL
Andre Poenitz [EMAIL PROTECTED] writes:
| I found a bug that can be reproduced as shown below:
|
| I can confirm this for a fairly recent 1.1.5cvs.
| Maybe it is time to add a big warning to 1.1.4 and refer people to older
| versions...
Or help to quickly find the real problems...
in fl_check_forms () from /usr/X11R6/lib/libxforms.so.0
#6 0x80ae8ad in LyXGUI::runTime ()
#7 0x80afcb5 in LyX::LyX ()
#8 0x80d844f in main ()
#9 0x804f9ed in _start ()
(gdb) cont
Continuing.
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. If possible, please read 'Known bugs'
> I found a bug that can be reproduced as shown below:
I can confirm this for a fairly recent 1.1.5cvs.
Maybe it is time to add a big warning to 1.1.4 and refer people to older
versions...
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > I found a bug that can be reproduced as shown below:
|
| I can confirm this for a fairly recent 1.1.5cvs.
| Maybe it is time to add a big warning to 1.1.4 and refer people to older
| versions...
Or help to quickly find the real problems...
I am using the binary versions of lyx (rpm). I found this bug in lyx-1.1.3
but the same bug persists even after I've upgraded to lyx 1.1.4fix1.
I've turned on the server. The server pipes are the defaults ".lyxpipe.in"
and ".lyxpipe.out". When I send the command "buffer-new:" by the following
I am using the binary versions of lyx (rpm). I found this bug in lyx-1.1.3
but the same bug persists even after I've upgraded to lyx 1.1.4fix1.
I've turned on the server. The server pipes are the defaults ".lyxpipe.in"
and ".lyxpipe.out". When I send the command "buffer-new:" by the following
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel I've added a counter to the loop, so the loop can be exited if
Dekel a 'l.' line isn't found after a certain number of lines. Also,
Dekel I've changed scanLogFile to ignore multiple errors at the same
Dekel line in the latex file (only first
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> I've added a counter to the loop, so the loop can be exited if
Dekel> a 'l.' line isn't found after a certain number of lines. Also,
Dekel> I've changed scanLogFile to ignore multiple errors at the same
Dekel> line in the latex file
On Fri, Feb 25, 2000 at 08:30:26PM +0100, Lars Gullik Bjnnes wrote:
|
| I've added a counter to the loop, so the loop can be exited if a 'l.'
| line isn't found after a certain number of lines.
| Also, I've changed scanLogFile to ignore multiple errors at the same line in
| the latex file
801 - 900 of 1196 matches
Mail list logo
