spurious group closing symbol.
I look in file, and the nesting of layout and inset is crossed up.
I am not doing anything special.
This seems like a pretty major bug.
Is it just me ? Or are other people having same problems ?
I looked in the bug tracker(lyx.org/trac) and didn't see anything
2012/5/6 Bert Douglas:
Brand new document. One page long.
All defaults.
Make a table.
Type some names in a column.
Then insert index entry after names, using cut and paste of name into index.
After doing this I get message about spurious group closing symbol.
I look in file
spurious group closing symbol.
I look in file, and the nesting of layout and inset is crossed up.
I am not doing anything special.
This seems like a pretty major bug.
Is it just me ? Or are other people having same problems ?
I looked in the bug tracker(lyx.org/trac) and didn't see anything
2012/5/6 Bert Douglas:
Brand new document. One page long.
All defaults.
Make a table.
Type some names in a column.
Then insert index entry after names, using cut and paste of name into index.
After doing this I get message about spurious group closing symbol.
I look in file
spurious group closing symbol.
I look in file, and the nesting of layout and inset is crossed up.
I am not doing anything special.
This seems like a pretty major bug.
Is it just me ? Or are other people having same problems ?
I looked in the bug tracker(lyx.org/trac) and didn't see anything
2012/5/6 Bert Douglas:
> Brand new document. One page long.
> All defaults.
> Make a table.
> Type some names in a column.
> Then insert index entry after names, using cut and paste of name into index.
>
> After doing this I get message about spurious group closing sym
On Fri, 2010-05-28 at 04:19 +0200, Uwe Stöhr wrote:
Please send the next time a _small_ LyX example file.
Okay. I wasn't sure WHERE the actual error was though.
The bug occurs because you sometimes set the tables as being part of the
paragraph headings.
Sometimes you also set the
On Fri, 2010-05-28 at 04:19 +0200, Uwe Stöhr wrote:
Please send the next time a _small_ LyX example file.
Okay. I wasn't sure WHERE the actual error was though.
The bug occurs because you sometimes set the tables as being part of the
paragraph headings.
Sometimes you also set the
On Fri, 2010-05-28 at 04:19 +0200, Uwe Stöhr wrote:
>
> Please send the next time a _small_ LyX example file.
Okay. I wasn't sure WHERE the actual error was though.
>
> The bug occurs because you sometimes set the tables as being part of the
> paragraph headings.
> Sometimes you also set
inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Besides not being able to find the offending }.
1) What is usually the cause of this? I do a lot of copy/cut - paste.
2) Exactly where
Am 27.05.2010 23:46, schrieb Tim Cook:
LyX version - 1.6.5
I have a document at:
http://bazaar.launchpad.net/~mlhim-specs-dev/mlhim-specs/main/annotate/head:/specs/1.0.x/mlhim/mlhim-ref-man-1.0.0-enUS.lyx
That generates an error when exporting to PDF (pdflatex ps2pdf):
First line of error:
inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Besides not being able to find the offending }.
1) What is usually the cause of this? I do a lot of copy/cut - paste.
2) Exactly where
Am 27.05.2010 23:46, schrieb Tim Cook:
LyX version - 1.6.5
I have a document at:
http://bazaar.launchpad.net/~mlhim-specs-dev/mlhim-specs/main/annotate/head:/specs/1.0.x/mlhim/mlhim-ref-man-1.0.0-enUS.lyx
That generates an error when exporting to PDF (pdflatex ps2pdf):
First line of error:
just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Besides not being able to find the offending }.
1) What is usually the cause of this? I do a lot of copy/cut - paste.
2) Exactly w
Am 27.05.2010 23:46, schrieb Tim Cook:
LyX version - 1.6.5
I have a document at:
http://bazaar.launchpad.net/~mlhim-specs-dev/mlhim-specs/main/annotate/head:/specs/1.0.x/mlhim/mlhim-ref-man-1.0.0-enUS.lyx
That generates an error when exporting to PDF (pdflatex& ps2pdf):
First line of error:
Paul,
Eventually, I surrendered and set Yap to use DVIPS by default.
Good idea, thank you for this hint.
Regards,
Tom Schlangen
--
Paul,
Eventually, I surrendered and set Yap to use DVIPS by default.
Good idea, thank you for this hint.
Regards,
Tom Schlangen
--
Paul,
> Eventually, I surrendered and set Yap to use DVIPS by default.
Good idea, thank you for this hint.
Regards,
Tom Schlangen
--
graphics spurious but reproducible errors show up in YAP, which just look
like a missing needle in a matrix printer output would do.
Since generating just postscript output to printer or generating PDF to file
output doesn´t show such rendering errors, the problem might just be in YAP
, in such DVIPS rendered
.EPS graphics spurious but reproducible errors show up in YAP, which just look
like a missing needle in a matrix printer output would do.
Since generating just postscript output to printer or generating PDF to file
output doesn´t show such rendering errors, the problem might just
graphics spurious but reproducible errors show up in YAP, which just look
like a missing needle in a matrix printer output would do.
Since generating just postscript output to printer or generating PDF to file
output doesn´t show such rendering errors, the problem might just be in YAP
, in such DVIPS rendered
.EPS graphics spurious but reproducible errors show up in YAP, which just look
like a missing needle in a matrix printer output would do.
Since generating just postscript output to printer or generating PDF to file
output doesn´t show such rendering errors, the problem might just
graphics spurious but reproducible errors show up in YAP, which just look
like a missing needle in a matrix printer output would do.
Since generating just postscript output to printer or generating PDF to file
output doesn´t show such rendering errors, the problem might just be in YAP
, in such DVIPS rendered
.EPS graphics spurious but reproducible errors show up in YAP, which just look
like a missing needle in a matrix printer output would do.
Since generating just postscript output to printer or generating PDF to file
output doesn´t show such rendering errors, the problem might just
24 matches
Mail list logo
