Re: Table row shading throws compile error

[Rich Shepard]

On Wed, 6 Jul 2022, Herbert Voss wrote:

I tried this in a fresh document (KomaScript Report class) by adding 
\usepackage{xcolor, colortbl} to the preamble, and my table with your ERT 
and column name in row 1, column 1 compiled just fine. You didn't specify 
what module you are using, and a MWE would be helpful.


\usepackage[table]{xcolor}
does the same


Herbert,

Thanks for this alternative. I missed seeing it in your LaTeX table book.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Table row shading throws compile error

[Rich Shepard]

On Wed, 6 Jul 2022, Daniel wrote:


As a workaround you could use an ERT with
\cellcolor{lightgray}
in each cell.


Daniel,

I've never before used colors in tables so I'm new to doing so. Because this
document is going to a regulatory agency whose staff can be fussy about
appearences I decided to add a bit of glitter to the header rows of the few
tables in the document.

Using \cellcolor{} does the job, and for my very infrequent use it's the
solution I'll use.

Thanks very much,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Table row shading throws compile error

[Herbert Voss]

Am 05.07.22 um 23:54 schrieb Paul A. Rubin:

On 7/5/22 17:37, Rich Shepard wrote:

I suspect this is another outdated module issue but I've not seen the
reason.

The first column in row 1 of a table contains the ERT 
\rowcolor{lightgray}

Species Common Name. TeX doesn't like it; see attached error log. It is
ignored but I'd like to fix the issue.

Rich



I tried this in a fresh document (KomaScript Report class) by adding 
\usepackage{xcolor, colortbl} to the preamble, and my table with your 
ERT and column name in row 1, column 1 compiled just fine. You didn't 
specify what module you are using, and a MWE would be helpful.


\usepackage[table]{xcolor}

does the same


HErbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Table row shading throws compile error

[Daniel]

On 06/07/2022 00:55, Paul A. Rubin wrote:

On 7/5/22 18:14, Rich Shepard wrote:

On Tue, 5 Jul 2022, Paul A. Rubin wrote:


I tried this in a fresh document (KomaScript Report class) by adding
\usepackage{xcolor, colortbl} to the preamble, and my table with your 
ERT
and column name in row 1, column 1 compiled just fine. You didn't 
specify

what module you are using, and a MWE would be helpful.


Paul,

I had \usepackage{colortbl}; just added xcolor. Made no difference. MWE
attached, with the build log.

Thanks,

Rich

Well, the introduction of table borders causes LyX to introduce 
"multicolumns" of one column each, which somehow seems to conflict 
(slightly) with the \rowcolor command. Maybe a TeXpert can figure out a 
workaround, but I suspect this is one of those LaTeX things you just 
need to accept ... unless maybe you want to experiment with using LaTeX 
commands to introduce the border lines yourself.


FWIW, I tried editing the LaTeX to move the \rowcolor file before rather 
than in the first cell. It seemed to fix the problem, but I can't find 
any way in LyX to wedge a custom command/setting into a table before the 
first row. The Embedded Objects help manual says to color rows the way 
you are currently doing it, if that is any consolation.


Paul


For columns, LyX supports an ominous "LaTeX argument" in the table 
settings which injects LaTeX code into the column header. Maybe 
something similar would be needed for the row settings?


Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Table row shading throws compile error

[Daniel]

On 06/07/2022 00:14, Rich Shepard wrote:

On Tue, 5 Jul 2022, Paul A. Rubin wrote:


I tried this in a fresh document (KomaScript Report class) by adding
\usepackage{xcolor, colortbl} to the preamble, and my table with your ERT
and column name in row 1, column 1 compiled just fine. You didn't specify
what module you are using, and a MWE would be helpful.


Paul,

I had \usepackage{colortbl}; just added xcolor. Made no difference. MWE
attached, with the build log.

Thanks,

Rich


As a workaround you could use an ERT with

\cellcolor{lightgray}

in each cell.

Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Table row shading throws compile error

[Paul A. Rubin]

On 7/5/22 18:14, Rich Shepard wrote:

On Tue, 5 Jul 2022, Paul A. Rubin wrote:


I tried this in a fresh document (KomaScript Report class) by adding
\usepackage{xcolor, colortbl} to the preamble, and my table with your 
ERT
and column name in row 1, column 1 compiled just fine. You didn't 
specify

what module you are using, and a MWE would be helpful.


Paul,

I had \usepackage{colortbl}; just added xcolor. Made no difference. MWE
attached, with the build log.

Thanks,

Rich

Well, the introduction of table borders causes LyX to introduce 
"multicolumns" of one column each, which somehow seems to conflict 
(slightly) with the \rowcolor command. Maybe a TeXpert can figure out a 
workaround, but I suspect this is one of those LaTeX things you just 
need to accept ... unless maybe you want to experiment with using LaTeX 
commands to introduce the border lines yourself.


FWIW, I tried editing the LaTeX to move the \rowcolor file before rather 
than in the first cell. It seemed to fix the problem, but I can't find 
any way in LyX to wedge a custom command/setting into a table before the 
first row. The Embedded Objects help manual says to color rows the way 
you are currently doing it, if that is any consolation.


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Table row shading throws compile error

[Rich Shepard]

On Tue, 5 Jul 2022, Paul A. Rubin wrote:


I tried this in a fresh document (KomaScript Report class) by adding
\usepackage{xcolor, colortbl} to the preamble, and my table with your ERT
and column name in row 1, column 1 compiled just fine. You didn't specify
what module you are using, and a MWE would be helpful.


Paul,

I had \usepackage{colortbl}; just added xcolor. Made no difference. MWE
attached, with the build log.

Thanks,

Rich#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 544
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass scrreprt
\begin_preamble
\date{}
%\usepackage{newpxtext}
%\usepackage{newpxmath}
\usepackage{mathpazo,amssymb}
\usepackage{graphicx,relsize}
\usepackage{scrlayer-scrpage}
\usepackage{xcolor,colortbl}
\definecolor{lightgray}{gray}{0.8}
\pagestyle{scrheadings}
\lehead{Biological Evaluation}
\rohead{Biological Evaluation}
\refoot{Applied Ecosystem Services, LLC}
\lofoot{Applied Ecosystem Services, LLC}
\automark*{section}
%DeclareNolabel{
%  \nolabel{\regexp{[\p{S}\p{Z}\p{C}]+}}
%}
\end_preamble
\options headsepline=on, footsepline=on
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding utf8
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\use_microtype false
\use_dash_ligatures true
\graphics default
\default_output_format pdf2
\output_sync 0
\bibtex_command biber mergedate=compact
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize letterpaper
\use_geometry true
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 0
\use_package mathdots 0
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine biblatex-natbib
\cite_engine_type authoryear
\biblatex_bibstyle authoryear
\biblatex_citestyle authoryear
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\use_minted 0
\index Index
\shortcut idx
\color #008000
\end_index
\leftmargin 2cm
\topmargin 4cm
\bottommargin 2cm
\headsep 1.5cm
\secnumdepth 2
\tocdepth 2
\paragraph_separation skip
\defskip medskip
\is_math_indent 0
\math_numbering_side default
\quotes_style english
\dynamic_quotes 0
\papercolumns 1
\papersides 2
\paperpagestyle plain
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Subsubsection*
I.
 Is the project located within designated/proposed critical habitat for
 any of these species?
\end_layout

\begin_layout Standard
\align center
\begin_inset Tabular







\begin_inset Text

\begin_layout Plain Layout
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
rowcolor{lightgray}
\end_layout

\end_inset

Species common name
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
Yes
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
No
\end_layout

\end_inset




\begin_inset Text

\begin_layout Plain Layout
Southern resident killer whale
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout

\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
checkmark
\end_layout

\end_inset


\end_layout

\end_inset




\begin_inset Text

\begin_layout Plain Layout
Marbled murrelet
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout

\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
checkmark
\end_layout

\end_inset


\end_layout

\end_inset




\begin_inset Text

\begin_layout Plain Layout
Northern spotted owl
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout

\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
checkmark
\end_layout

\end_inset


\end_layout

\end_inset




\begin_inset Text

\begin_layout Plain Layout
Western snowy plover
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout

\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
checkmark
\end_layout

\end_inset


\end_layout

\end_inset




\begin_inset Text

\begin_layout Plain Layout
Green sturgeon
\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout

\end_layout

\end_inset


\begin_inset Text

\begin_layout Plain Layout
\begin_inset ERT
status open

\begin_layout Plain Layout


\

Re: Table row shading throws compile error

[Paul A. Rubin]

On 7/5/22 17:37, Rich Shepard wrote:

I suspect this is another outdated module issue but I've not seen the
reason.

The first column in row 1 of a table contains the ERT 
\rowcolor{lightgray}

Species Common Name. TeX doesn't like it; see attached error log. It is
ignored but I'd like to fix the issue.

Rich



I tried this in a fresh document (KomaScript Report class) by adding 
\usepackage{xcolor, colortbl} to the preamble, and my table with your 
ERT and column name in row 1, column 1 compiled just fine. You didn't 
specify what module you are using, and a MWE would be helpful.


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Table row shading throws compile error

[Rich Shepard]

I suspect this is another outdated module issue but I've not seen the
reason.

The first column in row 1 of a table contains the ERT \rowcolor{lightgray}
Species Common Name. TeX doesn't like it; see attached error log. It is
ignored but I'd like to fix the issue.

Rich


The error message box says, "Misplaced \noalign.
...{\rowcolor{lightgray}Species common name} & I expect to see \noalign only
after the \cr of an alignment. Proceed, and I'll ignore this case.

The full error log:

This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2021 on Slint) 
(preloaded format=pdflatex 2021.10.13)  5 JUL 2022 14:16
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**biol-eval.tex
(./biol-eval.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18>
(/usr/share/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2021/03/17 v3.33 KOMA-Script document class (report)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2021/03/17 v3.33 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2021/03/17 v3.33 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2021/03/17 v3.33 KOMA-Script package (file load hooks)
(/usr/share/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
Package: scrlfile-hook 2021/03/17 v3.33 KOMA-Script package (using LaTeX hooks)


LaTeX3 Info: Defining command \BeforeFile with sig. 'm' on line 61.


LaTeX3 Info: Defining command \AfterFile with sig. 'm' on line 65.


LaTeX3 Info: Defining command \BeforeClass with sig. 'm' on line 69.


LaTeX3 Info: Defining command \BeforePackage with sig. 'm' on line 73.


LaTeX3 Info: Defining command \AfterAtEndOfClass with sig. 'smo+m' on line 83.


LaTeX3 Info: Defining command \AfterAtEndOfPackage with sig. 'smo+m' on line
(LaTeX3) 93.


LaTeX3 Info: Defining command \scrlfile@AfterClass with sig. 'smo+m' on line
(LaTeX3) 173.


LaTeX3 Info: Defining command \AfterClass with sig. '' on line 174.


LaTeX3 Info: Defining command \scrlfile@AfterPackage with sig. 'smo+m' on line
(LaTeX3) 191.


LaTeX3 Info: Defining command \AfterPackage with sig. '' on line 192.


LaTeX3 Info: Defining command \ReplaceInput with sig. '' on line 193.


LaTeX3 Info: Defining command \ReplaceClass with sig. 'mm' on line 196.


LaTeX3 Info: Defining command \ReplacePackage with sig. 'mm' on line 199.


LaTeX3 Info: Defining command \UnReplaceInput with sig. '' on line 200.


LaTeX3 Info: Defining command \UnReplaceClass with sig. 'm' on line 203.


LaTeX3 Info: Defining command \UnReplacePackage with sig. 'mm' on line 206.


LaTeX3 Info: Defining command \PreventPackageFromLoading with sig. 's+om' on
(LaTeX3) line 234.


LaTeX3 Info: Defining command \StorePreventPackageFromLoading with sig. 'm' on
(LaTeX3) line 242.


LaTeX3 Info: Defining command \ResetPreventPackageFromLoading with sig. '' on
(LaTeX3) line 247.


LaTeX3 Info: Defining command \UnPreventPackageFromLoading with sig. 'sm' on
(LaTeX3) line 261.


LaTeX3 Info: Defining command \BeforeClosingMainAux with sig. 'om' on line
(LaTeX3) 274.


LaTeX3 Info: Defining command \AfterReadingMainAux with sig. 'om' on line 287.


LaTeX3 Info: Defining command \protected@immediate@write with sig. 'm+m+m' on
(LaTeX3) line 298.

(/usr/share/texmf-dist/tex/latex/koma-script/scrlogo.sty
Package: scrlogo 2021/03/17 v3.33 KOMA-Script package (logo)
))) (/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks15
)
Skipping: [2021/05/01] Usage of raw option list on input line 252.
Applying: [/00/00] compatibility for LaTeX before 2021/05/01 on input line 
337.
)) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2021/03/17 v3.33 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip47
\scr@dte@tocline@numbox=\box47
)
Package tocbasic Info: babel extension for `toc' omitted
(tocbasic) because of missing \bbl@set@language on input line 137.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 245
1.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2021/03/17 v3.33 KOMA-Script font size class option (11pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2021/03/17 v3.33 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count179
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 418.2pt
(typearea)   

Re: Curious compile error, easily fixed

[Rich Shepard]

On Mon, 23 May 2022, Paul A. Rubin wrote:


From some long forgotten sci-fi movie, I think you fill the document with
a fine powder, shake, and hope it sticks to the invisible package (?).


Paul,

I think that's a recent conspiracy topic.


I created an empty document with the contents of your preamble and didn't
get any references to verbatim. Does your document contain code listings
or other funky elements that might automagically trigger a load of the
verbatim package? You may need to apply bisection to find out the culprit.


No. Code and similar funky elements would be in a verbatim environment.
T'ain't none of that stuff in this document. Other than standard body text
and tables, there are section*, sub-section*, and sub-sub-section* headers.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Curious compile error, easily fixed

[Paul A. Rubin]

On 5/23/22 13:54, Rich Shepard wrote:

On Fri, 20 May 2022, Paul A. Rubin wrote:


After the initial compilation attempt, you can open the generated .tex
file (lurking in the buffer directory) in a text editor and search 
for any

mention of verbatim. It could be that some module or funky document
element is using it. If there's more than one occurrence, the 
location of

the error in the document log window might help narrow down which one
triggered the error.


Paul,

I wonder if the SARS-COV-2 virus infected this document. Here's the 
preamble

as shown in Documents -> Settings -> Preamble:
\date{}
\usepackage{mathpazo}
\usepackage{graphicx,relsize}
\usepackage{scrlayer-scrpage}
\usepackage{colortbl}
\definecolor{lightgray}{gray}{0.8}
\pagestyle{scrheadings}
\lehead{Biological Evaluation}
\rohead{Biological Evaluation}
\refoot{Applied Ecosystem Services, LLC}
\lofoot{Applied Ecosystem Services, LLC}
\automark*{section}

And this is the preamble in /tmp/lyx_tmpdir.oskNDlV31096/lyx_tmpbuf1:
\batchmode
\makeatletter
\def\input@path{{/home/rshepard/projects/.../.../reports/}}
\makeatother
\documentclass[twoside,headsepline=on, footsepline=on]{scrreprt}
\PassOptionsToPackage{natbib=true}{biblatex}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage[letterpaper]{geometry}
\geometry{verbose,tmargin=4cm,bmargin=2cm,lmargin=2cm,headsep=1.5cm}
\pagestyle{plain}
\setlength{\parskip}{\medskipamount}
\setlength{\parindent}{0pt}
\usepackage{verbatim}
\usepackage{graphicx}

\makeatletter

I do not see any reference to the verbatim package in any settings dialog
box.

How do I remove an invisible package?

Regards,

Rich
From some long forgotten sci-fi movie, I think you fill the document 
with a fine powder, shake, and hope it sticks to the invisible package (?).


I created an empty document with the contents of your preamble and 
didn't get any references to verbatim. Does your document contain code 
listings or other funky elements that might automagically trigger a load 
of the verbatim package? You may need to apply bisection to find out the 
culprit.


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Curious compile error, easily fixed

[Rich Shepard]

On Fri, 20 May 2022, Paul A. Rubin wrote:


After the initial compilation attempt, you can open the generated .tex
file (lurking in the buffer directory) in a text editor and search for any
mention of verbatim. It could be that some module or funky document
element is using it. If there's more than one occurrence, the location of
the error in the document log window might help narrow down which one
triggered the error.


Paul,

I wonder if the SARS-COV-2 virus infected this document. Here's the preamble
as shown in Documents -> Settings -> Preamble:
\date{}
\usepackage{mathpazo}
\usepackage{graphicx,relsize}
\usepackage{scrlayer-scrpage}
\usepackage{colortbl}
\definecolor{lightgray}{gray}{0.8}
\pagestyle{scrheadings}
\lehead{Biological Evaluation}
\rohead{Biological Evaluation}
\refoot{Applied Ecosystem Services, LLC}
\lofoot{Applied Ecosystem Services, LLC}
\automark*{section}

And this is the preamble in /tmp/lyx_tmpdir.oskNDlV31096/lyx_tmpbuf1:
\batchmode
\makeatletter
\def\input@path{{/home/rshepard/projects/.../.../reports/}}
\makeatother
\documentclass[twoside,headsepline=on, footsepline=on]{scrreprt}
\PassOptionsToPackage{natbib=true}{biblatex}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage[letterpaper]{geometry}
\geometry{verbose,tmargin=4cm,bmargin=2cm,lmargin=2cm,headsep=1.5cm}
\pagestyle{plain}
\setlength{\parskip}{\medskipamount}
\setlength{\parindent}{0pt}
\usepackage{verbatim}
\usepackage{graphicx}

\makeatletter

I do not see any reference to the verbatim package in any settings dialog
box.

How do I remove an invisible package?

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Curious compile error, easily fixed

[Paul A. Rubin]

On 5/20/22 18:32, Rich Shepard wrote:

Attempting to compile a document using pdflatex halts with an error
referencing a verbatim@ environment. Since I've not explicitly used that
environment, and a search of the .lyx file doesn't find that word 
present, I
wonder why it suddenly decided to show up each time I use the chord, 
C-x h.


Regardless, when I close the error window and repeat C-x h pdflatex 
happily

compiles the file.

Has anyone a thought about why the error would appear if the environment
'verbatim' can't be found in the .lyx file?

Rich


After the initial compilation attempt, you can open the generated .tex 
file (lurking in the buffer directory) in a text editor and search for 
any mention of verbatim. It could be that some module or funky document 
element is using it. If there's more than one occurrence, the location 
of the error in the document log window might help narrow down which one 
triggered the error.


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Curious compile error, easily fixed

[Rich Shepard]

Attempting to compile a document using pdflatex halts with an error
referencing a verbatim@ environment. Since I've not explicitly used that
environment, and a search of the .lyx file doesn't find that word present, I
wonder why it suddenly decided to show up each time I use the chord, C-x h.

Regardless, when I close the error window and repeat C-x h pdflatex happily
compiles the file.

Has anyone a thought about why the error would appear if the environment
'verbatim' can't be found in the .lyx file?

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Dr Eberhard Lisse]

Rich,

you are welcome :-)-O


I would not spend much time focussing on the latel/cite key.  Since that
does not appear in the PDF (only the names do, and they allow
apostrophes) just remove the apostrophe(s) in the label and citations.

el


On 13/10/2021 18:57, Rich Shepard wrote:

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


BibTeX does not like Apostropes "'" in the label names.


el,

With more research on stackexchange I see that you're correct.  My
apologies.

[...]

--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error [FIXED]

[Dr Eberhard Lisse]

':' also seem to work in LaTeX.

And, there's not heat here :-)-O

el

On 14/10/2021 09:58, Steve Litt wrote:

Rich Shepard said on Wed, 13 Oct 2021 08:10:57 -0700 (PDT)

[...]

I'm not taking sides in this too-heated argument, but my practice is
to make every variable and filename consist of the characters that in
ASCII would be 32 to 126, and except for underscore I never put
punctuation nor spaces in variable names and filenames.  When somebody
sends me a file whose filename has spaces, I just delete it unless
it's important enough for me to remove all punctuation and replace
spaces with underscores.  Unless I remember to quote every variable in
every shellscript, space or punctuation within filenames cause
malfunction.  Life's too short.

[...]

--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error [FIXED]

[Steve Litt]

Rich Shepard said on Wed, 13 Oct 2021 08:10:57 -0700 (PDT)

>On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:
>
>> But it does make sense not to put Apostrophes into the labels.  
>
>Tell Irish authors that. :-)
>
>Rich

Rich,

I'm not taking sides in this too-heated argument, but my practice is to
make every variable and filename consist of the characters that in
ASCII would be 32 to 126, and except for underscore I never put
punctuation nor spaces in variable names and filenames. When somebody
sends me a file whose filename has spaces, I just delete it unless it's
important enough for me to remove all punctuation and replace spaces
with underscores. Unless I remember to quote every variable in every
shellscript, space or punctuation within filenames cause malfunction.
Life's too short.

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Rich Shepard]

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


BibTeX does not like Apostropes "'" in the label names.


el,

With more research on stackexchange I see that you're correct. My apologies.


The issue is with biblatex, too. But, it's supposed to have been fixed:

"This has been addressed in the recent update to biblatex and Biber (version
3.1 and 2.2 respectively).

"With \DeclareNolabel we can now choose exactly those characters to be
dropped from label creation, the default is \p{P}\p{S}\p{C}. In order to
preserve apostrophes you can use

"\DeclareNolabel{
  \nolabel{\regexp{[\p{S}\p{Z}\p{C}]+}}
}"

I don't know how to find the biblatex and Biber versions.

Placing the DeclareNoLabel in Settings -> Bibliography -> Citation Style ->
Options or in the preamble have no effect.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: compile error not found in document or bibliographic database [RESOLVED]

[Rich Shepard]

On Wed, 13 Oct 2021, Rich Shepard wrote:


I think it's related to a biblatex style, but otherwise I've no idea where
that string is located.


Sure enough. I don't know if it was the citation or bibliography style
variant that caused the error. Regardless, setting both styles to authoryear
(after carefully reading the biblatex.pdf) removed that error when the
compiling the document.

However, I still have the issue of no bibliography in the PDF. The
bibliography is located after the last chapter and before the appendix.
(Removing the empty appendix makes no difference.)

Where should I look for the reason the bibliography isn't in the PDF?

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

compile error not found in document or bibliographic database

[Rich Shepard]

Compiling the document displays an error message box containing this excerpt
from the latex.log:
\tabbedlabeldatewidth=\skip92
! TeX capacity exceeded, sorry [input stack size=5000].
 \UseTextSymbol
  {TS1}
l.2949 \edef\blxarch@style@niedersachsen{Archä
   ologische Kommission für Nie...
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

When I search the document for 'Kommission' it's not found. Same with
searching the bibliographic database.

I think it's related to a biblatex style, but otherwise I've no idea where
that string is located.

The latex.log is attached. Really!!

I would like suggestions for finding where this originates.

TIA,

RichThis is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020 on Slackware 
(SlackBuilds.org)) (preloaded format=pdflatex 2021.2.17)  13 OCT 2021 05:56
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**biological-evaluation.tex
(./biological-evaluation.tex
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-06-03>
(/usr/share/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2020/04/19 v3.30 KOMA-Script document class (report)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2020/04/19 v3.30 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2020/04/19 v3.30 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks15
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2020/04/19 v3.30 KOMA-Script package (loading files)
))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2020/04/19 v3.30 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip47
\scr@dte@tocline@numbox=\box45
)
Package tocbasic Info: babel extension for `toc' omitted
(tocbasic) because of missing \bbl@set@language on input line 137.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 242
4.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2020/04/19 v3.30 KOMA-Script font size class option (11pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2020/04/19 v3.30 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count167
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 418.2pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 47.2316pt
(typearea)  \oddsidemargin  = -12.5192pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 514.20023pt
(typearea)  \topmargin  = 12.2347pt
(typearea)  \headheight = 17.0pt
(typearea)  \headsep= 20.40001pt
(typearea)  \topskip= 11.0pt
(typearea)  \footskip   = 47.6pt
(typearea)  \baselineskip   = 13.6pt
(typearea)  on input line 1738.
)
\c@part=\count168
\c@chapter=\count169
\c@section=\count170
\c@subsection=\count171
\c@subsubsection=\count172
\c@paragraph=\count173
\c@subparagraph=\count174
\scr@dte@chapter@maxnumwidth=\skip53
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\chapter on input line 5588.
\scr@dte@section@maxnumwidth=\skip54
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\section on input line 5598.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\section on input line 5598.
\scr@dte@part@maxnumwidth=\skip55
Class scrreprt Info: using compatibility default `afterindent=true'
(scrreprt)   for `\part on input line 5607.
\scr@dte@subsection@maxnumwidth=\skip56
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsection on input line 5617.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsection on input line 5617.
\scr@dte@subsubsection@maxnumwidth=\skip57
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsubsection on input line 5627.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsubsection on input line 5627.
\scr@dte@paragraph@maxnumwidth=\skip58
Class scrreprt Info: using compatibility default `runin=bysign'
(scrr

Re: Compile error [FIXED]

[Rich Shepard]

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


the author field is not the same as the label field.


Of course not.


Perhaps it is enclosed by curly braces by default. In which case, the
label field should thus also be, by default).


If you look at a bib(la)tex entry it begins with '@{'

That's followed by the label; that line ends with a comma. The closing curly
brace for the entire entry is at the end. In the meantime, the label field
has no closing curly brace so apostrophes, accents, etc. are not explicitly
displayed. Curly braces around the label field itself solve the problem


But it does make sense not to put Apostrophes into the labels.


Tell Irish authors that. :-)

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error [FIXED]

[Dr Eberhard Lisse]

Rich,

the author field is not the same as the label field.

Perhaps it is enclosed by curly braces by default.  In which case, the
label field should thus also be, by default).

But it does make sense not to put Apostrophes into the labels.

greetings, el

On 13/10/2021 15:10, Rich Shepard wrote:

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:

[...]

Actually, neither bibtex nor biblatex object to apostrophes or other
accents and umlauts, etc.  It's how they're entered and I had
completely forgotten how to do it properly until this morning and
recent caffinization.

The solution is to enclose the string in curly braces: {}.

Doing so for @article{{O'Connor2019}, removed that error (and revealed
a totally different complaint I'll deal with).  But, there were no
errors generated with these strings:

author = {Brooks, R.P. and O'Connell, T.J. and Wardrop, D.H. and Jackson, L.E.},
author = {O'Hagan, M.},

and the other seven apostrophes because the entire string in which it
occurs were enclosed in curly braces.

The initial entry name string had an opening curly brace but not a
closing one.

Being bright-eyed and bushy-tailed upon awakening, and having consumed
my first mug of coffee, allowed me to remember this.

Regards,

Rich


--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error [FIXED]

[Rich Shepard]

On Wed, 13 Oct 2021, Dr Eberhard Lisse wrote:


Which part of 'change the label from "O'Connor" to "OConnor"' do you not
understand? Never mind the Minimal Working Example...

BibTeX does not like Apostropes "'" in the label names.


el,

Actually, neither bibtex nor biblatex object to apostrophes or other accents
and umlauts, etc. It's how they're entered and I had completely forgotten
how to do it properly until this morning and recent caffinization.

The solution is to enclose the string in curly braces: {}.

Doing so for @article{{O'Connor2019}, removed that error (and revealed a
totally different complaint I'll deal with). But, there were no errors
generated with these strings:
author = {Brooks, R.P. and O'Connell, T.J. and Wardrop, D.H. and Jackson, L.E.},
author = {O'Hagan, M.},
and the other seven apostrophes because the entire string in which it occurs
were enclosed in curly braces.

The initial entry name string had an opening curly brace but not a closing
one.

Being bright-eyed and bushy-tailed upon awakening, and having consumed my
first mug of coffee, allowed me to remember this.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Dr Eberhard Lisse]

Rich,

Which part of 'change the label from "O'Connor" to "OConnor"' do you not
understand? Never mind the Minimal Working Example...

BibTeX does not like Apostropes "'" in the label names.

el

On 12/10/2021 21:41, Rich Shepard wrote:
[...]


Now I still have biber complaining about the O'Conner article in the .bib
file, That's a warning and doesn't prevent the file from compiling ...
maybe ... but there's still no bibiolgraphy in the complied PDF. That needs
fixing.

[...]


--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Rich Shepard]

On Tue, 12 Oct 2021, Paul A. Rubin wrote:


I would use a command line tool to scan the document source file (.lyx)
for a non-ASCII or non-UTF8 character. If that turned up nothing, I would
scan the  .bib file (if any) and any included text files.


Paul,

Not the .bib file but the .lyx file with the error.

As I recall, you're on Linux. You might try


Since only 1997.

grep -P '[^\x00-\x7f]'  did the job.

Turns out the '>' were in a URL environment. Changed them to '/' and that
resolved the issue.

Now I still have biber complaining about the O'Conner article in the .bib
file, That's a warning and doesn't prevent the file from compiling ...
maybe ... but there's still no bibiolgraphy in the complied PDF. That needs
fixing.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Paul A. Rubin]

On 10/12/21 3:01 PM, Rich Shepard wrote:

On Tue, 12 Oct 2021, Rich Shepard wrote:

The current one is shown in the attached .png. There was no 'complete 
log'

produced when I clicked that button.


Darn! It's on this one.

Rich


Rich,

I would use a command line tool to scan the document source file (.lyx) 
for a non-ASCII or non-UTF8 character. If that turned up nothing, I 
would scan the .bib file (if any) and any included text files.


As I recall, you're on Linux. You might try

grep -axv '.*' 

first. It should find lines that are not in whatever encoding your 
system uses by default (UTF-8 in my case). It can also be done using 
'iconv'. I've had to jump through similar hoops in the past.


Paul



-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Rich Shepard]

On Tue, 12 Oct 2021, Paul A. Rubin wrote:

Make some coffee (regular) and take it intravenously /*immediately*/! There 
is no PNG attached,


Paul,

The document compiled before I added more text to it, then the new encoding
error arose. I was not paying attention when I placed the attachment. See
below.


but rather a LaTeX log (the one you say doesn't exist?) which seems to
show successful compilation other than some missing references.


That was a remnant from before that I hadn't deleted. It's now gone.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Rich Shepard]

On Tue, 12 Oct 2021, Rich Shepard wrote:


The current one is shown in the attached .png. There was no 'complete log'
produced when I clicked that button.


Darn! It's on this one.

Rich-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compile error

[Paul A. Rubin]

On 10/12/21 2:44 PM, Rich Shepard wrote:
Time for a new thread since bibliography styles are no longer an 
issue. No
bibliography in the compiled doc is, but lyx keeps throwing new 
compile-time

errors at me.

The current one is shown in the attached .png. There was no 'complete 
log'

produced when I clicked that button.

The default text encoding on all my hosts is utf8.

There are no close angle brackets '>' in the document (ctrl-s could 
not find

any) so I've no idea where this error originates.

In the .lyx file fontencoding is 'global' which I assume is the 
default on

all my lyx docs. Should that be changed to utf8?

Rich


Rich,

Make some coffee (regular) and take it intravenously /*immediately*/! 
There is no PNG attached, but rather a LaTeX log (the one you say 
doesn't exist?) which seems to show successful compilation other than 
some missing references.


Paul

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Compile error

[Rich Shepard]

Time for a new thread since bibliography styles are no longer an issue. No
bibliography in the compiled doc is, but lyx keeps throwing new compile-time
errors at me.

The current one is shown in the attached .png. There was no 'complete log'
produced when I clicked that button.

The default text encoding on all my hosts is utf8.

There are no close angle brackets '>' in the document (ctrl-s could not find
any) so I've no idea where this error originates.

In the .lyx file fontencoding is 'global' which I assume is the default on
all my lyx docs. Should that be changed to utf8?

RichThis is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020 on Slackware 
(SlackBuilds.org)) (preloaded format=pdflatex 2021.2.17)  12 OCT 2021 06:36
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**biological-evaluation.tex
(./biological-evaluation.tex
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-06-03>
(/usr/share/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2020/04/19 v3.30 KOMA-Script document class (report)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2020/04/19 v3.30 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2020/04/19 v3.30 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks15
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2020/04/19 v3.30 KOMA-Script package (loading files)
))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2020/04/19 v3.30 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip47
\scr@dte@tocline@numbox=\box45
)
Package tocbasic Info: babel extension for `toc' omitted
(tocbasic) because of missing \bbl@set@language on input line 137.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 242
4.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2020/04/19 v3.30 KOMA-Script font size class option (11pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2020/04/19 v3.30 KOMA-Script package (type area)
\ta@bcor=\skip48
\ta@div=\count167
\ta@hblk=\skip49
\ta@vblk=\skip50
\ta@temp=\skip51
\footheight=\skip52
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 418.2pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 47.2316pt
(typearea)  \oddsidemargin  = -12.5192pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 514.20023pt
(typearea)  \topmargin  = 12.2347pt
(typearea)  \headheight = 17.0pt
(typearea)  \headsep= 20.40001pt
(typearea)  \topskip= 11.0pt
(typearea)  \footskip   = 47.6pt
(typearea)  \baselineskip   = 13.6pt
(typearea)  on input line 1738.
)
\c@part=\count168
\c@chapter=\count169
\c@section=\count170
\c@subsection=\count171
\c@subsubsection=\count172
\c@paragraph=\count173
\c@subparagraph=\count174
\scr@dte@chapter@maxnumwidth=\skip53
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\chapter on input line 5588.
\scr@dte@section@maxnumwidth=\skip54
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\section on input line 5598.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\section on input line 5598.
\scr@dte@part@maxnumwidth=\skip55
Class scrreprt Info: using compatibility default `afterindent=true'
(scrreprt)   for `\part on input line 5607.
\scr@dte@subsection@maxnumwidth=\skip56
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsection on input line 5617.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsection on input line 5617.
\scr@dte@subsubsection@maxnumwidth=\skip57
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsubsection on input line 5627.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsubsection on input line 5627.
\scr@dte@paragraph@maxnumwidth=\skip58
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\paragraph on input line 5637.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\paragraph on input

Re: MWE isolation: was Puzzling compile error

[Scott Kostyshak]

On Fri, Dec 29, 2017 at 05:02:20AM +, Steve Litt wrote:
> On Thu, 28 Dec 2017 11:50:27 -0800 (PST)
> Rich Shepard  wrote:
> 
> > On Thu, 28 Dec 2017, Scott Kostyshak wrote:
> > 
> > > Rich, it would be great if you could send MWE for messages like
> > > this. The first step is: remove all text and just put "hello". Does
> > > that compile? If so, then figure out the smallest .lyx file that
> > > can give the same error.  
> > 
> > Scott,
> > 
> >The .lyx file is 8912 lines and the only strings shown in the error
> > message lower window are the years 2004 and 2005. They are nowhere
> > near the highlighted text so I've no idea how to create a MWE that
> > includes an error I cannot find based on what lyx shows me.
> 
> I can answer that. You get the message. Then you delete half the
> document, and see if the error still happens. If it does not, replace
> the half deleted and delete the other half. If it still happens you
> have multiple instances of the root cause.
> 
> Anyway, you keep deleting about 1/2 of the remaining document until you
> can toggle the symptom on or off with one paragraph. Then you start
> doing the same thing with the paragraph until you get the paragraph
> down to a few words. By then the root cause will probably be obvious,
> but if not, send in the pared down document.
> 
> I'm not saying this just for you Rich. Most people could benefit from
> creating an MWE, and I bet in half the cases people would find their
> own solutions before anybody could possibly reply. Besides being the
> best and most considerate way to ask for help, the MWE is a powerful
> troubleshooting tactic.

Well said, Steve! Thank you for writing that up. If you are up to the
task, I think we should give more details regarding what you mentioned
above in the "How to create a minimal example" section in the following:

https://wiki.lyx.org/FAQ/MinimalExample

Scott


signature.asc
Description: PGP signature

MWE isolation: was Puzzling compile error

[Steve Litt]

On Thu, 28 Dec 2017 11:50:27 -0800 (PST)
Rich Shepard  wrote:

> On Thu, 28 Dec 2017, Scott Kostyshak wrote:
> 
> > Rich, it would be great if you could send MWE for messages like
> > this. The first step is: remove all text and just put "hello". Does
> > that compile? If so, then figure out the smallest .lyx file that
> > can give the same error.  
> 
> Scott,
> 
>The .lyx file is 8912 lines and the only strings shown in the error
> message lower window are the years 2004 and 2005. They are nowhere
> near the highlighted text so I've no idea how to create a MWE that
> includes an error I cannot find based on what lyx shows me.

I can answer that. You get the message. Then you delete half the
document, and see if the error still happens. If it does not, replace
the half deleted and delete the other half. If it still happens you
have multiple instances of the root cause.

Anyway, you keep deleting about 1/2 of the remaining document until you
can toggle the symptom on or off with one paragraph. Then you start
doing the same thing with the paragraph until you get the paragraph
down to a few words. By then the root cause will probably be obvious,
but if not, send in the pared down document.

I'm not saying this just for you Rich. Most people could benefit from
creating an MWE, and I bet in half the cases people would find their
own solutions before anybody could possibly reply. Besides being the
best and most considerate way to ask for help, the MWE is a powerful
troubleshooting tactic.
 
SteveT

Steve Litt 
December 2017 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive

Re: Puzzling compile error [UPDATE]

[Rich Shepard]

On Thu, 28 Dec 2017, Paul A. Rubin wrote:


Looks okay to me. I assume that JabRef is storing that in a .bib file
somewhere. If you want to send me the .bib file, the .tex file and the log
file with the warning, I can take a look (most likely not until tomorrow,
though). I promise not to disclose the contents of your document to anyone
other than my neighbor's dog. (He's a Chihuahua, so he has it coming.)


Paul,

  Will send all. It's really FUBAR: tells me none of the citations are
defined (but they're all in the .bbl file), and shows the inputenc error for
latin9 when nothing in the document or .bib file uses that encoding.

  Chihuahua's are OK. Years ago a neighbor had one and my two Brittany
Spaniel's would lie down so they could get nose-to-nose with him.

Rich

Re: Puzzling compile error [UPDATE]

[Paul A. Rubin]

On 12/28/2017 06:04 PM, Rich Shepard wrote:

On Thu, 28 Dec 2017, Paul A. Rubin wrote:

I assume you're using bibtex (as opposed to biber or biblatex) to 
generate references.


Paul,

  Yeah, bibtex. Here's the error message running pdflatex on the .tex 
file:


Package natbib Warning: Citation `Goovaerts1997' on page 58 undefined 
on input line 2411.


and here's the citation in the file:
see, for example \citealp{Goovaerts1997}). These are powerful tools

  Same format as other \citealp in the text.

  The bibtex source in JabRef:

@Book{Goovaerts1997,
  author    = {Goovaerts, P},
  title = {Geostatistics for Natural Resources Evaluation},
  year  = {1997},
  publisher = {Oxford University Press},
  pages = {483},
  keywords  = {statistics, spatial},
  owner = {rshepard},
  timestamp = {2012.11.09},
}

  I'm not seeing what's 'undefined' in the .tex file or bibtex source. I
hope someone can point it out to me.

Rich
Looks okay to me. I assume that JabRef is storing that in a .bib file 
somewhere. If you want to send me the .bib file, the .tex file and the 
log file with the warning, I can take a look (mos likely not until 
tomorrow, though). I promise not to disclose the contents of your 
document to anyone other than my neighbor's dog. (He's a Chihuahua, so 
he has it coming.)


Paul

Re: Puzzling compile error [UPDATE]

[Rich Shepard]

On Thu, 28 Dec 2017, Paul A. Rubin wrote:

I assume you're using bibtex (as opposed to biber or biblatex) to generate 
references.


Paul,

  Yeah, bibtex. Here's the error message running pdflatex on the .tex file:

Package natbib Warning: Citation `Goovaerts1997' on page 58 undefined on input 
line 2411.


and here's the citation in the file:
see, for example \citealp{Goovaerts1997}). These are powerful tools

  Same format as other \citealp in the text.

  The bibtex source in JabRef:

@Book{Goovaerts1997,
  author= {Goovaerts, P},
  title = {Geostatistics for Natural Resources Evaluation},
  year  = {1997},
  publisher = {Oxford University Press},
  pages = {483},
  keywords  = {statistics, spatial},
  owner = {rshepard},
  timestamp = {2012.11.09},
}

  I'm not seeing what's 'undefined' in the .tex file or bibtex source. I
hope someone can point it out to me.

Rich

Re: Puzzling compile error [UPDATE]

[Paul A. Rubin]

On 12/28/2017 04:04 PM, Rich Shepard wrote:

On Thu, 28 Dec 2017, Paul A. Rubin wrote:


If the glitch is in a BibTeX reference, ...


Paul,

  I found the reported warnings, but still get the same compile error 
from

lyx. Here's an update:

  Running pdflatex on the *.tex file was followed by running bibtex on 
the
*.aux file. It showed 4 warnings of a missing journal name. This 
puzzled me
as I know I enter journal names so I looked at the four entries in 
JabRef,

found and corrected the problem: for reasons unknown to me JabRef added a
data entry field called "journaltitle" immediately below the field
"journel." No explanation of the difference between the two; I cannot
imagine there would be any difference. Anyway, those 4 rows had the 
journal

names in the "journaltitle" field, so I moved them to the "journal" field
instead. Now bibtex is happy: no warnings, or errors.

  But, when I run dvips on the .dvi file and look at the postscript 
output
with gv there are no references at the end of the document. Running 
ps2pdf

on the .ps file produces a .pdf file also with no references.

  And trying to compile the .lyx file with pdflatex within lyx shows the
same error as before.

  I'm using the plainnat style with NatBib author-year citation style. 
What

recently broke is still broken.

Rich
I assume you're using bibtex (as opposed to biber or biblatex) to 
generate references. If you export a .tex file and then run the pdflatex 
- bibtex - pdflatex sequence (or whatever sequence you use if you're not 
using pdflatex) in a terminal, do you get any error messages, and do you 
get a legit .aux file? It's been a while since I was bitten by this, but 
it seems to me the usual reason for no references is that bibtex gagged 
on the .bib file. (Runner up is no citations in the text.)


Paul

Re: Puzzling compile error [UPDATE]

[Rich Shepard]

On Thu, 28 Dec 2017, Paul A. Rubin wrote:


If the glitch is in a BibTeX reference, ...


Paul,

  I found the reported warnings, but still get the same compile error from
lyx. Here's an update:

  Running pdflatex on the *.tex file was followed by running bibtex on the
*.aux file. It showed 4 warnings of a missing journal name. This puzzled me
as I know I enter journal names so I looked at the four entries in JabRef,
found and corrected the problem: for reasons unknown to me JabRef added a
data entry field called "journaltitle" immediately below the field
"journel." No explanation of the difference between the two; I cannot
imagine there would be any difference. Anyway, those 4 rows had the journal
names in the "journaltitle" field, so I moved them to the "journal" field
instead. Now bibtex is happy: no warnings, or errors.

  But, when I run dvips on the .dvi file and look at the postscript output
with gv there are no references at the end of the document. Running ps2pdf
on the .ps file produces a .pdf file also with no references.

  And trying to compile the .lyx file with pdflatex within lyx shows the
same error as before.

  I'm using the plainnat style with NatBib author-year citation style. What
recently broke is still broken.

Rich

Re: Puzzling compile error

[Rich Shepard]

On Thu, 28 Dec 2017, Paul A. Rubin wrote:


If you're using BibTeX, the BibTeX file could be the culprit. Sometimes
people copy citations (or parts thereof) from non-text sources (e.g., PDF
files) and paste them into a .bib file. They look benign, but there are
character codes (ligatures come to mind) that prove indigestible to
BibTeX. There could also be a nonprinting character mucking things up.


Paul,

  As I just posted to the list, I think that's the problem. Exporting the
.lyx file to plain .tex and running pdflatex against it shows undefined
citations.

If the glitch is in a BibTeX reference, I would open the .bib file in a plain 
text editor (or a hex editor, if I were feeling geeky) and look for stray 
characters that look out of place. If the glitch is in the document text, I 
would open the .lyx file in a text editor and snoop for stray characters in 
the vicinity of the glitch.


  I don't have a .bib file, but the latex error suggested looking in the
.aux file.

  My after-lunch work has been planned for me.

Thanks,

Rich

Re: Puzzling compile error

[Rich Shepard]

On Thu, 28 Dec 2017, Scott Kostyshak wrote:


Rich, it would be great if you could send MWE for messages like this. The
first step is: remove all text and just put "hello". Does that compile? If
so, then figure out the smallest .lyx file that can give the same error.


Scott,

  I think that I found the problem. Exporting the file to plain TeX and
running pdflatex on it shows undefined references. I'll look to see that all
citations are in the bibtex file.

Rich

Re: Puzzling compile error

[Paul A. Rubin]

On 12/28/2017 02:50 PM, Rich Shepard wrote:

On Thu, 28 Dec 2017, Scott Kostyshak wrote:

Rich, it would be great if you could send MWE for messages like this. 
The
first step is: remove all text and just put "hello". Does that 
compile? If

so, then figure out the smallest .lyx file that can give the same error.


Scott,

  The .lyx file is 8912 lines and the only strings shown in the error
message lower window are the years 2004 and 2005. They are nowhere 
near the
highlighted text so I've no idea how to create a MWE that includes an 
error

I cannot find based on what lyx shows me.

  The 2004 is associated with a citation and bibliographic entry; the 
2005

is in the body of the document. There is no 'california' with a lowercase
initial 'c', nor the word 'bypass' anywhere.

  What would be an appropriate diagnostic to refine the source of this
error?

Thanks,

Rich

Rich,

If you're using BibTeX, the BibTeX file could be the culprit. Sometimes 
people copy citations (or parts thereof) from non-text sources (e.g., 
PDF files) and paste them into a .bib file. They look benign, but there 
are character codes (ligatures come to mind) that prove indigestible to 
BibTeX. There could also be a nonprinting character mucking things up.


If the glitch is in a BibTeX reference, I would open the .bib file in a 
plain text editor (or a hex editor, if I were feeling geeky) and look 
for stray characters that look out of place. If the glitch is in the 
document text, I would open the .lyx file in a text editor and snoop for 
stray characters in the vicinity of the glitch.


Paul

Re: Puzzling compile error

[Rich Shepard]

On Thu, 28 Dec 2017, Scott Kostyshak wrote:


Rich, it would be great if you could send MWE for messages like this. The
first step is: remove all text and just put "hello". Does that compile? If
so, then figure out the smallest .lyx file that can give the same error.


Scott,

  The .lyx file is 8912 lines and the only strings shown in the error
message lower window are the years 2004 and 2005. They are nowhere near the
highlighted text so I've no idea how to create a MWE that includes an error
I cannot find based on what lyx shows me.

  The 2004 is associated with a citation and bibliographic entry; the 2005
is in the body of the document. There is no 'california' with a lowercase
initial 'c', nor the word 'bypass' anywhere.

  What would be an appropriate diagnostic to refine the source of this
error?

Thanks,

Rich

Re: Puzzling compile error

[Scott Kostyshak]

On Thu, Dec 28, 2017 at 07:22:19PM +, Rich Shepard wrote:

> I've no idea where to look for the source of
> this error and would appreciate a pointer or two.

Rich, it would be great if you could send MWE for messages like this.
The first step is: remove all text and just put "hello". Does that
compile? If so, then figure out the smallest .lyx file that can give the
same error.

Scott


signature.asc
Description: PGP signature

Puzzling compile error

[Rich Shepard]

  I've added text to the book and now it chokes at compiling. The reported
problem is with this text: "variables) to describe their objectives and
actions needed to achieve them." and the error window is shown in the
attached screenshot.

  There were no problems compiling the document before and a search of the
terms shown in the error window (bypass, california, 2004, 2005) do not show
up in a search of the text. I've no idea where to look for the source of
this error and would appreciate a pointer or two.

Rich

Re: Strange compile error

[Steve Hnizdur]

On 03/09/17 21:20, Paul A. Rubin wrote:

On 09/03/2017 04:10 PM, Steve Hnizdur wrote:

Hi

Thanks for replying. Ctrl-R  does pdflatex. Attached is the tex file 
produced by exporting from lyx, and I get the same error by running 
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto 
date.


By the way the error still happens if the superscripts are removed, it 
seems to be the \dots that are causing the problem.


Cheers
To facilitate others following the thread, it's preferred that we 
bottom-post.


I just ran pdflatex against your TeX, and again it compiled for me with 
no errors. I'm running Linux Mint 18.2 (based on Ubuntu 16.04), with LyX 
2.2.3 and TeXLive 2017. I've attached the pdflatex log file; maybe you 
can look for differences with yours and find out where yours deviates. 
It seems to be something on your system, not a LyX error.


Paul


I can confirm there is a problem with amsmath 2.15a. I have now updated 
to 2.16a and all is fine. Many thanks for comments and help.


--

Steve Hnizdur

Re: Strange compile error

[Guenter Milde]

On 2017-09-03, Steve Hnizdur wrote:

> Attached is a lyx file which when complied with ctrl-R gives the error 
> below copied from the error log. It also fails if I try to compile it as 
> a native .tex file.

I tried the example you posted later and it runs without problems here
(Debian/stable with pre-packaged TeXLive 2016).

> The error goes away if the \dots is removed and it also goes away if the 
> "Number Equations by Section" Module is removed.

> Any thoughts.

I know that amsmath re-defines \dots to be context sensitive. It may be
that \numberwithin{equation}{section} interferes with this re-definition in
some way (in the version used by you) and the bug is solved in current
versions.

You may try to use \ldots instead of \dots or to update your TeX installation.

Günter

Re: Strange compile error

[Paul A. Rubin]

On 09/03/2017 04:10 PM, Steve Hnizdur wrote:

Hi

Thanks for replying. Ctrl-R  does pdflatex. Attached is the tex file 
produced by exporting from lyx, and I get the same error by running 
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto 
date.


By the way the error still happens if the superscripts are removed, it 
seems to be the \dots that are causing the problem.


Cheers
To facilitate others following the thread, it's preferred that we 
bottom-post.


I just ran pdflatex against your TeX, and again it compiled for me with 
no errors. I'm running Linux Mint 18.2 (based on Ubuntu 16.04), with LyX 
2.2.3 and TeXLive 2017. I've attached the pdflatex log file; maybe you 
can look for differences with yours and find out where yours deviates. 
It seems to be something on your system, not a LyX error.


Paul

This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdflatex 2017.8.2)  3 SEP 2017 16:14
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**test_error.tex
(./test_error.tex
LaTeX2e <2017-04-15>
Babel <3.12> and hyphenation patterns for 3 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2017/04/05 v2.0i Standard LaTeX package

(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2017/04/05 v2.0i Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 48.
))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2015/03/17 v1.2c Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15

(/usr/share/texlive/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2015/03/17 v1.2c Input encoding file
))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
Package: amsmath 2016/11/05 v2.16a AMS math features
\@mathmargin=\skip43

For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
Package: amstext 2000/06/29 v2.01 AMS text

(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty
File: amsgen.sty 1999/11/30 v2.0 generic functions
\@emptytoks=\toks16
\ex@=\dimen103
))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty
Package: amsbsy 1999/11/29 v1.2d Bold Symbols
\pmbraise@=\dimen104
)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty
Package: amsopn 2016/03/08 v2.02 operator names
)
\inf@bad=\count87
LaTeX Info: Redefining \frac on input line 213.
\uproot@=\count88
\leftroot@=\count89
LaTeX Info: Redefining \overline on input line 375.
\classnum@=\count90
\DOTSCASE@=\count91
LaTeX Info: Redefining \ldots on input line 472.
LaTeX Info: Redefining \dots on input line 475.
LaTeX Info: Redefining \cdots on input line 596.
\Mathstrutbox@=\box26
\strutbox@=\box27
\big@size=\dimen105
LaTeX Font Info:Redeclaring font encoding OML on input line 712.
LaTeX Font Info:Redeclaring font encoding OMS on input line 713.
\macc@depth=\count92
\c@MaxMatrixCols=\count93
\dotsspace@=\muskip10
\c@parentequation=\count94
\dspbrk@lvl=\count95
\tag@help=\toks17
\row@=\count96
\column@=\count97
\maxfields@=\count98
\andhelp@=\toks18
\eqnshift@=\dimen106
\alignsep@=\dimen107
\tagshift@=\dimen108
\tagwidth@=\dimen109
\totwidth@=\dimen110
\lineht@=\dimen111
\@envbody=\toks19
\multlinegap=\skip44
\multlinetaggap=\skip45
\mathdisplay@stack=\toks20
LaTeX Info: Redefining \[ on input line 2817.
LaTeX Info: Redefining \] on input line 2818.
)
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
Package: babel 2017/06/29 3.12 The Babel package

(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def
File: switch.def 2017/06/29 3.12 Babel switching mechanism
)
(/usr/share/texlive/texmf-dist/tex/generic/babel-english/british.ldf
Language: british 2017/06/06 v3.3r English support from the babel system

(/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
Language: english 2017/06/06 v3.3r English support from the babel system

(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
File: babel.def 2017/06/29 3.12 Babel common definitions

(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def
File: switch.def 2017/06/29 3.12 Babel switching mechanism
)
\babel@savecnt=\count99
\U@D=\dimen112
)
\l@british = a dialect from \language\l@english 
\l@UKenglish = a dialect from \language\l@english 
\l@canadian = a dialect from \language\l@american 
\l@australian = a dialect from \language\l@british 
\l@newzealand = a 

Re: Strange compile error

[Steve Hnizdur]

Hi

Thanks for replying. Ctrl-R  does pdflatex. Attached is the tex file 
produced by exporting from lyx, and I get the same error by running 
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto date.


By the way the error still happens if the superscripts are removed, it 
seems to be the \dots that are causing the problem.


Cheers

On 03/09/17 21:00, Paul A. Rubin wrote:

On 09/03/2017 01:06 PM, Steve Hnizdur wrote:

Hi

Attached is a lyx file which when complied with ctrl-R gives the error 
below copied from the error log. It also fails if I try to compile it 
as a native .tex file.


The error goes away if the \dots is removed and it also goes away if 
the "Number Equations by Section" Module is removed.


Any thoughts.
What format does ctrl-R use in your configuration? In mine, it's 
pdflatex, and the document compiles just fine.


Paul



--

Steve Hnizdur
%% LyX 2.2.3 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[british]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{amsmath}

\makeatletter
%% Textclass specific LaTeX commands.
\numberwithin{equation}{section}

\makeatother

\usepackage{babel}
\begin{document}
aaa
\[
\left\Vert P_{1}\right\Vert ^{m_{1}}\dots\left\Vert P_{r}\right\Vert ^{m_{r}}
\]

xxx
\end{document}

Re: Strange compile error

[Paul A. Rubin]

On 09/03/2017 01:06 PM, Steve Hnizdur wrote:

Hi

Attached is a lyx file which when complied with ctrl-R gives the error 
below copied from the error log. It also fails if I try to compile it 
as a native .tex file.


The error goes away if the \dots is removed and it also goes away if 
the "Number Equations by Section" Module is removed.


Any thoughts.
What format does ctrl-R use in your configuration? In mine, it's 
pdflatex, and the document compiles just fine.


Paul

Strange compile error

[Steve Hnizdur]

Hi

Attached is a lyx file which when complied with ctrl-R gives the error 
below copied from the error log. It also fails if I try to compile it as 
a native .tex file.


The error goes away if the \dots is removed and it also goes away if the 
"Number Equations by Section" Module is removed.


Any thoughts.


Error
**

! Argument of \zap@to@space has an extra }.

\par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've 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.

Runaway argument?
\left..
! Paragraph ended before \zap@to@space was complete.

   \par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.

Runaway argument?
! Paragraph ended before \macro@ was complete.

   \par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.

! Missing $ inserted.

$
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I've inserted a begin-math/end-math symbol since I think
you left one out. Proceed, with fingers crossed.

! Display math should end with $$.

   \par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

The `$' that I just saw supposedly matches a previous `$$'.
So I shall assume that you typed `$$' both times.

Runaway argument?
\meaning@ \not@ \ifgtest@ \gdef \thedots@ {\dotsb@ }\else \@xp \DOTS@ \ETC.
! Paragraph ended before \macro@ was complete.

   \par
l.22

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.


! LaTeX Error: \begin{equation*} on input line 19 ended by \end{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.24 \end{document}

Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

[1

{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./test_error.aux) )
(\end occurred inside a group at level 1)

### semi simple group (level 1) entered at line 19 (\begingroup)
### bottom level
(\end occurred when \iffalse on line 20 was incomplete)
(\end occurred when \iffalse on line 20 was incomplete)
(\end occurred when \iffalse on line 20 was incomplete)
(\end occurred when \ifx on line 20 was incomplete)
(\end occurred when \ifx on line 20 was incomplete)
(\end occurred when \ifx on line 20 was incomplete)
Here is how much of TeX's memory you used:

--

Steve Hnizdur


test_error.lyx
Description: application/lyx

Re: Compile error File does not exist: /var/folders

[Graham Smith]

> Yes, this sounds like a problem specific to a particular file (then it
> will be even harder for me to diagnose). Does that one produce figures
> from R?
>

Yes, it produces figures as well.

Graham

Re: Compile error File does not exist: /var/folders

[Jean-Marc Lasgouttes]

Le 09/02/2012 04:59, Yihui Xie a écrit :

21:59:54.748: Warning message:


 21:59:54.748: In readLines(f[1L], warn = FALSE) :

 21:59:54.748: invalid input found on input connection
 
'/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.Rnw'


Could you show what is in the .Rnw file? Do you use special encodings?
It is strange that the file cannot even be read by readLines.

JMarc

Re: Compile error File does not exist: /var/folders

[Yihui Xie]

Yes, this sounds like a problem specific to a particular file (then it
will be even harder for me to diagnose). Does that one produce figures
from R?

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Thu, Feb 9, 2012 at 12:38 AM, Graham Smith  wrote:
>
> I have just a different file from a different project, but still one using
> Sweave, and that compliled fine so it seems something unique to this file,
> so maybe that is where I should be looking.
>
> Graham
>

Re: Compile error File does not exist: /var/folders

[Graham Smith]

I have just a different file from a different project, but still one using
Sweave, and that compliled fine so it seems something unique to this file,
so maybe that is where I should be looking.

Graham

Re: Compile error File does not exist: /var/folders

[Graham Smith]

Can you also attach a copy of the script
> /Applications/LyX.app/Contents/Resources/scripts/lyxsweave.R ?
>

File atached

Thanks,

Graham


lyxsweave.R
Description: Binary data

Re: Compile error File does not exist: /var/folders

[Yihui Xie]

Can you also attach a copy of the script
/Applications/LyX.app/Contents/Resources/scripts/lyxsweave.R ?

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Wed, Feb 8, 2012 at 4:06 PM, Graham Smith  wrote:
> Yihui
>
>
>> This is confusing to me. Ideally Sweave should write that file in the
>> temp folder, and R will clean up the temp dir string in the tex
>> output. However, in your case, both tasks failed. Have you set up any
>> Sweave options like prefix and prefix.string in your document? Or have
>> you ever changed the Sweave module in LyX? What are the first few
>> lines of messages when you compile the document? (View-->View
>> Messages)
>
>
> Not as confusing as it is to me :-(
>
> It's identical to the file that compiled in October, I opened the Lyx file
> and tried to compile it and couldn't because I got this error, then opened
> it in Lyx/Ubuntu and it compiled fine.
>
> I have pasted the lines from View-->Messages errors come half way through,
> so I thought this would be more informative than just the firet few lines
>
> 21:59:54.210: Previewing ...
>
> 21:59:54.218: (buffer-view: ⌘R)
>
> 21:59:54.299: Rscript --verbose --no-save --no-restore
> "/Applications/LyX.app/Contents/Resources/scripts/lyxsweave.R"
> "/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/""R-GettingStarted.Rnw"
> "/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/""R-GettingStarted.tex"
> UTF-8 "/Users/graham/Dropbox/projects/R-Intro_Oct2011/"
>
> 21:59:54.302: running
>
> 21:59:54.302: '/Library/Frameworks/R.framework/Versions/2.14/Resources/bin/R
> --slave --no-restore --no-save --no-restore
> --file=/Applications/LyX.app/Contents/Resources/scripts/lyxsweave.R --args
> /var/folders/g3
>
> 21:59:54.302:
> /h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.Rnw
> /var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.tex
> UTF-8'
>
> 21:59:54.302:
>
> 21:59:54.609: Writing to file
> /var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.tex
>
> 21:59:54.611: Processing code chunks with options ...
>
> 21:59:54.627: 1 : keep.source term verbatim
>
> 21:59:54.646: 2 : echo keep.source
>
> 21:59:54.648: 3 : echo keep.source term verbatim
>
> 21:59:54.662: 4 : echo keep.source
>
> 21:59:54.664: 5 : echo keep.source
>
> 21:59:54.666: 6 : echo keep.source term verbatim
>
> 21:59:54.671: 7 : echo keep.source
>
> 21:59:54.674: 8 : echo keep.source term verbatim
>
> 21:59:54.686: 9 : echo keep.source
>
> 21:59:54.687: 10 : echo keep.source
>
> 21:59:54.689: 11 : echo keep.source
>
> 21:59:54.692: 12 : echo keep.source term verbatim pdf
>
> 21:59:54.748:
>
> 21:59:54.748: You can now run (pdf)latex on
> '/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.tex'
>
> 21:59:54.748: Warning message:
>
> 21:59:54.748: In readLines(f[1L], warn = FALSE) :
>
> 21:59:54.748: invalid input found on input connection
> '/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.Rnw'
>
> 21:59:54.778: pdflatex "R-GettingStarted.tex"
>
> 21:59:54.932: This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
>
> 21:59:54.934: restricted \write18 enabled.
>
> 21:59:54.940: entering extended mode
>
> 21:59:54.940: (./R-GettingStarted.tex
>
> 21:59:54.940: LaTeX2e <2011/06/27>
>
> 21:59:54.940: Babel  and hyphenation patterns for english, dumylang,
> nohyphenation, ge
>
> 21:59:54.940: rman-x-2011-07-01, ngerman-x-2011-07-01, afrikaans,
> ancientgreek, ibycus, arabi
>
> 21:59:54.941: c, armenian, basque, bulgarian, catalan, pinyin, coptic,
> croatian, czech, danis
>
> 21:59:54.941: h, dutch, ukenglish, usenglishmax, esperanto, estonian,
> ethiopic, farsi, finnis
>
> 21:59:54.941: h, french, galician, german, ngerman, swissgerman, monogreek,
> greek, hungarian,
>
> 21:59:54.941: icelandic, assamese, bengali, gujarati, hindi, kannada,
> malayalam, marathi, or
>
> 21:59:54.941: iya, panjabi, tamil, telugu, indonesian, interlingua, irish,
> italian, kurmanji,
>
> 21:59:54.941: lao, latin, latvian, lithuanian, mongolian, mongolianlmc,
> bokmal, nynorsk, pol
>
> 21:59:54.941: ish, portuguese, romanian, russian, sanskrit, serbian,
> serbianc, slovak, sloven
>
> 21:59:54.941: ian, spanish, swedish, turkish, turkmen, ukrainian,
> uppersorbian, welsh, loaded
>
> 21:59:54.941: .
>
> 21:59:54.941:
>
> 21:59:55.396: pdflatex
> "R-GettingStarted.tex"/Users/Shared/LyX/lyx-2.0.2/src/support/Systemcall.cpp(243):
> Systemcall: 'pdflatex "R-GettingStarted.tex"' finished with exit code 1
>
> 21:59:55.550: This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
>
> 21:59:55.550: restricted \write18 enabled.
>
> 21:59:55.558: entering extended mode
>
> 21:59:55.559: (./R-GettingStarted.tex
>
> 21:59:55.559: LaTeX2e

Re: Compile error File does not exist: /var/folders

[Graham Smith]

Just realised I didn't answer

>Have you set up any Sweave options like prefix and prefix.string in your
document? Or have you ever changed the >Sweave module in LyX?

No I haven't doen either of these things, except when I added the TEX box
you suggsted, which Inave since removed.

Graham

Re: Compile error File does not exist: /var/folders

[Graham Smith]

Yihui


This is confusing to me. Ideally Sweave should write that file in the
> temp folder, and R will clean up the temp dir string in the tex
> output. However, in your case, both tasks failed. Have you set up any
> Sweave options like prefix and prefix.string in your document? Or have
> you ever changed the Sweave module in LyX? What are the first few
> lines of messages when you compile the document? (View-->View
> Messages)
>

Not as confusing as it is to me :-(

It's identical to the file that compiled in October, I opened the Lyx file
and tried to compile it and couldn't because I got this error, then opened
it in Lyx/Ubuntu and it compiled fine.

I have pasted the lines from View-->Messages errors come half way through,
so I thought this would be more informative than just the firet few lines

 21:59:54.210: Previewing ...

21:59:54.218: (buffer-view: ⌘R)

21:59:54.299: Rscript --verbose --no-save --no-restore
"/Applications/LyX.app/Contents/Resources/scripts/lyxsweave.R"
"/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/""R-GettingStarted.Rnw"
"/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/""R-GettingStarted.tex"
UTF-8 "/Users/graham/Dropbox/projects/R-Intro_Oct2011/"

21:59:54.302: running

21:59:54.302:
'/Library/Frameworks/R.framework/Versions/2.14/Resources/bin/R --slave
--no-restore --no-save --no-restore
--file=/Applications/LyX.app/Contents/Resources/scripts/lyxsweave.R --args
/var/folders/g3

21:59:54.302:
/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.Rnw
/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.tex
UTF-8'

21:59:54.302:

21:59:54.609: Writing to file
/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.tex

21:59:54.611: Processing code chunks with options ...

21:59:54.627: 1 : keep.source term verbatim

21:59:54.646: 2 : echo keep.source

21:59:54.648: 3 : echo keep.source term verbatim

21:59:54.662: 4 : echo keep.source

21:59:54.664: 5 : echo keep.source

21:59:54.666: 6 : echo keep.source term verbatim

21:59:54.671: 7 : echo keep.source

21:59:54.674: 8 : echo keep.source term verbatim

21:59:54.686: 9 : echo keep.source

21:59:54.687: 10 : echo keep.source

21:59:54.689: 11 : echo keep.source

21:59:54.692: 12 : echo keep.source term verbatim pdf

21:59:54.748:

21:59:54.748: You can now run (pdf)latex on
'/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.tex'

21:59:54.748: Warning message:

21:59:54.748: In readLines(f[1L], warn = FALSE) :

21:59:54.748: invalid input found on input connection
'/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.JL3034/lyx_tmpbuf2/R-GettingStarted.Rnw'

21:59:54.778: pdflatex "R-GettingStarted.tex"

21:59:54.932: This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)

21:59:54.934: restricted \write18 enabled.

21:59:54.940: entering extended mode

21:59:54.940: (./R-GettingStarted.tex

21:59:54.940: LaTeX2e <2011/06/27>

21:59:54.940: Babel  and hyphenation patterns for english, dumylang,
nohyphenation, ge

21:59:54.940: rman-x-2011-07-01, ngerman-x-2011-07-01, afrikaans,
ancientgreek, ibycus, arabi

21:59:54.941: c, armenian, basque, bulgarian, catalan, pinyin, coptic,
croatian, czech, danis

21:59:54.941: h, dutch, ukenglish, usenglishmax, esperanto, estonian,
ethiopic, farsi, finnis

21:59:54.941: h, french, galician, german, ngerman, swissgerman, monogreek,
greek, hungarian,

21:59:54.941: icelandic, assamese, bengali, gujarati, hindi, kannada,
malayalam, marathi, or

21:59:54.941: iya, panjabi, tamil, telugu, indonesian, interlingua, irish,
italian, kurmanji,

21:59:54.941: lao, latin, latvian, lithuanian, mongolian, mongolianlmc,
bokmal, nynorsk, pol

21:59:54.941: ish, portuguese, romanian, russian, sanskrit, serbian,
serbianc, slovak, sloven

21:59:54.941: ian, spanish, swedish, turkish, turkmen, ukrainian,
uppersorbian, welsh, loaded

21:59:54.941: .

21:59:54.941:

21:59:55.396: pdflatex
"R-GettingStarted.tex"/Users/Shared/LyX/lyx-2.0.2/src/support/Systemcall.cpp(243):
Systemcall: 'pdflatex "R-GettingStarted.tex"' finished with exit code 1

21:59:55.550: This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)

21:59:55.550: restricted \write18 enabled.

21:59:55.558: entering extended mode

21:59:55.559: (./R-GettingStarted.tex

21:59:55.559: LaTeX2e <2011/06/27>

21:59:55.559: Babel  and hyphenation patterns for english, dumylang,
nohyphenation, ge

21:59:55.559: rman-x-2011-07-01, ngerman-x-2011-07-01, afrikaans,
ancientgreek, ibycus, arabi

21:59:55.559: c, armenian, basque, bulgarian, catalan, pinyin, coptic,
croatian, czech, danis

21:59:55.559: h, dutch, ukenglish, usenglishmax, esperanto, estonian,
ethiopic, farsi, finnis

21:59:55.559: h, french, galician, german, ngerman, swissgerman, monogreek,
greek, hungarian,

21:59:55.560: icelandic, assamese, bengali, gujarati, 

Re: Compile error File does not exist: /var/folders

[Yihui Xie]

This is confusing to me. Ideally Sweave should write that file in the
temp folder, and R will clean up the temp dir string in the tex
output. However, in your case, both tasks failed. Have you set up any
Sweave options like prefix and prefix.string in your document? Or have
you ever changed the Sweave module in LyX? What are the first few
lines of messages when you compile the document? (View-->View
Messages)

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Wed, Feb 8, 2012 at 3:02 PM, Graham Smith  wrote:
> OK,
>
> The file doesn't seem to exist. A search only finds the PDF from October in
>
> \Users\graham\Dropbox\projects\R-Intro_Oct2011\R-GettingStarted.pdf
>
> The temp folder has all the tex files etc but no PDF.
>
> Graham
>

Re: Compile error File does not exist: /var/folders

[Graham Smith]

OK,

The file doesn't seem to exist. A search only finds the PDF from October in

\Users\graham\Dropbox\projects\R-Intro_Oct2011\R-GettingStarted.pdf

The temp folder has all the tex files etc but no PDF.

Graham

On 8 February 2012 20:50, Yihui Xie  wrote:

> OK, then the question is where is this file. Can you try to compile
> the document again, and search for that R-GettingStarted.pdf?
>
> Regards,
> Yihui
> --
> Yihui Xie 
> Phone: 515-294-2465 Web: http://yihui.name
> Department of Statistics, Iowa State University
> 2215 Snedecor Hall, Ames, IA
>
>
>
> On Wed, Feb 8, 2012 at 2:44 PM, Graham Smith  wrote:
> > Yihui
> >
> >> This sounds hard to diagnose... Does that file really exist or not?
> >> Can you go and check in that folder?
> >
> >
> > The folder exists, but there is no R-GettingStarted.pdf in the folder.
> The
> > folder is empty.
> >
> > Graham
> >
> >
> >
>

Re: Compile error File does not exist: /var/folders

[Yihui Xie]

OK, then the question is where is this file. Can you try to compile
the document again, and search for that R-GettingStarted.pdf?

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Wed, Feb 8, 2012 at 2:44 PM, Graham Smith  wrote:
> Yihui
>
>> This sounds hard to diagnose... Does that file really exist or not?
>> Can you go and check in that folder?
>
>
> The folder exists, but there is no R-GettingStarted.pdf in the folder. The
> folder is empty.
>
> Graham
>
>
>

Re: Compile error File does not exist: /var/folders

[Graham Smith]

Yihui

This sounds hard to diagnose... Does that file really exist or not?
> Can you go and check in that folder?
>

The folder exists, but there is no R-GettingStarted.pdf in the folder. The
folder is empty.

Graham

Re: Compile error File does not exist: /var/folders

[Yihui Xie]

This sounds hard to diagnose... Does that file really exist or not?
Can you go and check in that folder?

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Wed, Feb 8, 2012 at 2:20 PM, Graham Smith  wrote:
> Yihui
>
> Thanks for the response
>
>
>> Which version of R are you using? Does it work when you add this to
>> your document as TeX code (Insert-->TeX Code)?
>>
>> \SweaveOpts{prefix=TRUE,prefix.string=sweave-figure}
>
> It's R 2.14.1, and adding the code doesn't make any difference.
>
> Graham
>

Re: Compile error File does not exist: /var/folders

[Graham Smith]

Yihui

Thanks for the response

> Which version of R are you using? Does it work when you add this to
> your document as TeX code (Insert-->TeX Code)?
>
> \SweaveOpts{prefix=TRUE,prefix.string=sweave-figure}

It's R 2.14.1, and adding the code doesn't make any difference.

Graham

Re: Compile error File does not exist: /var/folders

[Yihui Xie]

Which version of R are you using? Does it work when you add this to
your document as TeX code (Insert-->TeX Code)?

\SweaveOpts{prefix=TRUE,prefix.string=sweave-figure}

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA



On Wed, Feb 8, 2012 at 4:11 AM, Graham Smith  wrote:
> I have just tried compile a file that I last compiled in October 2011, on
> Mac with Lion and Lyx 2.02, but may have originally been compiled on a  Mac
> with Snow leopard and Lyx 2.01.
>
> I am getting the error
>
> File does not exist:
> /var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.xJL756/lyx_tmpbuf0/R-GettingStarted.pdf
>
>
> The file points to some screen grabs and has R code so it also uses Sweave.
>
>
> I have just tried and the same file compiles fine on Ubnutu 11.10/lyx 2.0.0
> (Ubuntu is running virtual box on the Mac so is pointing at the same file in
> the same directory as the Mac copy of Lyx is pointing at). So I can carry
> on, but I coud do with sorting out the problem with the Mac version of Lyx.
>
>
> I see the same question was asked in December, but it didn't reach a
> conclusion.
>
>
> Many thanks,
>
>
> Graham
>
>

Compile error File does not exist: /var/folders

[Graham Smith]

I have just tried compile a file that I last compiled in October 2011, on
Mac with Lion and Lyx 2.02, but may have originally been compiled on a  Mac
with Snow leopard and Lyx 2.01.

I am getting the error

 File does not exist:
/var/folders/g3/h89z1g_n7yv3fth6y2yd2nlhgn/T/lyx_tmpdir.xJL756/lyx_tmpbuf0/R-GettingStarted.pdf


The file points to some screen grabs and has R code so it also uses Sweave.


I have just tried and the same file compiles fine on Ubnutu 11.10/lyx 2.0.0
(Ubuntu is running virtual box on the Mac so is pointing at the same file
in the same directory as the Mac copy of Lyx is pointing at). So I can
carry on, but I coud do with sorting out the problem with the Mac version
of Lyx.


I see the same question was asked in December, but it didn't reach a
conclusion.


Many thanks,


Graham

Re: Compile error: "The directory path to the document cannot contain spaces"

[David]

It would be too much of a hassle to change that because it's my default 
document directory, and there are some dependency problems as well which I 
don't think it's a good idea to alter it.

When I installed MikTeX 2.9 I didn't remove MikTeX 2.8. The compiler works fine 
if I re-configure LyX to use the MikTeX 2.8 installation. Compiling speed was 
very slow though (this happened after I installed some packages for 2.8 which 
seemed to be causing such slowness although I couldn't figure out why - this is 
the reason why I installed MikTeX 2.9).

Another point is that my office computer also uses LyX on a MikTeX 2.9 
installation (also runs on Windows XP). The directory also contains spaces, but 
I can compile normally on that machine. Now I don't know which part is actually 
the culprit, because it seems that the compiler is designed to deal with spaces 
but somehow that does not work on my computer.


--- 2011年12月5日 星期一，Richard Heck  寫道﹕

寄件人: Richard Heck 
主題: Re: Compile error: "The directory path to the document cannot contain 
spaces"
收件人: "David" 
副本(CC): lyx-users@lists.lyx.org
日期: 2011年12月5日,星期一,上午1:53



  


  
  
On 12/04/2011 07:55 AM, David wrote:

  

  
Dear all,

  

  I have been using MikTeX 2.8 and has recently upgraded to
  MikTeX 2.9. To ensure my LyX (2.0) runs smoothly I
  uninstalled that and reinstalled the latest version
  (2.0.2), pointing it to my latest MikTex installation.
  However, when I use it to compile my document (Ctrl+R) a
  message box appears immediately saying that "The directory
  path to the document cannot contain spaces", an error that
  I have never encountered before. Yes I know my directory
  contains spaces but it worked fine before I did all these
  changes. Moving my file somewhere else works, but
  certainly it will be too troublesome to do that every
  time. Furthermore my directory is something like "D:\My
  Documents\blahblahblah" and I clearly cannot change "My
  Documents" to something else.

  


  

  

Actually, you can change it. I don't have Windows machines in my
house any more, but I used to do it routinely on my wife's machine.




  

  
Is there an
  alternative method that can bypass this problem?

  


  

  

It would seem that the configuration script has for some reason
decided MikTeX won't allow spaces. You might try reconfiguring, but
then again, if the configure script failed this test, then there may
be an issue.



Windows people may be able to give more advice.



Richard



  

Re: Compile error: "The directory path to the document cannot contain spaces"

[Richard Heck]

On 12/04/2011 07:55 AM, David wrote:
> Dear all,
>
> I have been using MikTeX 2.8 and has recently upgraded to MikTeX 2.9.
> To ensure my LyX (2.0) runs smoothly I uninstalled that and
> reinstalled the latest version (2.0.2), pointing it to my latest
> MikTex installation. However, when I use it to compile my document
> (Ctrl+R) a message box appears immediately saying that "The directory
> path to the document cannot contain spaces", an error that I have
> never encountered before. Yes I know my directory contains spaces but
> it worked fine before I did all these changes. Moving my file
> somewhere else works, but certainly it will be too troublesome to do
> that every time. Furthermore my directory is something like "D:\My
> Documents\blahblahblah" and I clearly cannot change "My Documents" to
> something else.
>
Actually, you can change it. I don't have Windows machines in my house
any more, but I used to do it routinely on my wife's machine.

> Is there an alternative method that can bypass this problem?
>
It would seem that the configuration script has for some reason decided
MikTeX won't allow spaces. You might try reconfiguring, but then again,
if the configure script failed this test, then there may be an issue.

Windows people may be able to give more advice.

Richard

Compile error: "The directory path to the document cannot contain spaces"

[David]

Dear all,

I have been using MikTeX 2.8 and has recently upgraded to MikTeX 2.9. To
 ensure my LyX (2.0) runs smoothly I uninstalled that and reinstalled 
the latest version (2.0.2), pointing it to my latest MikTex 
installation. However, when I use it to compile my document (Ctrl+R) a 
message box appears immediately saying that "The directory path to the 
document cannot contain spaces", an error that I have never encountered 
before. Yes I know my directory contains spaces but it worked fine 
before I did all these changes. Moving my file somewhere else works, but
 certainly it will be too troublesome to do that every time. Furthermore
 my directory is something like "D:\My Documents\blahblahblah" and I 
clearly cannot change "My Documents" to something else.

Is there an alternative method that can bypass this problem?

Thanks,
David

Adding section to appendix causes a compile error

[Thangalin]

Hi,

I ran into a situation that boggles my mind. I have posted the details on
the TeX StackExchange website:

http://tex.stackexchange.com/questions/6721/adding-section-to-appendix-causes-a-compile-error

Any ideas or suggestions on how to resolve the error would be greatly
appreciated.

Thank you!

Re: compile error

[Kornel Benko]

Am Dienstag 06 Oktober 2009 schrieb Gerard Ranke:
> James C. Sutherland  writes:
> > On Oct 6, 2009, at 9:57 AM, Gerard Ranke wrote:
> > > Hi,
> > >
> > > When trying to compile lyx 1.6.4 on irix 6.5.30, I get this error
> > > message:
> > >
> > > cc-1005 CC: ERROR File = ./boost/preprocessor/list/fold_left.hpp,
> > > Line = 37
> > >  The source file "boost/preprocessor/list/detail/edg/fold_left.hpp" is
> > >  unavailable.
> > >
> > >  #include 
> >
> > I am not a LyX developer, but my first guess is that you have an
> > incompatible (very old) version of boost.  What version of boost do
> > you have installed?
>
> I'm using the version that comes with the LyX package. Configure's output:
>
>  checking whether to use boost included library... yes
>
> Any idea what boost version might be acceptible? The INSTALL file doesn't
> mention boost as a requirement. Thanks btw for taking the time to answer!

On ubuntu, this file is part of libboost-dev package.

You may consider to install the corresponing package on your system.

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

Re: compile error

[Gerard Ranke]

James C. Sutherland  writes:

> 
> 
> On Oct 6, 2009, at 9:57 AM, Gerard Ranke wrote:
> 
> > Hi,
> >
> > When trying to compile lyx 1.6.4 on irix 6.5.30, I get this error  
> > message:
> >
> > cc-1005 CC: ERROR File = ./boost/preprocessor/list/fold_left.hpp,  
> > Line = 37
> >  The source file "boost/preprocessor/list/detail/edg/fold_left.hpp" is
> >  unavailable.
> >
> >  #include 
> >
>> 
> I am not a LyX developer, but my first guess is that you have an  
> incompatible (very old) version of boost.  What version of boost do  
> you have installed?

I'm using the version that comes with the LyX package. Configure's output:

 checking whether to use boost included library... yes

Any idea what boost version might be acceptible? The INSTALL file doesn't
mention boost as a requirement. Thanks btw for taking the time to answer!

Re: compile error

[James C. Sutherland]

On Oct 6, 2009, at 9:57 AM, Gerard Ranke wrote:


Hi,

When trying to compile lyx 1.6.4 on irix 6.5.30, I get this error  
message:


cc-1005 CC: ERROR File = ./boost/preprocessor/list/fold_left.hpp,  
Line = 37

 The source file "boost/preprocessor/list/detail/edg/fold_left.hpp" is
 unavailable.

 #include 

Indeed, there is no boost/preprocessor/list/detail/edg/ 
fold_left.hpp. What I do

have is:
boost/boost/preprocessor/list/fold_left.hpp
and
boost/boost/preprocessor/list/detail/fold_left.hpp
Any ideas how to solve this?
Sorry for asking basically the same question as a few years ago, but  
I got no
response then, so forgot about lyx for a while... Still would be  
nice to have it.

TIA,

gerard



I am not a LyX developer, but my first guess is that you have an  
incompatible (very old) version of boost.  What version of boost do  
you have installed?

compile error

[Gerard Ranke]

Hi,

When trying to compile lyx 1.6.4 on irix 6.5.30, I get this error message:

cc-1005 CC: ERROR File = ./boost/preprocessor/list/fold_left.hpp, Line = 37
  The source file "boost/preprocessor/list/detail/edg/fold_left.hpp" is
  unavailable.

  #include 

Indeed, there is no boost/preprocessor/list/detail/edg/fold_left.hpp. What I do
have is:
boost/boost/preprocessor/list/fold_left.hpp
and
boost/boost/preprocessor/list/detail/fold_left.hpp
Any ideas how to solve this?
Sorry for asking basically the same question as a few years ago, but I got no
response then, so forgot about lyx for a while... Still would be nice to have 
it.
TIA,

gerard

compile error: file unavailable

[Gerard Ranke]

Hi all,

I'm trying to build lyx-1.5.2 on Irix 6.5, and I'm getting this error:

cc-1005 CC: ERROR File = 
../../../../boost/boost/preprocessor/list/fold_left.hpp, Line = 37

  The source file "boost/preprocessor/list/detail/edg/fold_left.hpp" is
  unavailable.

  #include 

This file is indeed absent from my lyx distribution, it seems. What I've 
got is:


./boost/boost/preprocessor/list/fold_left.hpp
and
./boost/boost/preprocessor/list/detail/fold_left.hpp

from the top of the distribution, which is /usr/local/lyx-1.5.2. 
Configure options:


./configure --prefix=/usr/nekoware --with-qt4-dir=/usr/nekoware/qt4

Any thoughts on this would be greatly appreciated!
Best regards,

Gerard Ranke

Re: Ubuntu compile error

[John McCabe-Dansted]

On 3/22/07, Bob Lounsbury <[EMAIL PROTECTED]> wrote:

configure:7277: gcc -o conftest -g -O2 -Wextra -Wallconftest.cc  >&5
/tmp/ccgRmGPA.o:(.eh_frame+0x11): undefined reference to
`__gxx_personality_v0'


According to this page:
  http://www.network-theory.co.uk/docs/gccintro/gccintro_54.html
This error is caused by compiling with gcc instead of g++.

try typing "g++ -v" to see if it is available and what version it is.
If it is not available try installing it.

If it is installed, or this doesn't help, try typing
  CXX=g++ ./configure
and see if this works better than a straight configure.

Report any further problems or success.

--
John C. McCabe-Dansted
PhD Student
University of Western Australia

Ubuntu compile error

[Bob Lounsbury]

Hi,

I'm trying to do a ./configure of LyX 1.5.0beta1 and I get the error
message:

"checking size of wchar_t... configure: error: cannot compute sizeof
(wchar_t), 77"

I'm new to this source installation game and I have no idea what this means.

Any suggestions.

Thanks,
Bob

Here is the start of the config.log error:

configure:6958: checking size of wchar_t
configure:7277: gcc -o conftest -g -O2 -Wextra -Wallconftest.cc  >&5
/tmp/ccgRmGPA.o:(.eh_frame+0x11): undefined reference to
`__gxx_personality_v0'
collect2: ld returned 1 exit status
configure:7280: $? = 1
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "LyX"
| #define PACKAGE_TARNAME "lyx"
| #define PACKAGE_VERSION "1.5.0beta1"
| #define PACKAGE_STRING "LyX 1.5.0beta1"
| #define PACKAGE_BUGREPORT "lyx-devel@lists.lyx.org"
| #define USE_POSIX_PACKAGING 1
| #define PACKAGE "lyx"
| #define HAVE_KPSEWHICH 1
| #define WORDS_BIGENDIAN 1
| #ifdef __cplusplus
| extern "C" void std::exit (int) throw (); using std::exit;
| #endif
| #define WITH_WARNINGS 1
| #define _GLIBCXX_CONCEPT_CHECKS 1
| #define HAVE_STD_COUNT 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_OSTREAM 1
| #define HAVE_ISTREAM 1
| #define HAVE_SSTREAM 1
| #define HAVE_LOCALE 1
| #define HAVE_LIMITS 1
| #define HAVE_IOS 1
| #define MODERN_STL_STREAMS 1
| #define ENABLE_ASSERTIONS 1
| #define AIKSAURUS_H_LOCATION
| /* end confdefs.h.  */
| #include 
| #if HAVE_SYS_TYPES_H
| # include 
| #endif
| #if HAVE_SYS_STAT_H
| # include 
| #endif
| #if STDC_HEADERS
| # include 
| # include 
| #else
| # if HAVE_STDLIB_H
| #  include 
| # endif
| #endif
| #if HAVE_STRING_H
| # if !STDC_HEADERS && HAVE_MEMORY_H
| #  include 
| # endif
| # include 
| #endif
| #if HAVE_STRINGS_H
| # include 
| #endif
| #if HAVE_INTTYPES_H
| # include 
| #else
| # if HAVE_STDINT_H
| #  include 
| # endif
| #endif
| #if HAVE_UNISTD_H
| # include 
| #endif
| long longval () { return (long) (sizeof (wchar_t)); }
| unsigned long ulongval () { return (long) (sizeof (wchar_t)); }
| #include 
| #include 
| int
| main ()
| {
|
|   FILE *f = fopen ("conftest.val", "w");
|   if (! f)
| exit (1);
|   if (((long) (sizeof (wchar_t))) < 0)
| {
|   long i = longval ();
|   if (i != ((long) (sizeof (wchar_t
| exit (1);
|   fprintf (f, "%ld\n", i);
| }
|   else
| {
|   unsigned long i = ulongval ();
|   if (i != ((long) (sizeof (wchar_t
| exit (1);
|   fprintf (f, "%lu\n", i);
| }
|   exit (ferror (f) || fclose (f) != 0);
|
|   ;
|   return 0;
| }
configure:7295: error: cannot compute sizeof (wchar_t), 77
See `config.log' for more details.

Re: Beamer Compile Error -- FIXED

[Rich Shepard]

On Sat, 22 Oct 2005, Rich Shepard wrote:


 Is it the mix of definition and enumerate that causes pdflatex the
indigestion? I just do not see the error.


  It was not the mixture of types (I don't think) as much as it was too much
information to fit on a slide. The mixture probably didn't help matters. As
soon as I put the enumerated block on a separate frame, the document compiled
just fine.

I now return you to your regularly scheduled weekend,

Rich

--
Dr. Richard B. Shepard, President |   Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM) |  Impact Assessments Using Fuzzy Logic"
 Voice: 503-667-4517 Fax: 503-667-8863

Beamer Compile Error

[Rich Shepard]

  I've tried adding some subsections and frames in a presentation I'm
writing. I get this error message when compiling with pdflatex:

LaTeX Error: There's no line here to end.
 \lyxframeend
  {}\lyxframe{Information Domains II}
Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

  Just before this error -- in the \lyxframe{Informaiton Domains I} I have a
definition and four lines of enumeration:

\layout BeginFrame

Information Domains I
\layout Definition

A system is defined as a process, event, or mechanism.
 It can be characterized analytically, algorithmically, symbolically, or
 linguistically within defined boundaries.
 A system can be physical, numerical, or conceptual.
\newline

\newline 
Each system is defined relative to four basic information domains:

\layout Enumerate

Input
\layout Enumerate

System
\layout Enumerate

Environment
\layout Enumerate

Output
\layout BeginFrame %% Information Domains II begins here.

  Is it the mix of definition and enumerate that causes pdflatex the
indigestion? I just do not see the error.

TIA,

Rich

--
Dr. Richard B. Shepard, President |   Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM) |  Impact Assessments Using Fuzzy Logic"
 Voice: 503-667-4517 Fax: 503-667-8863

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[Jean-Marc Lasgouttes]

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:

Angus> Anand wrote:
>> How do you enforce compiling without STL?

Angus> Qt's STL compatibility mode means that QString can be converted
Angus> implicitly to/from std::string.

Yes, and it is disabled by defining QT_NO_STL.

Jarc

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[Angus Leeming]

Anand wrote:
> How do you enforce compiling without STL?

Qt's STL compatibility mode means that QString can be converted implicitly
to/from std::string.

-- 
Angus

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[rsamurti]

On Sunday 17 Jul 2005 6:16 pm, Georg Baum wrote:
> Am Sonntag, 17. Juli 2005 08:40 schrieb [EMAIL PROTECTED]:
> > Can anybody help to correct this error?
>
> Change line 350 of QPrefs.C from
>
>  if (cb->text(i) == default_font_name) {
>
> to
>  if (fromqstr(cb->text(i)) == default_font_name) {
>
>
> Georg
I did this. Now it is compiling properly. Thank you.

Anand

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[rsamurti]

On Sunday 17 Jul 2005 9:33 pm, Jean-Marc Lasgouttes wrote:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>
> Georg> Am Sonntag, 17. Juli 2005 08:40 schrieb [EMAIL PROTECTED]:
> >> Can anybody help to correct this error?
>
> Georg> Change line 350 of QPrefs.C from
>
> Georg>  if (cb->text(i) == default_font_name) {
>
> Georg> to if (fromqstr(cb->text(i)) == default_font_name) {
>
> I did that in 1.3.7, and additionally enforced compiling without STL
> compatibility.
>
> JMarc
How do you enforce compiling without STL?

Anand

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[Rich Shepard]

On Sun, 17 Jul 2005, Jean-Marc Lasgouttes wrote:


I did that in 1.3.7, and additionally enforced compiling without STL
compatibility.


JMarc,

  Thank you. Patrick seems to not be a fan of STL. I had fits trying to
compile a GIS application that requires it. Finally just gave up.

Rich

--
Dr. Richard B. Shepard, President  | Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM)  | Impact Assessments Using Fuzzy Logic"
   Voice: 503-667-4517   Fax: 503-667-8863

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[Jean-Marc Lasgouttes]

> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:

Georg> Am Sonntag, 17. Juli 2005 08:40 schrieb [EMAIL PROTECTED]:
>> Can anybody help to correct this error?

Georg> Change line 350 of QPrefs.C from

Georg>  if (cb->text(i) == default_font_name) {

Georg> to if (fromqstr(cb->text(i)) == default_font_name) {

I did that in 1.3.7, and additionally enforced compiling without STL
compatibility.

JMarc

Re: LyX-1.3.6 compile error on Slackware-10.1 system.

[Georg Baum]

Am Sonntag, 17. Juli 2005 08:40 schrieb [EMAIL PROTECTED]:

> Can anybody help to correct this error?

Change line 350 of QPrefs.C from

if (cb->text(i) == default_font_name) {

to
if (fromqstr(cb->text(i)) == default_font_name) {


Georg

LyX-1.3.6 compile error on Slackware-10.1 system.

[rsamurti]

Hello,

I tried to compile LyX-1.3.6 on stock Slackware 10.1 system. My build script 
is given below:

#!/bin/sh

VERSION=1.3.6

SLKCFLAGS="-O2 -march=i486 -mcpu=i686"
CFLAGS="$SLKCFLAGS"
CXXFLAGS="$SLKCFLAGS"

rm -rf lyx-$VERSION
tar -xjvf lyx-$VERSION.tar.bz2
cd lyx-$VERSION

# Corret ownerships
chown -R root.root .

# Correct permissions
find . -perm 664 -exec chmod 644 {} \;
find . -perm 600 -exec chmod 644 {} \;
find . -perm 444 -exec chmod 644 {} \;
find . -perm 400 -exec chmod 644 {} \;
find . -perm 440 -exec chmod 644 {} \;
find . -perm 777 -exec chmod 755 {} \;
find . -perm 775 -exec chmod 755 {} \;
find . -perm 511 -exec chmod 755 {} \;
find . -perm 711 -exec chmod 755 {} \;
find . -perm 555 -exec chmod 755 {} \;
find . -perm 666 -exec chmod 644 {} \;

./configure --prefix=/usr \
--build=i486-slackware-linux \
 --with-frontend=qt
make all
checkinstall

When I run the above script, configure went off well and I got the following 
output:

Configuration
  Host type:  i486-slackware-linux-gnu
  Special build flags:aiksaurus use-pspell use-ispell
  C   Compiler:   gcc
  C   Compiler flags: -g -O2
  C++ Compiler:   g++ (3.3.4)
  C++ Compiler flags: -O
  Linker flags:   
  Frontend:   qt
Qt version:   3.3.3
  Packaging:  posix
LyX binary dir:   /usr/bin
LyX files dir:/usr/share/lyx

Configuration of LyX was successful.

But during make all I got the following error messages:

g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -I../../../src 
-I../../../src/frontends -I../../../images -I./qt2 -I/usr/lib/qt/include 
-I../../../boost -I../../../src/frontends/controllers 
-isystem /usr/X11R6/include -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR 
-DQT_THREAD_SUPPORT -O -MT QPrefs.lo -MD -MP -MF .deps/QPrefs.Tpo -c QPrefs.C
QPrefs.C: In function `void ::setComboxFont(QComboBox*, const 
   std::string&, const std::string&, QFont::StyleHint)':
QPrefs.C:350: error: no match for 'operator==' in 'QComboBox::text(int) 
   const(i) == default_font_name'
../../../src/lyxlength.h:85: error: candidates are: bool operator==(const 
   LyXLength&, const LyXLength&)
../../../src/lyxgluelength.h:67: error: bool operator==(const 
   LyXGlueLength&, const LyXGlueLength&)
../../../src/Spacing.h:76: error: bool operator==(const 
   Spacing&, const Spacing&)
../../../src/Bullet.h:48: error: bool operator==(const 
Bullet&, 
   const Bullet&)
../../../src/lyxfont.h:438: error: bool operator==(const 
   LyXFont&, const LyXFont&)
../../../src/lyxfont.h:427: error: bool operator==(const 
   LyXFont::FontBits&, const LyXFont::FontBits&)
/usr/lib/qt/include/qcstring.h:299: error: bool 
   operator==(const QCString&, const QCString&)
/usr/lib/qt/include/qcstring.h:302: error: bool 
   operator==(const QCString&, const char*)
/usr/lib/qt/include/qcstring.h:305: error: bool 
   operator==(const char*, const QCString&)
/usr/lib/qt/include/qstring.h:303: error: bool 
operator==(char, 
   QChar)
/usr/lib/qt/include/qstring.h:308: error: bool 
   operator==(QChar, char)
/usr/lib/qt/include/qstring.h:313: error: bool 
   operator==(QChar, QChar)
/usr/lib/qt/include/qstring.h:1015: error: bool 
   operator==(const QString&, const QString&)
/usr/lib/qt/include/qstring.h:1022: error: bool 
   operator==(const QString&, const char*)
/usr/lib/qt/include/qstring.h:1028: error: bool 
   operator==(const char*, const QString&)
/usr/lib/qt/include/qpoint.h:148: error: bool operator==(const 
   QPoint&, const QPoint&)
/usr/lib/qt/include/qsize.h:162: error: bool operator==(const 
   QSize&, const QSize&)
/usr/lib/qt/include/qrect.h:151: error: bool operator==(const 
   QRect&, const QRect&)
make[5]: *** [QPrefs.lo] Error 1
make[5]: Leaving directory `/home/anand/lyx-1.3.6/src/frontends/qt2'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/anand/lyx-1.3.6/src/frontends/qt2'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/anand/lyx-1.3.6/src/frontends'
make[2]: *** [all-recursive] Error 1

Can anybody help to correct this error?

Thanks for your help,

Anand

Re: Quickly Finding Compile Error Boxes

[Juergen Spitzmueller]

Rich Shepard wrote:
> Is there a
> way to quickly find the location of the error box? I don't see that on a
> menu and I have almost 200 pages of material now.

Navigate -> Error.

Regards,
Jürgen

Re: Quickly Finding Compile Error Boxes -- SOLVED

[Rich Shepard]

On Thu, 4 Nov 2004, Paul A. Rubin wrote:
Navigate->Error (C-g)?
Paul,
  Thanks! I never looked that far down the list so I hadn't seen all the
goodies there.
Rich
--
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
   Voice: 503-667-4517   Fax: 503-667-8863

Re: Quickly Finding Compile Error Boxes

[Paul A. Rubin]

Rich Shepard wrote:
  For some reason, my book generated an error when I tried to compile it
using pdflatex within version 1.3.5 (on linux, of course :-) ). Is there a
way to quickly find the location of the error box? I don't see that on a
menu and I have almost 200 pages of material now.
Thanks,
Rich
Navigate->Error (C-g)?
-- Paul

Quickly Finding Compile Error Boxes

[Rich Shepard]

  For some reason, my book generated an error when I tried to compile it
using pdflatex within version 1.3.5 (on linux, of course :-) ). Is there a
way to quickly find the location of the error box? I don't see that on a
menu and I have almost 200 pages of material now.
Thanks,
Rich
--
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
   Voice: 503-667-4517   Fax: 503-667-8863

Re: again, the C-M C-M \alpha -> compile error problem.

[Bo Peng]

On Sun, Dec 21, 2003 at 11:50:29PM -0600, Bo Peng wrote:

> The following works for 1.4cvs: a black WrongFormula box will be shown 
> in place of wrong formula. This is just to show the idea, no efficiency  
> has been considered.

My small script only works for *new* wrong formula and will fail when 
opening a file with correct and wrong formula (so 0lyxpreview.tex will 
have multiple previews). 

A thorough treatment would have to find out and then replace the wrong 
formulas (by compiling previews one by one?). This will be much more 
complicated and time consuming.  

I should not have expected this problem to be so easy. :-(


-- 
Bo Peng

Re: again, the C-M C-M \alpha -> compile error problem.

[Bo Peng]

> cat >> wrong formula.tex  <> wrongformula.tex <

Re: again, the C-M C-M \alpha -> compile error problem.

[Bo Peng]

> I had a look at the source code and found that we only need to change
> lib/scripts/lypreview2bitmap.sh. If you allow, I will try to figure out a
> patch.

The following works for 1.4cvs: a black WrongFormula box will be shown 
in place of wrong formula. This is just to show the idea, no efficiency  
has been considered.


edit lib/scripts/lyxpreview2bitmap.sh, remove line 131:
BAIL_OUT "Failed: ${LATEX} ${TEXFILE}"

replace it with

head -`grep -n 'begin{preview}' ${TEXFILE} | cut -d: -f1` ${TEXFILE} > wrongformula.tex
cat >> wrong formula.tex  <

Re: again, the C-M C-M \alpha -> compile error problem.

[Bo Peng]

>
> As the guy writing the code, I beg to differ.
>
> Turn on instant preview and assume that any inset not previewed is
> wrong?
>

I notice that instant preview is not *always* working. I have not tried to
repeat this bug (?) but  I sometimes need to enter a formula and leave to
let it be displayed. Also, raw display seems to be 'normal' and is not
enough a sign of wrong formula.

I had a look at the source code and found that we only need to change
lib/scripts/lypreview2bitmap.sh. If you allow, I will try to figure out a
patch.

Bo

Re: again, the C-M C-M \alpha -> compile error problem.

[Angus Leeming]

Bo Peng wrote:

> 
>> The effort for a black alpha is zero, the effort for a red one is
>> substantial, or in other words, _I_ won't do it. If there was a
>> clean patch by someone else, I might apply it, though...
> 
> 
> I have another idea. Under 'instant preview', when error happens and
> latex can not compile the snipet, lyx will do nothing. How about
> returning some image of 'wrong formula'?
> 
> I think this is a good idea since
> 1. Running latex on small pieces of code is a cost-effective way to
>check for errors. .. and 'instant preview' has done that for us.
> 2. This can detect not only \text{\alpha}, but also other common
>errors such as \cases without amsmath.
> 3. As far as I can see, the effort of doing this is not significant.

As the guy writing the code, I beg to differ.

Turn on instant preview and assume that any inset not previewed is 
wrong?

-- 
Angus

Re: again, the C-M C-M \alpha -> compile error problem.

[Bo Peng]

> The effort for a black alpha is zero, the effort for a red one is
> substantial, or in other words, _I_ won't do it. If there was a clean
> patch by someone else, I might apply it, though...


I have another idea. Under 'instant preview', when error happens and 
latex can not compile the snipet, lyx will do nothing. How about 
returning some image of 'wrong formula'?

I think this is a good idea since
1. Running latex on small pieces of code is a cost-effective way to 
   check for errors. .. and 'instant preview' has done that for us.
2. This can detect not only \text{\alpha}, but also other common 
   errors such as \cases without amsmath.
3. As far as I can see, the effort of doing this is not significant. We 
   need only to change the snipet latex code to '\fbox{wrong formula}' 
   when compilation fails and then compile again.

Any opinions?

-- 
Bo Peng

Re: again, the C-M C-M \alpha -> compile error problem.

[Angus Leeming]

Andre Poenitz wrote:
>> How about a red \alpha instead of black one? Or, a red error box
>> like the ones after we compile the file?
> 
> The effort for a black alpha is zero, the effort for a red one is
> substantial, or in other words, _I_ won't do it. If there was a
> clean patch by someone else, I might apply it, though...
> 
> But if people can't distinguish blue and black I'd guess they won't
> be good at distinguishing blue and red either

How about red-and-flashing? :-P

-- 
Angus

Re: again, the C-M C-M \alpha -> compile error problem.

[Andre Poenitz]

On Thu, Dec 11, 2003 at 12:11:08PM -0600, Bo Peng wrote:
> > > It is not a very bad idea. A big message box will be intrusive (and 
> > > scary) but users will learn very quickly how to avoid it.
> 
> > No they won't, they'll just come and complain at you, and at us. Users
> > do not read error boxes, and they certainly don't read intrusive and
> > rude ones like the one you suggest.
> 
> *nod*, *sign*
> 
> > Andre's suggestion of a status bar message is probably better, but I
> > still doubt many will ever see/read it.
> 
> How about a red \alpha instead of black one? Or, a red error box like 
> the ones after we compile the file?

The effort for a black alpha is zero, the effort for a red one is
substantial, or in other words, _I_ won't do it. If there was a clean
patch by someone else, I might apply it, though...

But if people can't distinguish blue and black I'd guess they won't be
good at distinguishing blue and red either

Andre'

Re: again, the C-M C-M \alpha -> compile error problem.

[Bo Peng]

> > It is not a very bad idea. A big message box will be intrusive (and 
> > scary) but users will learn very quickly how to avoid it.

> No they won't, they'll just come and complain at you, and at us. Users
> do not read error boxes, and they certainly don't read intrusive and
> rude ones like the one you suggest.

*nod*, *sign*

> Andre's suggestion of a status bar message is probably better, but I
> still doubt many will ever see/read it.

How about a red \alpha instead of black one? Or, a red error box like 
the ones after we compile the file?

-- 
Bo Peng

Re: again, the C-M C-M \alpha -> compile error problem.

[Andre Poenitz]

On Thu, Dec 11, 2003 at 11:55:55AM -0600, Bo Peng wrote:
> > but also because I won't go through all 700 supported symbols and 
> > figure out which ones are safe to use in text and which ones are not.
> 
> As I said, the warning message does not have to be fired for ALL 
> symbols. Just all Greek letters and less than 20 \le \sum, \frac etc. I 
> am a statistician and I believe this will cover 99% of the cases.

*grin*

Well. And I am a lazy programmer ;-)

Andre'