Roger McMurtrie wrote:
> 
> I don't have a \fontscheme in lyx, nor can I see it in the LaTeX log file
> (View->LaTeX Logfile).

It would actually be in the .lyx file and you would need to use
less||vi||cat||grep||notepad to see it, it is a LyX setting from a dialog.
the "xset:  bad font path element ..." seems rather un-helpful except that
it tells you there is a problem with fonts, I was trying to figure out which
font it did not like. I am not sure it is related to the problem, but the
programmer in me wants all warnings cleaned up to be sure they are unrelated
to the problem :).

<SNIP> 
> The LaTeX logfile contains Warnings that each citation is undefined.
> 
> When I View->DVI a second time, TOC and citations work, the debug output is
> the same as for the first run (still no "Run #"s or  "Scanning aux file:
> #.aux") but, of course, the LaTeX logfile doesn't have any citation warnings.
> 

The second and further run are using the data cached temporarily from the
first run. Still seems strange that LyX does not automatically handle it.

when I view->DVI on the attached simple lyx file, I get Run #1 and Run #2
and the TOC and refs are correct. also attached is the log of the run,
compressed because its ~9k.

BTW, if someone feels these attached files would be useful to put these
files on the WIKI, you have my permission.

> The problem returns if I close the file (without closing lyx) then reopen it.
> 
> Roger
> 
> On Thu, 30 Jun 2005 11:26 pm, Todd Denniston wrote:
<SNIP>
> > So you can see what a working run looks like, here is my debug output
> > (trimmed down a bit), for a file with a TOC and cross refs. Also note the
> > 'Run #'s, I don't see them in your log:
> >
> > Setting debug level to 128
> > Debugging `latex' (LaTeX generation/execution)
> > makeLaTeXFile...
> >   Validating buffer...
> > Color enabled. Font: Bold, Smallest, red, Language: English
> > Color enabled. Font: Bold, Smallest, red, Underline On, Language: English
> > Color enabled. Font: Bold, Smallest, red, Language: English
> > LyX needs the following commands when LaTeXing:
> > ***** Packages:\usepackage{color}
<SNIP>
> > Roger McMurtrie wrote:
<SNIP>
> > > $ lyx -dbg 128
> > > Setting debug level to 128
> > > Debugging `latex' (LaTeX generation/execution)
> > >
> > > On opening file:
> > >
> > > xset:  bad font path element (#59), possible causes are:
> > >     Directory does not exist or has wrong permissions
> > >     Directory missing fonts.dir
> > >     Incorrect font server address or syntax
> > > Unable to add font path.
> > >
> > > On View->DVI:
> > >
> > > makeLaTeXFile...
> > >   Validating buffer...
> > > LyX needs the following commands when LaTeXing:
> > > ***** Packages:\usepackage{amsmath}
> > > \usepackage{setspace}
> > > \onehalfspacing
> > > \usepackage{amssymb}
<SNIP>
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default

\layout Standard

some text on a page
\begin_inset LatexCommand \label{some-text-on}

\end_inset 


\layout Standard
\pagebreak_top 

\begin_inset LatexCommand \tableofcontents{}

\end_inset 


\layout Section
\pagebreak_top 
a section
\begin_inset LatexCommand \label{sec:a-section}

\end_inset 


\layout Standard

a cross ref to some text on page 
\begin_inset LatexCommand \pageref{some-text-on}

\end_inset 


\layout Subsection
\pagebreak_top 
a subsection
\layout Standard

a cross ref to section 
\begin_inset LatexCommand \ref{sec:a-section}

\end_inset 

.
\the_end

Attachment: newfile1.lyxdbglog.tgz
Description: Binary data

Reply via email to