Re: Books in LyX: Was How to import separate chapters into document?

[Anthony Campbell]

On 20 Feb 2009, Steve Litt wrote:
 On Friday 20 February 2009 09:35:27 am Anthony Campbell wrote:
  I'm just starting to prepare my fourth book with Lyx, this time using
  1.6.1 instead of 1.5.x.
 
 Anthony,
 
 What were your other three books? Are you self-publishing them, were they 
 published by others, or were they books used internally by an organization? 
 Are their descriptions/sales-brochures viewable on the Internet?
 
 What challenges did you have to overcome in order to write books with LyX, 
 and 
 in what ways was LyX a pleasant surprise? Do you have any tips you can give 
 others who write books using LyX?
 
 If you, I and a few others answer these questions, it might make life easier 
 for lots of people trying to write books in LyX.

[snip] 

The three books I have out at present are described on my website:
Homeopathy in Perspective, The Assassins of Alamut, Totality Beliefs and
the Religious Imagination. I had been using Latex for a long time before
this, including for book writing, and an reasonably au fait with it,
though far from an expert. I still write letters and shorter stuff in
Latex since I have the templates ready. I started using Lyx as an
experiment because I was finding it difficult and time-consuming to
include pictures in the text with wrap-around using Latex. 

I'm now fully persuaded of the value of Lyx for books. I would not say
there have been any major problems, apart from some issues with
including the Preface in the TOC and things like that. This list is
extremely useful and helpful in sorting them out. My policy generally is
Keep it Simple, so I mostly accept the defaults in the Book Class and
don't try to be clever.

What I particularly value in Lyx is the ability to make footnotes
easily. I regret the demise of the footnote in printed books and it's a
delight to be able to have as many as I like at the touch of a button.
Aother thing I like is that I can get an instantaneous preview of a page
which shows me exactly how it will look in the book. Making the index is
also easy.

As regards my method of working, I don't generally compose the text
directly in Lyx. I write in vim (gvim) which I'm used to and which
allows me to make large-scale changes quickly and easily. When I've got
the text more or less as I want it, I then import it into Lyx and carry
on from there.

Anthony

-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews, 
and sceptical articles)

Re: serious problems with LyX (semi-fatal crashes)

[Murat Yildizoglu]

Neither me, under Windows XP and the last stable LyX.

2009/2/21 Stefano Franchi fran...@philosophy.tamu.edu

 On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
  Vincent van Ravesteijn schreef:
   Before releasing 1.6.0 there were a number of bugs which depended on
   the location of the cursor at the time of right-clicking. Maybe this
   helps you ..
  
   I mean, there happen strange things if you right-click on a certain
   inset A.. keep the mouse down and then release it at another inset B.
   Now, the context menu of inset A is requested, but the enabling of
   items is dependent on inset B. This enabling/disabling is done via the
   getStatus mechanism, and that's exactly what I see in your backtrace.
   Maybe your tried to right-click the comment, but incidentally released
   the mouse at a neighbouring inset, which couldn't properly handle the
   next-inset-modify command and kaboom  just guessing.
  
   Vincent
 
  Bingo!
 
  1. New LyX file
  2. Insert label
  3. Insert comment
  4. Right-click on the button of the comment
  5. Hold down the mouse
  6. Release on the label
  7. Assertion.
 
 
  Vincent

 Hmm,

 if what you meant was

 4. Right click on the button of the comment
 5. Hold down the mouse
 5'. move the cursor over the label
 6. Release the right button


 then I cannot reproduce it on my system.

 S.


 __
 Stefano Franchi
 Department of Philosophy  Ph:  (979) 862-2211
 Texas AM University  Fax: (979) 845-0458
 305B Bolton Hall  fran...@philosophy.tamu.edu
 College Station, TX 77843-4237




-- 
*** NEW UNIVERSITY, NEW ADDRESS ! ***

Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http://www.vcharite.univ-mrs.fr/PP/yildi/index.html
__

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 11:21, Murat Yildizoglu wrote:

Neither me, under Windows XP and the last stable LyX.


Stefano seems to be using a debug build. In this build mode an assertion 
causes a crash each time. With a release build assertions are softer 
and, most of the time, the only visible effect is a message on the 
console or the cursor is moving weirdly.


Stefano, whenever you need to work seriously with LyX don't compile in 
full debug mode.


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
 On 21/02/2009 11:21, Murat Yildizoglu wrote:
  Neither me, under Windows XP and the last stable LyX.

 Stefano seems to be using a debug build. In this build mode an assertion
 causes a crash each time. With a release build assertions are softer
 and, most of the time, the only visible effect is a message on the
 console or the cursor is moving weirdly.

 Stefano, whenever you need to work seriously with LyX don't compile in
 full debug mode.

 Abdel.


Well, I am using a debug build now because I wanted to help tracking down the 
bug. It is frequent enough to have become a serious annoyance. But I started 
experiencing the problem (and started this thread) with the standard build. 

So what Abdel's message seems to imply is that either:

1. the assert problem is not related to the crashes I experienced originally

or 

2. I somehow was unwittingly using a debug build before recompiling Lyx with 
the debug option


I'll look into the second option, but i doubt it is the case. Which means I am 
at sea once again.


S.


__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 15:10, Stefano Franchi wrote:

On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:

On 21/02/2009 11:21, Murat Yildizoglu wrote:

Neither me, under Windows XP and the last stable LyX.

Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions are softer
and, most of the time, the only visible effect is a message on the
console or the cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX don't compile in
full debug mode.

Abdel.



Well, I am using a debug build now because I wanted to help tracking down the
bug. It is frequent enough to have become a serious annoyance.


And this is very nice of you to do that :-)


But I started
experiencing the problem (and started this thread) with the standard build.

So what Abdel's message seems to imply is that either:

1. the assert problem is not related to the crashes I experienced originally


Unless you can reproduce the last crash with a release build with the 
same symptoms I am tempted to say that the two crashes are unrelated indeed.




or

2. I somehow was unwittingly using a debug build before recompiling Lyx with
the debug option


I remember that Debian packages used to have full assertion enabled 
sometime ago, I don't know if they changed their policy since then...


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

  Before releasing 1.6.0 there were a number of bugs
 which depended on the location of the cursor at the time of
 right-clicking. Maybe this helps you ..
 I mean, there happen strange things if you right-click on a
 certain inset A.. keep the mouse down and then release it at
 another inset B. Now, the context menu of inset A is
 requested, but the enabling of items is dependent on inset
 B. This enabling/disabling is done via the getStatus
 mechanism, and that's exactly what I see in your
 backtrace. Maybe your tried to right-click the comment, but
 incidentally released the mouse at a neighbouring inset,
 which couldn't properly handle the
 next-inset-modify command and kaboom  just
 guessing.
  
  Vincent

 I have same problem that Stefano but when I writing, not when I make a mouse 
click.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: serious problems with LyX (semi-fatal crashes)

[Vincent van Ravesteijn]

Marcelo Acuña schreef:

Before releasing 1.6.0 there were a number of bugs
  

which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then release it at
another inset B. Now, the context menu of inset A is
requested, but the enabling of items is dependent on inset
B. This enabling/disabling is done via the getStatus
mechanism, and that's exactly what I see in your
backtrace. Maybe your tried to right-click the comment, but
incidentally released the mouse at a neighbouring inset,
which couldn't properly handle the
next-inset-modify command and kaboom  just
guessing.


Vincent
  


 I have same problem that Stefano but when I writing, not when I make a mouse 
click.
 Marcelo
  
Yes, .. Stefano came across another problem.. but the good news is that 
his original problem (and yours) has disappeared :).


Vincent

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

 Stefano seems to be using a debug build. In this build mode
 an assertion causes a crash each time. With a release build
 assertions are softer and, most of the time, the
 only visible effect is a message on the console or the
 cursor is moving weirdly.
 
 Stefano, whenever you need to work seriously with LyX
 don't compile in full debug mode.
 
 Abdel.

Hello,
 excuse me. I want to say that I compiled lyx without any debug mode.
 When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key and 
save my work.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 16:13, Marcelo Acuña wrote:

Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX
don't compile in full debug mode.

Abdel.


Hello,


Hi Marcelo,


  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key and 
save my work.


If you can press F2 and save your work then LyX is not frozen, it's just 
that it lost the editing focus. This happens for obscure reasons and I 
think part of this bug has been fixed recently. The next time this 
happen, just click with your mouse in the editing area to get the focus 
back.


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 08:19:16 Abdelrazak Younes wrote:
 On 21/02/2009 15:10, Stefano Franchi wrote:
  On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
  On 21/02/2009 11:21, Murat Yildizoglu wrote:
  Neither me, under Windows XP and the last stable LyX.
 
  Stefano seems to be using a debug build. In this build mode an assertion
  causes a crash each time. With a release build assertions are softer
  and, most of the time, the only visible effect is a message on the
  console or the cursor is moving weirdly.
 
  Stefano, whenever you need to work seriously with LyX don't compile in
  full debug mode.
 
  Abdel.
 
  Well, I am using a debug build now because I wanted to help tracking down
  the bug. It is frequent enough to have become a serious annoyance.

 And this is very nice of you to do that :-)

  But I started
  experiencing the problem (and started this thread) with the standard
  build.
 
  So what Abdel's message seems to imply is that either:
 
  1. the assert problem is not related to the crashes I experienced
  originally

 Unless you can reproduce the last crash with a release build with the
 same symptoms I am tempted to say that the two crashes are unrelated
 indeed.

  or
 
  2. I somehow was unwittingly using a debug build before recompiling Lyx
  with the debug option

 I remember that Debian packages used to have full assertion enabled
 sometime ago, I don't know if they changed their policy since then...

 Abdel.


That sounds right. So what's the best way to have both a debug-enabled and a 
plain vanilla lyx installed?

Can I just move the debug-enabled binary out of the source directory, make 
clean, and recompile without the debugging option? Or does the binary need 
similarly 
compiled libraries and other files? Sorry if the questions sound silly, but I 
have no idea how Lyx handles the compilation process..

Cheers,

S.




__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[rgheck]

Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a 
plain vanilla lyx installed?


  
Don't install the debug version. You can run it from where you compiled 
it. I just use a little script:



#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
/cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
if [ -f $OFFENDER ]; then rm $OFFENDER; fi


saved as lyx16 to run the debug-enabled version.

rh

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

excuse me. I want to say that I compiled lyx without
 any debug mode.
When I writing quickly, I get Lyx frozen like
 Stefano. I can press F2 key and save my work.
 
 If you can press F2 and save your work then LyX is not
 frozen, it's just that it lost the editing focus. This
 happens for obscure reasons and I think part of this bug has
 been fixed recently. The next time this happen, just click
 with your mouse in the editing area to get the focus back.
 
 Abdel.

 No. Is not a lost of editing focus. I make a lot of click over all lyx parts 
and I can´t get lyx work again. I need kill it and run again.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: newbies's difficulties

[Paul A. Rubin]

Edgar Ataíde wrote:

I am a newbie to Lyx, but I have several difficulties that I cannot
overcome. I made the complete installation of MiKTeX. I verified if
all the packages, available in MiKTeX, were installed namely Jhep.
For my surprise this package (article, book, report) is not available
in LyX, Document -Settings - Document Class. 


I have JHEP installed, but as far as I can tell it's just one document 
type (I assume article).  In any case, LyX does not come with a layout 
file for it (at least not that I can find), so you would need to find 
(or create) one.  See section 5.2 of the Customization manual.



Another aspect that I
do not understand is that the Springer styles appear in Lyx at
Document -Settings - Document Class as unavailable although they
appear as found in the Latex Configuration (I attached this file
in my mail).


Your configuration file apparently was not attached.  However, I have 
the same thing -- my configuration file lists them as found.  In point 
of fact, I don't think I have them installed (at least I cannot find 
them, nor can I find a MiKTeX package that would contain them).  I 
wonder if the LyX configuration script has a bug in it creating a false 
positive here.


In any event, if you need these classes, you can download and install 
the LaTeX packages manually from CTAN (Customization, section 5.1), run 
MiKTeX's Settings application and click Refresh FNDB (this is the 
equivalent of running texhash as described in the Customization manual), 
then load LyX, run Tools  Reconfigure, and restart LyX.  That should 
(hopefully) make the document classes available.


Another error I cannot overcome is the following:

I need to use xypic package. To train myself, I tried to make some
diagrams that are in XY-pic manual, namely the diagram that is at the
bottom of page 3. This particular diagram gives me the following
error, when I try to make the PDF output:

TeX capacity exceeded, sorry [input stack size=5000].



I'm not sure, but I think sometimes syntax errors in the source document 
 lead to that error message.  I'm attaching a LyX file containing the 
diagram.  Try it with your installation.  If the PDF output comes out 
correctly, compare the document contents to your version and see if 
perhaps you can find a discrepancy.  (View  Source is a good way to do 
this -- it will show you the LaTeX code that LyX will emit.)


/Paul


xypic_test.lyx
Description: application/lyx

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 09:46:36 rgheck wrote:
 Stefano Franchi wrote:
  So what's the best way to have both a debug-enabled and a
  plain vanilla lyx installed?

 Don't install the debug version. You can run it from where you compiled

 it. I just use a little script:
  #!/bin/bash
  USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
  if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
  /cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
  if [ -f $OFFENDER ]; then rm $OFFENDER; fi

 saved as lyx16 to run the debug-enabled version.

 rh

I didn't make myself clear, I am afraid. What I meant was:

I never installed the debuge-enabled binary, I am running ot fromt the src 
subdir in the lys-src directory. But I am not sure (see previous messages) if 
the previously installed LyX version is or is not debug-enabled. So I want to 
reinstall it from scratch. Two options:

1.  I have to redownload the sources, unpack them in another dir, conf/make/ 
install

2. I can just take the debug-enabled compiled  lyx binary out of the existing 
source tree, make clean, re-cong, / make / install


S

__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[rgheck]

Stefano Franchi wrote:

On Saturday 21 February 2009 09:46:36 rgheck wrote:
  

Stefano Franchi wrote:


So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
  

Don't install the debug version. You can run it from where you compiled

it. I just use a little script:


#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
/cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
if [ -f $OFFENDER ]; then rm $OFFENDER; fi
  

saved as lyx16 to run the debug-enabled version.

rh



I didn't make myself clear, I am afraid. What I meant was:

I never installed the debuge-enabled binary, I am running ot fromt the src 
subdir in the lys-src directory. But I am not sure (see previous messages) if 
the previously installed LyX version is or is not debug-enabled. So I want to 
reinstall it from scratch. Two options:


1.  I have to redownload the sources, unpack them in another dir, conf/make/ 
install


2. I can just take the debug-enabled compiled  lyx binary out of the existing 
source tree, make clean, re-cong, / make / install


  
Either way should do. Here's what I do: I have two separate trees, one 
called lyx-pristine, one called lyx16. The former is the non-debug build 
linked to the lyx16 svn tree; I have a cron job that keeps it updated, 
and I recompile it and install it from time to time. The other is the 
same tree but a debug build. It never gets installed but is run from the 
script.


rh

Dimensions of figure wrap float

[Hubert Christiaen]

Hello!
I find Lyx a very sophisticated program, but I am deceived by the way it 
handles figure wrap floats. Without correction, I have between 50 to 100% 
excess white space below the figure. The best way of controlling this seems 
to specify a height in lines. One could expect that if one specifies 15 lines 
as height, the systeem will take the height of the default normal line and 
multitply this by 15 and use this as height. Unfortunately, the systeem just 
seems to count the lines on the side of the image. But I have chosen to have 
an empty line between paragraphs. This empty line is not counted. Sometimes 
at the side of the image is a mathematical expression with a matrix 
multiplication in it. This is counted as 1 line althought the heigt is 4 or 5 
times a normal line height! So if I add or delete more than 2 lines, I have 
to adjust all the figures in the following pages. This is clearly 
unacceptable. There should be a way of specifying the height of a figure in 
an absolute way, which does not change over time.

One could also use '\vspace{}' with a negative number, but this is far 
less 'reactive' of precise.

Sincerely,
Hubert

-- 
Hubert Christiaen
Bloesemlaan 17
3360 Korbeek-Lo
Belgium   

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
  Stefano seems to be using a debug build. In this build mode
  an assertion causes a crash each time. With a release build
  assertions are softer and, most of the time, the
  only visible effect is a message on the console or the
  cursor is moving weirdly.
 
  Stefano, whenever you need to work seriously with LyX
  don't compile in full debug mode.
 
  Abdel.

 Hello,
  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key
 and save my work. Marcelo



That indeed was my original problem---before the more recent issues with 
asserts which are probably unrelated.
That is: Lyx is frozen in the sense that it does not accept any input 
*except* control commands (or function keys).

S.





   Yahoo! Cocina
 Recetas prácticas y comida saludable
 http://ar.mujer.yahoo.com/cocina/


__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 17:49, Stefano Franchi wrote:

On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:

Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX
don't compile in full debug mode.

Abdel.

Hello,
  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key
and save my work. Marcelo




That indeed was my original problem---before the more recent issues with
asserts which are probably unrelated.
That is: Lyx is frozen in the sense that it does not accept any input
*except* control commands (or function keys).


That is really weird indeed...

Abdel.

Re: Books in LyX: Was How to import separate chapters into document?

[Abdelrazak Younes]

On 21/02/2009 09:53, Anthony Campbell wrote:

On 20 Feb 2009, Steve Litt wrote:

On Friday 20 February 2009 09:35:27 am Anthony Campbell wrote:

I'm just starting to prepare my fourth book with Lyx, this time using
1.6.1 instead of 1.5.x.

Anthony,

What were your other three books? Are you self-publishing them, were they
published by others, or were they books used internally by an organization?
Are their descriptions/sales-brochures viewable on the Internet?

What challenges did you have to overcome in order to write books with LyX, and
in what ways was LyX a pleasant surprise? Do you have any tips you can give
others who write books using LyX?

If you, I and a few others answer these questions, it might make life easier
for lots of people trying to write books in LyX.


[snip]

The three books I have out at present are described on my website:
Homeopathy in Perspective, The Assassins of Alamut,


off topic/
I've skimmed over the summary, looks very interesting. There's another 
famous book that talk about this sect: Samarcand by Hamid Malouf.
This book is a romanced biography of Omar Khayam, the most famous arabic 
poet. As far from I remember from this excellent book, the word 
Assassin come from Assass Iyoun i.e. the fidels of Iyoun, or 
something like that. This book is a must read :-)

off topic/

Abdel.

why doesn't \numberwithin{equation}{section} work?

[Erez Yerushalmi]

Hi All,

I've been trying to figure this out for a long time. Maybe one of you can
help me?

I've been using  \numberwithin{equation}{section}   in the preamble for
quite some time.
Every time I open a new template, it takes me some time until the PDF output
doesn't get jammed with a crash.
This must mean I don't really understand something.

When I remove \numberwithin{equation}{section}   from the preamble, pdf
output works fine.
When I put it back in, Lyx pdf output crashes.

My errors are the following:

error Undefined control sequence, with description

\numberwithin{equation}{section} % #section.#equation

The control sequence at the end of the top line

of your error message was never \def'ed. If you have

misspelled it (e.g., `\hobx'), type `I' and the correct

spelling (e.g., `I\hbox'). Otherwise just continue,

and I'll forget about whatever was undefined.


second error: LaTeX Error: Missing \begin{document}.


with description:

\numberwithin{equation}{section} % #section.#equation

You're in trouble here. Try typing return to proceed.

If that doesn't work, type X return to quit.


I'm attaching the lyx file. Please look at the preample.


Thanks a lot,  Erez

-- 
Erez Yerushalmi
PhD Student
Warwick University, UK
http://www2.warwick.ac.uk/fac/soc/economics/research/phds/3rd_year/yerushalmi


test.lyx
Description: application/lyx

Re: why doesn't \numberwithin{equation}{section} work?

[Paul A. Rubin]

Erez Yerushalmi wrote:


I've been trying to figure this out for a long time. Maybe one of you 
can help me?


I've been using  \numberwithin{equation}{section}   in the preamble for 
quite some time. 
Every time I open a new template, it takes me some time until the PDF 
output doesn't get jammed with a crash.

This must mean I don't really understand something.

When I remove \numberwithin{equation}{section}   from the preamble, pdf 
output works fine.

When I put it back in, Lyx pdf output crashes.



In Document  Settings...  Math Options, uncheck Use AMS math package 
automatically and check Use AMS math package instead, and it will work.


The \numberwithin macro is part of the AMS package, so if the AMS 
package is not loaded, you get the aforementioned LaTeX error.  The ... 
automatically setting (default) tells LyX to keep an eye out for things 
in the body of the document that require AMS math, and load the AMS 
package if and only if it finds any of them.  The test document _body_ 
did not contain anything that triggered loading of AMS math.  Either LyX 
does not look for references to AMS macros in the preamble or it doesn't 
recognize \numberwithin as one of them.  This also sometimes happens 
when someone uses an AMS macro in the body but puts it in ERT, rather 
than having LyX insert it.


/Paul

Re: listings package problem

[Nikos Alexandris]

On Fri, 2009-02-20 at 21:19 +0100, David Weenink wrote:
 L.S.,
 
 I have found the solution to my problem. The following listings configuration 
 solves my space injection problem:
 
 alsoletter={*()'0123456789.}
 basicstyle={\footnotesize\ttfamily}
 extendedchars=false
 frame=L
 upquote=false
 
 (only the first line matters for this specific problem, I think)
 
 Thanks for your responses.
 
 David
 

Thanks David, your alsoletter line helped me.
Kind regards, Nikos

Re: Books in LyX: Was How to import separate chapters into document?

[M. Edward (Ed) Borasky]

1. I've seen your web site, Steve, and I must say it's a remarkable
body of work and a great resource!

2. I think I'm going to be closer to Rich in the ebooks I write. I'll
take the defaults whenever possible. I do a lot with the
latex-beamer package, but I also use the R - LyX Sweave interface.
But you do need to know LaTeX to figure out what's broken when you do
a view PDF and get a cryptic error message out of pdftex.
Fortunately, LyX gives you a blue highlight close to where the
problem is.

3. I do find LyX / latex-beamer frustrating, though. Till Tantau, who
wrote latex-beamer and also the pgf / tkiz tool set, has made some
absolutely stunning lecture notes with these tools. But I can't for
the life of me figure out how to make my own presentations that
beautiful, even though I've read the manuals and looked at the code.
In any event, the tools *are* there.

4. There are instructions in the LyX documentation on how to do a
modular document by including sub-documents. The projects I've done
so far haven't needed that, but I'm starting a big one that will need
that.
-- 
M. Edward (Ed) Borasky
http://www.linkedin.com/in/edborasky

I've never met a happy clam. In fact, most of them were pretty steamed.

Re: listings package problem

[Nikos Alexandris]

[ I am posting a listing-related problem here instead of starting a new
thread. ]

I now realise how powerful is the listing package. I used some R code
and setting the fonts to BeraMono gives a very nice and highlighted code
in the output.

There is only one *important* problem though: usually the _backticks_
(used in *nix-like OSes to execute a command within, let's say, from
another command) appear as to have a top-left to bottom-right direction.
With my current setting (Typewriter font set to BeraMono and language
set to _bash_) the _backticks_ look very similar to the... well, the
_ticks_!

I guess it's a font-specific issue. Too bad because Bera looks great.

Any other recommendation? Kind regards, Nikos

Re: Books in LyX: Was How to import separate chapters into document?

[Anthony Campbell]

On 20 Feb 2009, Steve Litt wrote:
 On Friday 20 February 2009 09:35:27 am Anthony Campbell wrote:
  I'm just starting to prepare my fourth book with Lyx, this time using
  1.6.1 instead of 1.5.x.
 
 Anthony,
 
 What were your other three books? Are you self-publishing them, were they 
 published by others, or were they books used internally by an organization? 
 Are their descriptions/sales-brochures viewable on the Internet?
 
 What challenges did you have to overcome in order to write books with LyX, 
 and 
 in what ways was LyX a pleasant surprise? Do you have any tips you can give 
 others who write books using LyX?
 
 If you, I and a few others answer these questions, it might make life easier 
 for lots of people trying to write books in LyX.

[snip] 

The three books I have out at present are described on my website:
Homeopathy in Perspective, The Assassins of Alamut, Totality Beliefs and
the Religious Imagination. I had been using Latex for a long time before
this, including for book writing, and an reasonably au fait with it,
though far from an expert. I still write letters and shorter stuff in
Latex since I have the templates ready. I started using Lyx as an
experiment because I was finding it difficult and time-consuming to
include pictures in the text with wrap-around using Latex. 

I'm now fully persuaded of the value of Lyx for books. I would not say
there have been any major problems, apart from some issues with
including the Preface in the TOC and things like that. This list is
extremely useful and helpful in sorting them out. My policy generally is
Keep it Simple, so I mostly accept the defaults in the Book Class and
don't try to be clever.

What I particularly value in Lyx is the ability to make footnotes
easily. I regret the demise of the footnote in printed books and it's a
delight to be able to have as many as I like at the touch of a button.
Aother thing I like is that I can get an instantaneous preview of a page
which shows me exactly how it will look in the book. Making the index is
also easy.

As regards my method of working, I don't generally compose the text
directly in Lyx. I write in vim (gvim) which I'm used to and which
allows me to make large-scale changes quickly and easily. When I've got
the text more or less as I want it, I then import it into Lyx and carry
on from there.

Anthony

-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews, 
and sceptical articles)

Re: serious problems with LyX (semi-fatal crashes)

[Murat Yildizoglu]

Neither me, under Windows XP and the last stable LyX.

2009/2/21 Stefano Franchi fran...@philosophy.tamu.edu

 On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
  Vincent van Ravesteijn schreef:
   Before releasing 1.6.0 there were a number of bugs which depended on
   the location of the cursor at the time of right-clicking. Maybe this
   helps you ..
  
   I mean, there happen strange things if you right-click on a certain
   inset A.. keep the mouse down and then release it at another inset B.
   Now, the context menu of inset A is requested, but the enabling of
   items is dependent on inset B. This enabling/disabling is done via the
   getStatus mechanism, and that's exactly what I see in your backtrace.
   Maybe your tried to right-click the comment, but incidentally released
   the mouse at a neighbouring inset, which couldn't properly handle the
   next-inset-modify command and kaboom  just guessing.
  
   Vincent
 
  Bingo!
 
  1. New LyX file
  2. Insert label
  3. Insert comment
  4. Right-click on the button of the comment
  5. Hold down the mouse
  6. Release on the label
  7. Assertion.
 
 
  Vincent

 Hmm,

 if what you meant was

 4. Right click on the button of the comment
 5. Hold down the mouse
 5'. move the cursor over the label
 6. Release the right button


 then I cannot reproduce it on my system.

 S.


 __
 Stefano Franchi
 Department of Philosophy  Ph:  (979) 862-2211
 Texas AM University  Fax: (979) 845-0458
 305B Bolton Hall  fran...@philosophy.tamu.edu
 College Station, TX 77843-4237




-- 
*** NEW UNIVERSITY, NEW ADDRESS ! ***

Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http://www.vcharite.univ-mrs.fr/PP/yildi/index.html
__

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 11:21, Murat Yildizoglu wrote:

Neither me, under Windows XP and the last stable LyX.


Stefano seems to be using a debug build. In this build mode an assertion 
causes a crash each time. With a release build assertions are softer 
and, most of the time, the only visible effect is a message on the 
console or the cursor is moving weirdly.


Stefano, whenever you need to work seriously with LyX don't compile in 
full debug mode.


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
 On 21/02/2009 11:21, Murat Yildizoglu wrote:
  Neither me, under Windows XP and the last stable LyX.

 Stefano seems to be using a debug build. In this build mode an assertion
 causes a crash each time. With a release build assertions are softer
 and, most of the time, the only visible effect is a message on the
 console or the cursor is moving weirdly.

 Stefano, whenever you need to work seriously with LyX don't compile in
 full debug mode.

 Abdel.


Well, I am using a debug build now because I wanted to help tracking down the 
bug. It is frequent enough to have become a serious annoyance. But I started 
experiencing the problem (and started this thread) with the standard build. 

So what Abdel's message seems to imply is that either:

1. the assert problem is not related to the crashes I experienced originally

or 

2. I somehow was unwittingly using a debug build before recompiling Lyx with 
the debug option


I'll look into the second option, but i doubt it is the case. Which means I am 
at sea once again.


S.


__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 15:10, Stefano Franchi wrote:

On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:

On 21/02/2009 11:21, Murat Yildizoglu wrote:

Neither me, under Windows XP and the last stable LyX.

Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions are softer
and, most of the time, the only visible effect is a message on the
console or the cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX don't compile in
full debug mode.

Abdel.



Well, I am using a debug build now because I wanted to help tracking down the
bug. It is frequent enough to have become a serious annoyance.


And this is very nice of you to do that :-)


But I started
experiencing the problem (and started this thread) with the standard build.

So what Abdel's message seems to imply is that either:

1. the assert problem is not related to the crashes I experienced originally


Unless you can reproduce the last crash with a release build with the 
same symptoms I am tempted to say that the two crashes are unrelated indeed.




or

2. I somehow was unwittingly using a debug build before recompiling Lyx with
the debug option


I remember that Debian packages used to have full assertion enabled 
sometime ago, I don't know if they changed their policy since then...


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

  Before releasing 1.6.0 there were a number of bugs
 which depended on the location of the cursor at the time of
 right-clicking. Maybe this helps you ..
 I mean, there happen strange things if you right-click on a
 certain inset A.. keep the mouse down and then release it at
 another inset B. Now, the context menu of inset A is
 requested, but the enabling of items is dependent on inset
 B. This enabling/disabling is done via the getStatus
 mechanism, and that's exactly what I see in your
 backtrace. Maybe your tried to right-click the comment, but
 incidentally released the mouse at a neighbouring inset,
 which couldn't properly handle the
 next-inset-modify command and kaboom  just
 guessing.
  
  Vincent

 I have same problem that Stefano but when I writing, not when I make a mouse 
click.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: serious problems with LyX (semi-fatal crashes)

[Vincent van Ravesteijn]

Marcelo Acuña schreef:

Before releasing 1.6.0 there were a number of bugs
  

which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then release it at
another inset B. Now, the context menu of inset A is
requested, but the enabling of items is dependent on inset
B. This enabling/disabling is done via the getStatus
mechanism, and that's exactly what I see in your
backtrace. Maybe your tried to right-click the comment, but
incidentally released the mouse at a neighbouring inset,
which couldn't properly handle the
next-inset-modify command and kaboom  just
guessing.


Vincent
  


 I have same problem that Stefano but when I writing, not when I make a mouse 
click.
 Marcelo
  
Yes, .. Stefano came across another problem.. but the good news is that 
his original problem (and yours) has disappeared :).


Vincent

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

 Stefano seems to be using a debug build. In this build mode
 an assertion causes a crash each time. With a release build
 assertions are softer and, most of the time, the
 only visible effect is a message on the console or the
 cursor is moving weirdly.
 
 Stefano, whenever you need to work seriously with LyX
 don't compile in full debug mode.
 
 Abdel.

Hello,
 excuse me. I want to say that I compiled lyx without any debug mode.
 When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key and 
save my work.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 16:13, Marcelo Acuña wrote:

Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX
don't compile in full debug mode.

Abdel.


Hello,


Hi Marcelo,


  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key and 
save my work.


If you can press F2 and save your work then LyX is not frozen, it's just 
that it lost the editing focus. This happens for obscure reasons and I 
think part of this bug has been fixed recently. The next time this 
happen, just click with your mouse in the editing area to get the focus 
back.


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 08:19:16 Abdelrazak Younes wrote:
 On 21/02/2009 15:10, Stefano Franchi wrote:
  On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
  On 21/02/2009 11:21, Murat Yildizoglu wrote:
  Neither me, under Windows XP and the last stable LyX.
 
  Stefano seems to be using a debug build. In this build mode an assertion
  causes a crash each time. With a release build assertions are softer
  and, most of the time, the only visible effect is a message on the
  console or the cursor is moving weirdly.
 
  Stefano, whenever you need to work seriously with LyX don't compile in
  full debug mode.
 
  Abdel.
 
  Well, I am using a debug build now because I wanted to help tracking down
  the bug. It is frequent enough to have become a serious annoyance.

 And this is very nice of you to do that :-)

  But I started
  experiencing the problem (and started this thread) with the standard
  build.
 
  So what Abdel's message seems to imply is that either:
 
  1. the assert problem is not related to the crashes I experienced
  originally

 Unless you can reproduce the last crash with a release build with the
 same symptoms I am tempted to say that the two crashes are unrelated
 indeed.

  or
 
  2. I somehow was unwittingly using a debug build before recompiling Lyx
  with the debug option

 I remember that Debian packages used to have full assertion enabled
 sometime ago, I don't know if they changed their policy since then...

 Abdel.


That sounds right. So what's the best way to have both a debug-enabled and a 
plain vanilla lyx installed?

Can I just move the debug-enabled binary out of the source directory, make 
clean, and recompile without the debugging option? Or does the binary need 
similarly 
compiled libraries and other files? Sorry if the questions sound silly, but I 
have no idea how Lyx handles the compilation process..

Cheers,

S.




__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[rgheck]

Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a 
plain vanilla lyx installed?


  
Don't install the debug version. You can run it from where you compiled 
it. I just use a little script:



#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
/cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
if [ -f $OFFENDER ]; then rm $OFFENDER; fi


saved as lyx16 to run the debug-enabled version.

rh

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

excuse me. I want to say that I compiled lyx without
 any debug mode.
When I writing quickly, I get Lyx frozen like
 Stefano. I can press F2 key and save my work.
 
 If you can press F2 and save your work then LyX is not
 frozen, it's just that it lost the editing focus. This
 happens for obscure reasons and I think part of this bug has
 been fixed recently. The next time this happen, just click
 with your mouse in the editing area to get the focus back.
 
 Abdel.

 No. Is not a lost of editing focus. I make a lot of click over all lyx parts 
and I can´t get lyx work again. I need kill it and run again.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: newbies's difficulties

[Paul A. Rubin]

Edgar Ataíde wrote:

I am a newbie to Lyx, but I have several difficulties that I cannot
overcome. I made the complete installation of MiKTeX. I verified if
all the packages, available in MiKTeX, were installed namely Jhep.
For my surprise this package (article, book, report) is not available
in LyX, Document -Settings - Document Class. 


I have JHEP installed, but as far as I can tell it's just one document 
type (I assume article).  In any case, LyX does not come with a layout 
file for it (at least not that I can find), so you would need to find 
(or create) one.  See section 5.2 of the Customization manual.



Another aspect that I
do not understand is that the Springer styles appear in Lyx at
Document -Settings - Document Class as unavailable although they
appear as found in the Latex Configuration (I attached this file
in my mail).


Your configuration file apparently was not attached.  However, I have 
the same thing -- my configuration file lists them as found.  In point 
of fact, I don't think I have them installed (at least I cannot find 
them, nor can I find a MiKTeX package that would contain them).  I 
wonder if the LyX configuration script has a bug in it creating a false 
positive here.


In any event, if you need these classes, you can download and install 
the LaTeX packages manually from CTAN (Customization, section 5.1), run 
MiKTeX's Settings application and click Refresh FNDB (this is the 
equivalent of running texhash as described in the Customization manual), 
then load LyX, run Tools  Reconfigure, and restart LyX.  That should 
(hopefully) make the document classes available.


Another error I cannot overcome is the following:

I need to use xypic package. To train myself, I tried to make some
diagrams that are in XY-pic manual, namely the diagram that is at the
bottom of page 3. This particular diagram gives me the following
error, when I try to make the PDF output:

TeX capacity exceeded, sorry [input stack size=5000].



I'm not sure, but I think sometimes syntax errors in the source document 
 lead to that error message.  I'm attaching a LyX file containing the 
diagram.  Try it with your installation.  If the PDF output comes out 
correctly, compare the document contents to your version and see if 
perhaps you can find a discrepancy.  (View  Source is a good way to do 
this -- it will show you the LaTeX code that LyX will emit.)


/Paul


xypic_test.lyx
Description: application/lyx

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 09:46:36 rgheck wrote:
 Stefano Franchi wrote:
  So what's the best way to have both a debug-enabled and a
  plain vanilla lyx installed?

 Don't install the debug version. You can run it from where you compiled

 it. I just use a little script:
  #!/bin/bash
  USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
  if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
  /cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
  if [ -f $OFFENDER ]; then rm $OFFENDER; fi

 saved as lyx16 to run the debug-enabled version.

 rh

I didn't make myself clear, I am afraid. What I meant was:

I never installed the debuge-enabled binary, I am running ot fromt the src 
subdir in the lys-src directory. But I am not sure (see previous messages) if 
the previously installed LyX version is or is not debug-enabled. So I want to 
reinstall it from scratch. Two options:

1.  I have to redownload the sources, unpack them in another dir, conf/make/ 
install

2. I can just take the debug-enabled compiled  lyx binary out of the existing 
source tree, make clean, re-cong, / make / install


S

__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[rgheck]

Stefano Franchi wrote:

On Saturday 21 February 2009 09:46:36 rgheck wrote:
  

Stefano Franchi wrote:


So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
  

Don't install the debug version. You can run it from where you compiled

it. I just use a little script:


#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
/cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
if [ -f $OFFENDER ]; then rm $OFFENDER; fi
  

saved as lyx16 to run the debug-enabled version.

rh



I didn't make myself clear, I am afraid. What I meant was:

I never installed the debuge-enabled binary, I am running ot fromt the src 
subdir in the lys-src directory. But I am not sure (see previous messages) if 
the previously installed LyX version is or is not debug-enabled. So I want to 
reinstall it from scratch. Two options:


1.  I have to redownload the sources, unpack them in another dir, conf/make/ 
install


2. I can just take the debug-enabled compiled  lyx binary out of the existing 
source tree, make clean, re-cong, / make / install


  
Either way should do. Here's what I do: I have two separate trees, one 
called lyx-pristine, one called lyx16. The former is the non-debug build 
linked to the lyx16 svn tree; I have a cron job that keeps it updated, 
and I recompile it and install it from time to time. The other is the 
same tree but a debug build. It never gets installed but is run from the 
script.


rh

Dimensions of figure wrap float

[Hubert Christiaen]

Hello!
I find Lyx a very sophisticated program, but I am deceived by the way it 
handles figure wrap floats. Without correction, I have between 50 to 100% 
excess white space below the figure. The best way of controlling this seems 
to specify a height in lines. One could expect that if one specifies 15 lines 
as height, the systeem will take the height of the default normal line and 
multitply this by 15 and use this as height. Unfortunately, the systeem just 
seems to count the lines on the side of the image. But I have chosen to have 
an empty line between paragraphs. This empty line is not counted. Sometimes 
at the side of the image is a mathematical expression with a matrix 
multiplication in it. This is counted as 1 line althought the heigt is 4 or 5 
times a normal line height! So if I add or delete more than 2 lines, I have 
to adjust all the figures in the following pages. This is clearly 
unacceptable. There should be a way of specifying the height of a figure in 
an absolute way, which does not change over time.

One could also use '\vspace{}' with a negative number, but this is far 
less 'reactive' of precise.

Sincerely,
Hubert

-- 
Hubert Christiaen
Bloesemlaan 17
3360 Korbeek-Lo
Belgium   

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
  Stefano seems to be using a debug build. In this build mode
  an assertion causes a crash each time. With a release build
  assertions are softer and, most of the time, the
  only visible effect is a message on the console or the
  cursor is moving weirdly.
 
  Stefano, whenever you need to work seriously with LyX
  don't compile in full debug mode.
 
  Abdel.

 Hello,
  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key
 and save my work. Marcelo



That indeed was my original problem---before the more recent issues with 
asserts which are probably unrelated.
That is: Lyx is frozen in the sense that it does not accept any input 
*except* control commands (or function keys).

S.





   Yahoo! Cocina
 Recetas prácticas y comida saludable
 http://ar.mujer.yahoo.com/cocina/


__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas AM University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 17:49, Stefano Franchi wrote:

On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:

Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are softer and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX
don't compile in full debug mode.

Abdel.

Hello,
  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key
and save my work. Marcelo




That indeed was my original problem---before the more recent issues with
asserts which are probably unrelated.
That is: Lyx is frozen in the sense that it does not accept any input
*except* control commands (or function keys).


That is really weird indeed...

Abdel.

Re: Books in LyX: Was How to import separate chapters into document?

[Abdelrazak Younes]

On 21/02/2009 09:53, Anthony Campbell wrote:

On 20 Feb 2009, Steve Litt wrote:

On Friday 20 February 2009 09:35:27 am Anthony Campbell wrote:

I'm just starting to prepare my fourth book with Lyx, this time using
1.6.1 instead of 1.5.x.

Anthony,

What were your other three books? Are you self-publishing them, were they
published by others, or were they books used internally by an organization?
Are their descriptions/sales-brochures viewable on the Internet?

What challenges did you have to overcome in order to write books with LyX, and
in what ways was LyX a pleasant surprise? Do you have any tips you can give
others who write books using LyX?

If you, I and a few others answer these questions, it might make life easier
for lots of people trying to write books in LyX.


[snip]

The three books I have out at present are described on my website:
Homeopathy in Perspective, The Assassins of Alamut,


off topic/
I've skimmed over the summary, looks very interesting. There's another 
famous book that talk about this sect: Samarcand by Hamid Malouf.
This book is a romanced biography of Omar Khayam, the most famous arabic 
poet. As far from I remember from this excellent book, the word 
Assassin come from Assass Iyoun i.e. the fidels of Iyoun, or 
something like that. This book is a must read :-)

off topic/

Abdel.

why doesn't \numberwithin{equation}{section} work?

[Erez Yerushalmi]

Hi All,

I've been trying to figure this out for a long time. Maybe one of you can
help me?

I've been using  \numberwithin{equation}{section}   in the preamble for
quite some time.
Every time I open a new template, it takes me some time until the PDF output
doesn't get jammed with a crash.
This must mean I don't really understand something.

When I remove \numberwithin{equation}{section}   from the preamble, pdf
output works fine.
When I put it back in, Lyx pdf output crashes.

My errors are the following:

error Undefined control sequence, with description

\numberwithin{equation}{section} % #section.#equation

The control sequence at the end of the top line

of your error message was never \def'ed. If you have

misspelled it (e.g., `\hobx'), type `I' and the correct

spelling (e.g., `I\hbox'). Otherwise just continue,

and I'll forget about whatever was undefined.


second error: LaTeX Error: Missing \begin{document}.


with description:

\numberwithin{equation}{section} % #section.#equation

You're in trouble here. Try typing return to proceed.

If that doesn't work, type X return to quit.


I'm attaching the lyx file. Please look at the preample.


Thanks a lot,  Erez

-- 
Erez Yerushalmi
PhD Student
Warwick University, UK
http://www2.warwick.ac.uk/fac/soc/economics/research/phds/3rd_year/yerushalmi


test.lyx
Description: application/lyx

Re: why doesn't \numberwithin{equation}{section} work?

[Paul A. Rubin]

Erez Yerushalmi wrote:


I've been trying to figure this out for a long time. Maybe one of you 
can help me?


I've been using  \numberwithin{equation}{section}   in the preamble for 
quite some time. 
Every time I open a new template, it takes me some time until the PDF 
output doesn't get jammed with a crash.

This must mean I don't really understand something.

When I remove \numberwithin{equation}{section}   from the preamble, pdf 
output works fine.

When I put it back in, Lyx pdf output crashes.



In Document  Settings...  Math Options, uncheck Use AMS math package 
automatically and check Use AMS math package instead, and it will work.


The \numberwithin macro is part of the AMS package, so if the AMS 
package is not loaded, you get the aforementioned LaTeX error.  The ... 
automatically setting (default) tells LyX to keep an eye out for things 
in the body of the document that require AMS math, and load the AMS 
package if and only if it finds any of them.  The test document _body_ 
did not contain anything that triggered loading of AMS math.  Either LyX 
does not look for references to AMS macros in the preamble or it doesn't 
recognize \numberwithin as one of them.  This also sometimes happens 
when someone uses an AMS macro in the body but puts it in ERT, rather 
than having LyX insert it.


/Paul

Re: listings package problem

[Nikos Alexandris]

On Fri, 2009-02-20 at 21:19 +0100, David Weenink wrote:
 L.S.,
 
 I have found the solution to my problem. The following listings configuration 
 solves my space injection problem:
 
 alsoletter={*()'0123456789.}
 basicstyle={\footnotesize\ttfamily}
 extendedchars=false
 frame=L
 upquote=false
 
 (only the first line matters for this specific problem, I think)
 
 Thanks for your responses.
 
 David
 

Thanks David, your alsoletter line helped me.
Kind regards, Nikos

Re: Books in LyX: Was How to import separate chapters into document?

[M. Edward (Ed) Borasky]

1. I've seen your web site, Steve, and I must say it's a remarkable
body of work and a great resource!

2. I think I'm going to be closer to Rich in the ebooks I write. I'll
take the defaults whenever possible. I do a lot with the
latex-beamer package, but I also use the R - LyX Sweave interface.
But you do need to know LaTeX to figure out what's broken when you do
a view PDF and get a cryptic error message out of pdftex.
Fortunately, LyX gives you a blue highlight close to where the
problem is.

3. I do find LyX / latex-beamer frustrating, though. Till Tantau, who
wrote latex-beamer and also the pgf / tkiz tool set, has made some
absolutely stunning lecture notes with these tools. But I can't for
the life of me figure out how to make my own presentations that
beautiful, even though I've read the manuals and looked at the code.
In any event, the tools *are* there.

4. There are instructions in the LyX documentation on how to do a
modular document by including sub-documents. The projects I've done
so far haven't needed that, but I'm starting a big one that will need
that.
-- 
M. Edward (Ed) Borasky
http://www.linkedin.com/in/edborasky

I've never met a happy clam. In fact, most of them were pretty steamed.

Re: listings package problem

[Nikos Alexandris]

[ I am posting a listing-related problem here instead of starting a new
thread. ]

I now realise how powerful is the listing package. I used some R code
and setting the fonts to BeraMono gives a very nice and highlighted code
in the output.

There is only one *important* problem though: usually the _backticks_
(used in *nix-like OSes to execute a command within, let's say, from
another command) appear as to have a top-left to bottom-right direction.
With my current setting (Typewriter font set to BeraMono and language
set to _bash_) the _backticks_ look very similar to the... well, the
_ticks_!

I guess it's a font-specific issue. Too bad because Bera looks great.

Any other recommendation? Kind regards, Nikos

Re: Books in LyX: Was How to import separate chapters into document?

[Anthony Campbell]

On 20 Feb 2009, Steve Litt wrote:
> On Friday 20 February 2009 09:35:27 am Anthony Campbell wrote:
> > I'm just starting to prepare my fourth book with Lyx, this time using
> > 1.6.1 instead of 1.5.x.
> 
> Anthony,
> 
> What were your other three books? Are you self-publishing them, were they 
> published by others, or were they books used internally by an organization? 
> Are their descriptions/sales-brochures viewable on the Internet?
> 
> What challenges did you have to overcome in order to write books with LyX, 
> and 
> in what ways was LyX a pleasant surprise? Do you have any tips you can give 
> others who write books using LyX?
> 
> If you, I and a few others answer these questions, it might make life easier 
> for lots of people trying to write books in LyX.

[snip] 

The three books I have out at present are described on my website:
Homeopathy in Perspective, The Assassins of Alamut, Totality Beliefs and
the Religious Imagination. I had been using Latex for a long time before
this, including for book writing, and an reasonably au fait with it,
though far from an expert. I still write letters and shorter stuff in
Latex since I have the templates ready. I started using Lyx as an
experiment because I was finding it difficult and time-consuming to
include pictures in the text with wrap-around using Latex. 

I'm now fully persuaded of the value of Lyx for books. I would not say
there have been any major problems, apart from some issues with
including the Preface in the TOC and things like that. This list is
extremely useful and helpful in sorting them out. My policy generally is
Keep it Simple, so I mostly accept the defaults in the Book Class and
don't try to be clever.

What I particularly value in Lyx is the ability to make footnotes
easily. I regret the demise of the footnote in printed books and it's a
delight to be able to have as many as I like at the touch of a button.
Aother thing I like is that I can get an instantaneous preview of a page
which shows me exactly how it will look in the book. Making the index is
also easy.

As regards my method of working, I don't generally compose the text
directly in Lyx. I write in vim (gvim) which I'm used to and which
allows me to make large-scale changes quickly and easily. When I've got
the text more or less as I want it, I then import it into Lyx and carry
on from there.

Anthony

-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews, 
and sceptical articles)

Re: serious problems with LyX (semi-fatal crashes)

[Murat Yildizoglu]

Neither me, under Windows XP and the last stable LyX.

2009/2/21 Stefano Franchi 

> On Friday 20 February 2009 17:49:35 Vincent van Ravesteijn wrote:
> > Vincent van Ravesteijn schreef:
> > >> Before releasing 1.6.0 there were a number of bugs which depended on
> > >> the location of the cursor at the time of right-clicking. Maybe this
> > >> helps you ..
> > >
> > > I mean, there happen strange things if you right-click on a certain
> > > inset A.. keep the mouse down and then release it at another inset B.
> > > Now, the context menu of inset A is requested, but the enabling of
> > > items is dependent on inset B. This enabling/disabling is done via the
> > > getStatus mechanism, and that's exactly what I see in your backtrace.
> > > Maybe your tried to right-click the comment, but incidentally released
> > > the mouse at a neighbouring inset, which couldn't properly handle the
> > > "next-inset-modify" command and kaboom  just guessing.
> > >
> > >> Vincent
> >
> > Bingo!
> >
> > 1. New LyX file
> > 2. Insert label
> > 3. Insert comment
> > 4. Right-click on the button of the comment
> > 5. Hold down the mouse
> > 6. Release on the label
> > 7. Assertion.
> >
> >
> > Vincent
>
> Hmm,
>
> if what you meant was
>
> 4. Right click on the button of the comment
> 5. Hold down the mouse
> 5'. move the cursor over the label
> 6. Release the right button
>
>
> then I cannot reproduce it on my system.
>
> S.
>
>
> __
> Stefano Franchi
> Department of Philosophy  Ph:  (979) 862-2211
> Texas A University  Fax: (979) 845-0458
> 305B Bolton Hall  fran...@philosophy.tamu.edu
> College Station, TX 77843-4237
>
>


-- 
*** NEW UNIVERSITY, NEW ADDRESS ! ***

Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http://www.vcharite.univ-mrs.fr/PP/yildi/index.html
__

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 11:21, Murat Yildizoglu wrote:

Neither me, under Windows XP and the last stable LyX.


Stefano seems to be using a debug build. In this build mode an assertion 
causes a crash each time. With a release build assertions are "softer" 
and, most of the time, the only visible effect is a message on the 
console or the cursor is moving weirdly.


Stefano, whenever you need to work seriously with LyX don't compile in 
full debug mode.


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
> On 21/02/2009 11:21, Murat Yildizoglu wrote:
> > Neither me, under Windows XP and the last stable LyX.
>
> Stefano seems to be using a debug build. In this build mode an assertion
> causes a crash each time. With a release build assertions are "softer"
> and, most of the time, the only visible effect is a message on the
> console or the cursor is moving weirdly.
>
> Stefano, whenever you need to work seriously with LyX don't compile in
> full debug mode.
>
> Abdel.


Well, I am using a debug build now because I wanted to help tracking down the 
bug. It is frequent enough to have become a serious annoyance. But I started 
experiencing the problem (and started this thread) with the standard build. 

So what Abdel's message seems to imply is that either:

1. the assert problem is not related to the crashes I experienced originally

or 

2. I somehow was unwittingly using a debug build before recompiling Lyx with 
the debug option


I'll look into the second option, but i doubt it is the case. Which means I am 
at sea once again.


S.


__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas A University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 15:10, Stefano Franchi wrote:

On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:

On 21/02/2009 11:21, Murat Yildizoglu wrote:

Neither me, under Windows XP and the last stable LyX.

Stefano seems to be using a debug build. In this build mode an assertion
causes a crash each time. With a release build assertions are "softer"
and, most of the time, the only visible effect is a message on the
console or the cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX don't compile in
full debug mode.

Abdel.



Well, I am using a debug build now because I wanted to help tracking down the
bug. It is frequent enough to have become a serious annoyance.


And this is very nice of you to do that :-)


But I started
experiencing the problem (and started this thread) with the standard build.

So what Abdel's message seems to imply is that either:

1. the assert problem is not related to the crashes I experienced originally


Unless you can reproduce the last crash with a release build with the 
same symptoms I am tempted to say that the two crashes are unrelated indeed.




or

2. I somehow was unwittingly using a debug build before recompiling Lyx with
the debug option


I remember that Debian packages used to have full assertion enabled 
sometime ago, I don't know if they changed their policy since then...


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

> > Before releasing 1.6.0 there were a number of bugs
> which depended on the location of the cursor at the time of
> right-clicking. Maybe this helps you ..
> I mean, there happen strange things if you right-click on a
> certain inset A.. keep the mouse down and then release it at
> another inset B. Now, the context menu of inset A is
> requested, but the enabling of items is dependent on inset
> B. This enabling/disabling is done via the getStatus
> mechanism, and that's exactly what I see in your
> backtrace. Maybe your tried to right-click the comment, but
> incidentally released the mouse at a neighbouring inset,
> which couldn't properly handle the
> "next-inset-modify" command and kaboom  just
> guessing.
> > 
> > Vincent

 I have same problem that Stefano but when I writing, not when I make a mouse 
click.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: serious problems with LyX (semi-fatal crashes)

[Vincent van Ravesteijn]

Marcelo Acuña schreef:

Before releasing 1.6.0 there were a number of bugs
  

which depended on the location of the cursor at the time of
right-clicking. Maybe this helps you ..
I mean, there happen strange things if you right-click on a
certain inset A.. keep the mouse down and then release it at
another inset B. Now, the context menu of inset A is
requested, but the enabling of items is dependent on inset
B. This enabling/disabling is done via the getStatus
mechanism, and that's exactly what I see in your
backtrace. Maybe your tried to right-click the comment, but
incidentally released the mouse at a neighbouring inset,
which couldn't properly handle the
"next-inset-modify" command and kaboom  just
guessing.


Vincent
  


 I have same problem that Stefano but when I writing, not when I make a mouse 
click.
 Marcelo
  
Yes, .. Stefano came across another problem.. but the good news is that 
his original problem (and yours) has disappeared :).


Vincent

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

> Stefano seems to be using a debug build. In this build mode
> an assertion causes a crash each time. With a release build
> assertions are "softer" and, most of the time, the
> only visible effect is a message on the console or the
> cursor is moving weirdly.
> 
> Stefano, whenever you need to work seriously with LyX
> don't compile in full debug mode.
> 
> Abdel.

Hello,
 excuse me. I want to say that I compiled lyx without any debug mode.
 When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key and 
save my work.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 16:13, Marcelo Acuña wrote:

Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are "softer" and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX
don't compile in full debug mode.

Abdel.


Hello,


Hi Marcelo,


  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key and 
save my work.


If you can press F2 and save your work then LyX is not frozen, it's just 
that it lost the editing focus. This happens for obscure reasons and I 
think part of this bug has been fixed recently. The next time this 
happen, just click with your mouse in the editing area to get the focus 
back.


Abdel.

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 08:19:16 Abdelrazak Younes wrote:
> On 21/02/2009 15:10, Stefano Franchi wrote:
> > On Saturday 21 February 2009 08:00:12 Abdelrazak Younes wrote:
> >> On 21/02/2009 11:21, Murat Yildizoglu wrote:
> >>> Neither me, under Windows XP and the last stable LyX.
> >>
> >> Stefano seems to be using a debug build. In this build mode an assertion
> >> causes a crash each time. With a release build assertions are "softer"
> >> and, most of the time, the only visible effect is a message on the
> >> console or the cursor is moving weirdly.
> >>
> >> Stefano, whenever you need to work seriously with LyX don't compile in
> >> full debug mode.
> >>
> >> Abdel.
> >
> > Well, I am using a debug build now because I wanted to help tracking down
> > the bug. It is frequent enough to have become a serious annoyance.
>
> And this is very nice of you to do that :-)
>
> > But I started
> > experiencing the problem (and started this thread) with the standard
> > build.
> >
> > So what Abdel's message seems to imply is that either:
> >
> > 1. the assert problem is not related to the crashes I experienced
> > originally
>
> Unless you can reproduce the last crash with a release build with the
> same symptoms I am tempted to say that the two crashes are unrelated
> indeed.
>
> > or
> >
> > 2. I somehow was unwittingly using a debug build before recompiling Lyx
> > with the debug option
>
> I remember that Debian packages used to have full assertion enabled
> sometime ago, I don't know if they changed their policy since then...
>
> Abdel.


That sounds right. So what's the best way to have both a debug-enabled and a 
plain vanilla lyx installed?

Can I just move the debug-enabled binary out of the source directory, make 
clean, and recompile without the debugging option? Or does the binary need 
similarly 
compiled libraries and other files? Sorry if the questions sound silly, but I 
have no idea how Lyx handles the compilation process..

Cheers,

S.




__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas A University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[rgheck]

Stefano Franchi wrote:
So what's the best way to have both a debug-enabled and a 
plain vanilla lyx installed?


  
Don't install the debug version. You can run it from where you compiled 
it. I just use a little script:



#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
/cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
if [ -f $OFFENDER ]; then rm $OFFENDER; fi


saved as "lyx16" to run the debug-enabled version.

rh

Re: serious problems with LyX (semi-fatal crashes)

[Marcelo Acuña]

> >   excuse me. I want to say that I compiled lyx without
> any debug mode.
> >   When I writing quickly, I get Lyx frozen like
> Stefano. I can press F2 key and save my work.
> 
> If you can press F2 and save your work then LyX is not
> frozen, it's just that it lost the editing focus. This
> happens for obscure reasons and I think part of this bug has
> been fixed recently. The next time this happen, just click
> with your mouse in the editing area to get the focus back.
> 
> Abdel.

 No. Is not a lost of editing focus. I make a lot of click over all lyx parts 
and I can´t get lyx work again. I need kill it and run again.
 Marcelo


  Yahoo! Cocina
Recetas prácticas y comida saludable
http://ar.mujer.yahoo.com/cocina/

Re: newbies's difficulties

[Paul A. Rubin]

Edgar Ataíde wrote:

I am a newbie to Lyx, but I have several difficulties that I cannot
overcome. I made the complete installation of MiKTeX. I verified if
all the packages, available in MiKTeX, were installed namely Jhep.
For my surprise this package (article, book, report) is not available
in LyX, Document ->Settings -> Document Class. 


I have JHEP installed, but as far as I can tell it's just one document 
type (I assume article).  In any case, LyX does not come with a layout 
file for it (at least not that I can find), so you would need to find 
(or create) one.  See section 5.2 of the Customization manual.



Another aspect that I
do not understand is that the Springer styles appear in Lyx at
Document ->Settings -> Document Class as unavailable although they
appear as "found" in the "Latex Configuration" (I attached this file
in my mail).


Your configuration file apparently was not attached.  However, I have 
the same thing -- my configuration file lists them as found.  In point 
of fact, I don't think I have them installed (at least I cannot find 
them, nor can I find a MiKTeX package that would contain them).  I 
wonder if the LyX configuration script has a bug in it creating a "false 
positive" here.


In any event, if you need these classes, you can download and install 
the LaTeX packages manually from CTAN (Customization, section 5.1), run 
MiKTeX's Settings application and click "Refresh FNDB" (this is the 
equivalent of running texhash as described in the Customization manual), 
then load LyX, run Tools > Reconfigure, and restart LyX.  That should 
(hopefully) make the document classes available.


Another error I cannot overcome is the following:

I need to use xypic package. To train myself, I tried to make some
diagrams that are in XY-pic manual, namely the diagram that is at the
bottom of page 3. This particular diagram gives me the following
error, when I try to make the PDF output:

"TeX capacity exceeded, sorry [input stack size=5000]".



I'm not sure, but I think sometimes syntax errors in the source document 
 lead to that error message.  I'm attaching a LyX file containing the 
diagram.  Try it with your installation.  If the PDF output comes out 
correctly, compare the document contents to your version and see if 
perhaps you can find a discrepancy.  (View > Source is a good way to do 
this -- it will show you the LaTeX code that LyX will emit.)


/Paul


xypic_test.lyx
Description: application/lyx

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 09:46:36 rgheck wrote:
> Stefano Franchi wrote:
> > So what's the best way to have both a debug-enabled and a
> > plain vanilla lyx installed?
>
> Don't install the debug version. You can run it from where you compiled
>
> it. I just use a little script:
> > #!/bin/bash
> > USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
> > if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
> > /cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
> > if [ -f $OFFENDER ]; then rm $OFFENDER; fi
>
> saved as "lyx16" to run the debug-enabled version.
>
> rh

I didn't make myself clear, I am afraid. What I meant was:

I never installed the debuge-enabled binary, I am running ot fromt the src 
subdir in the lys-src directory. But I am not sure (see previous messages) if 
the previously installed LyX version is or is not debug-enabled. So I want to 
reinstall it from scratch. Two options:

1.  I have to redownload the sources, unpack them in another dir, conf/make/ 
install

2. I can just take the debug-enabled compiled  lyx binary out of the existing 
source tree, make clean, re-cong, / make / install


S

__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas A University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[rgheck]

Stefano Franchi wrote:

On Saturday 21 February 2009 09:46:36 rgheck wrote:
  

Stefano Franchi wrote:


So what's the best way to have both a debug-enabled and a
plain vanilla lyx installed?
  

Don't install the debug version. You can run it from where you compiled

it. I just use a little script:


#!/bin/bash
USERDIR=/home/rgheck/dev/lyxdirs/lyxbranch/
if [ -e $USERDIR/.lyxpipe.in ]; then rm $USERDIR/.lyxpipe.*; fi
/cvs/lyx16/src/lyx -userdir $USERDIR $*  -geometry 1024x1024+100+100;
if [ -f $OFFENDER ]; then rm $OFFENDER; fi
  

saved as "lyx16" to run the debug-enabled version.

rh



I didn't make myself clear, I am afraid. What I meant was:

I never installed the debuge-enabled binary, I am running ot fromt the src 
subdir in the lys-src directory. But I am not sure (see previous messages) if 
the previously installed LyX version is or is not debug-enabled. So I want to 
reinstall it from scratch. Two options:


1.  I have to redownload the sources, unpack them in another dir, conf/make/ 
install


2. I can just take the debug-enabled compiled  lyx binary out of the existing 
source tree, make clean, re-cong, / make / install


  
Either way should do. Here's what I do: I have two separate trees, one 
called lyx-pristine, one called lyx16. The former is the non-debug build 
linked to the lyx16 svn tree; I have a cron job that keeps it updated, 
and I recompile it and install it from time to time. The other is the 
same tree but a debug build. It never gets installed but is run from the 
script.


rh

Dimensions of figure wrap float

[Hubert Christiaen]

Hello!
I find Lyx a very sophisticated program, but I am deceived by the way it 
handles figure wrap floats. Without correction, I have between 50 to 100% 
excess white space below the figure. The best way of controlling this seems 
to specify a height in lines. One could expect that if one specifies 15 lines 
as height, the systeem will take the height of the default normal line and 
multitply this by 15 and use this as height. Unfortunately, the systeem just 
seems to count the lines on the side of the image. But I have chosen to have 
an empty line between paragraphs. This empty line is not counted. Sometimes 
at the side of the image is a mathematical expression with a matrix 
multiplication in it. This is counted as 1 line althought the heigt is 4 or 5 
times a normal line height! So if I add or delete more than 2 lines, I have 
to adjust all the figures in the following pages. This is clearly 
unacceptable. There should be a way of specifying the height of a figure in 
an absolute way, which does not change over time.

One could also use '\vspace{}' with a negative number, but this is far 
less 'reactive' of precise.

Sincerely,
Hubert

-- 
Hubert Christiaen
Bloesemlaan 17
3360 Korbeek-Lo
Belgium   

Re: serious problems with LyX (semi-fatal crashes)

[Stefano Franchi]

On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:
> > Stefano seems to be using a debug build. In this build mode
> > an assertion causes a crash each time. With a release build
> > assertions are "softer" and, most of the time, the
> > only visible effect is a message on the console or the
> > cursor is moving weirdly.
> >
> > Stefano, whenever you need to work seriously with LyX
> > don't compile in full debug mode.
> >
> > Abdel.
>
> Hello,
>  excuse me. I want to say that I compiled lyx without any debug mode.
>  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key
> and save my work. Marcelo
>
>

That indeed was my original problem---before the more recent issues with 
asserts which are probably unrelated.
That is: Lyx is "frozen" in the sense that it does not accept any input 
*except* control commands (or function keys).

S.





>   Yahoo! Cocina
> Recetas prácticas y comida saludable
> http://ar.mujer.yahoo.com/cocina/


__
Stefano Franchi
Department of Philosophy          Ph:  (979) 862-2211
Texas A University  Fax: (979) 845-0458
305B Bolton Hall  fran...@philosophy.tamu.edu
College Station, TX 77843-4237

Re: serious problems with LyX (semi-fatal crashes)

[Abdelrazak Younes]

On 21/02/2009 17:49, Stefano Franchi wrote:

On Saturday 21 February 2009 09:13:54 Marcelo Acuña wrote:

Stefano seems to be using a debug build. In this build mode
an assertion causes a crash each time. With a release build
assertions are "softer" and, most of the time, the
only visible effect is a message on the console or the
cursor is moving weirdly.

Stefano, whenever you need to work seriously with LyX
don't compile in full debug mode.

Abdel.

Hello,
  excuse me. I want to say that I compiled lyx without any debug mode.
  When I writing quickly, I get Lyx frozen like Stefano. I can press F2 key
and save my work. Marcelo




That indeed was my original problem---before the more recent issues with
asserts which are probably unrelated.
That is: Lyx is "frozen" in the sense that it does not accept any input
*except* control commands (or function keys).


That is really weird indeed...

Abdel.

Re: Books in LyX: Was How to import separate chapters into document?

[Abdelrazak Younes]

On 21/02/2009 09:53, Anthony Campbell wrote:

On 20 Feb 2009, Steve Litt wrote:

On Friday 20 February 2009 09:35:27 am Anthony Campbell wrote:

I'm just starting to prepare my fourth book with Lyx, this time using
1.6.1 instead of 1.5.x.

Anthony,

What were your other three books? Are you self-publishing them, were they
published by others, or were they books used internally by an organization?
Are their descriptions/sales-brochures viewable on the Internet?

What challenges did you have to overcome in order to write books with LyX, and
in what ways was LyX a pleasant surprise? Do you have any tips you can give
others who write books using LyX?

If you, I and a few others answer these questions, it might make life easier
for lots of people trying to write books in LyX.


[snip]

The three books I have out at present are described on my website:
Homeopathy in Perspective, The Assassins of Alamut,



I've skimmed over the summary, looks very interesting. There's another 
famous book that talk about this sect: "Samarcand" by Hamid Malouf.
This book is a romanced biography of Omar Khayam, the most famous arabic 
poet. As far from I remember from this excellent book, the word 
"Assassin" come from "Assass Iyoun" i.e. the fidels of Iyoun, or 
something like that. This book is a must read :-)



Abdel.

why doesn't \numberwithin{equation}{section} work?

[Erez Yerushalmi]

Hi All,

I've been trying to figure this out for a long time. Maybe one of you can
help me?

I've been using  \numberwithin{equation}{section}   in the preamble for
quite some time.
Every time I open a new template, it takes me some time until the PDF output
doesn't get jammed with a crash.
This must mean I don't really understand something.

When I remove \numberwithin{equation}{section}   from the preamble, pdf
output works fine.
When I put it back in, Lyx pdf output crashes.

My errors are the following:

error Undefined control sequence, with description

\numberwithin{equation}{section} % #section.#equation

The control sequence at the end of the top line

of your error message was never \def'ed. If you have

misspelled it (e.g., `\hobx'), type `I' and the correct

spelling (e.g., `I\hbox'). Otherwise just continue,

and I'll forget about whatever was undefined.


second error: LaTeX Error: Missing \begin{document}.


with description:

\numberwithin{equation}{section} % #section.#equation

You're in trouble here. Try typing  to proceed.

If that doesn't work, type X  to quit.


I'm attaching the lyx file. Please look at the preample.


Thanks a lot,  Erez

-- 
Erez Yerushalmi
PhD Student
Warwick University, UK
http://www2.warwick.ac.uk/fac/soc/economics/research/phds/3rd_year/yerushalmi


test.lyx
Description: application/lyx

Re: why doesn't \numberwithin{equation}{section} work?

[Paul A. Rubin]

Erez Yerushalmi wrote:


I've been trying to figure this out for a long time. Maybe one of you 
can help me?


I've been using  \numberwithin{equation}{section}   in the preamble for 
quite some time. 
Every time I open a new template, it takes me some time until the PDF 
output doesn't get jammed with a crash.

This must mean I don't really understand something.

When I remove \numberwithin{equation}{section}   from the preamble, pdf 
output works fine.

When I put it back in, Lyx pdf output crashes.



In Document > Settings... > Math Options, uncheck "Use AMS math package 
automatically" and check "Use AMS math package" instead, and it will work.


The \numberwithin macro is part of the AMS package, so if the AMS 
package is not loaded, you get the aforementioned LaTeX error.  The "... 
automatically" setting (default) tells LyX to keep an eye out for things 
in the body of the document that require AMS math, and load the AMS 
package if and only if it finds any of them.  The test document _body_ 
did not contain anything that triggered loading of AMS math.  Either LyX 
does not look for references to AMS macros in the preamble or it doesn't 
recognize \numberwithin as one of them.  This also sometimes happens 
when someone uses an AMS macro in the body but puts it in ERT, rather 
than having LyX insert it.


/Paul

Re: listings package problem

[Nikos Alexandris]

On Fri, 2009-02-20 at 21:19 +0100, David Weenink wrote:
> L.S.,
> 
> I have found the solution to my problem. The following listings configuration 
> solves my space injection problem:
> 
> alsoletter={*()"'0123456789.}
> basicstyle={\footnotesize\ttfamily}
> extendedchars=false
> frame=L
> upquote=false
> 
> (only the first line matters for this specific problem, I think)
> 
> Thanks for your responses.
> 
> David
> 

Thanks David, your "alsoletter" line helped me.
Kind regards, Nikos

Re: Books in LyX: Was How to import separate chapters into document?

[M. Edward (Ed) Borasky]

1. I've seen your web site, Steve, and I must say it's a remarkable
body of work and a great resource!

2. I think I'm going to be closer to Rich in the ebooks I write. I'll
take the defaults whenever possible. I do a lot with the
"latex-beamer" package, but I also use the R - LyX "Sweave" interface.
But you do need to know LaTeX to figure out what's broken when you do
a "view PDF" and get a cryptic error message out of "pdftex".
Fortunately, LyX gives you a blue highlight "close" to where the
problem is.

3. I do find LyX / latex-beamer frustrating, though. Till Tantau, who
wrote "latex-beamer" and also the "pgf / tkiz" tool set, has made some
absolutely stunning lecture notes with these tools. But I can't for
the life of me figure out how to make my own presentations that
beautiful, even though I've read the manuals and looked at the code.
In any event, the tools *are* there.

4. There are instructions in the LyX documentation on how to do a
"modular" document by including sub-documents. The projects I've done
so far haven't needed that, but I'm starting a big one that will need
that.
-- 
M. Edward (Ed) Borasky
http://www.linkedin.com/in/edborasky

I've never met a happy clam. In fact, most of them were pretty steamed.

Re: listings package problem

[Nikos Alexandris]

[ I am posting a listing-related problem here instead of starting a new
thread. ]

I now realise how powerful is the listing package. I used some R code
and setting the fonts to BeraMono gives a very nice and highlighted code
in the output.

There is only one *important* problem though: usually the _backticks_
(used in *nix-like OSes to execute a command within, let's say, from
another command) appear as to have a top-left to bottom-right direction.
With my current setting (Typewriter font set to BeraMono and language
set to _bash_) the _backticks_ look very similar to the... well, the
_ticks_!

I guess it's a font-specific issue. Too bad because Bera looks great.

Any other recommendation? Kind regards, Nikos