Re: import lyx (1.6.1) file

[Wolfgang Engelmann]

Am Monday 27 April 2009 15:00:38 schrieb Vincent van Ravesteijn - TNW:
> >> >How do I import a lyx (1.6.1) file, in order to append it to an
> >> >existing one (also 1.6.1) in which I am currently working. I
>
> remember
>
> >> >to have it in the 1.5 series, but now under File>import.
> >>
> >> Insert->File->LyX Document..
> >>
> >> Vincent
> >
> >Thanks, Vincent,
> >
> >But I still did not catch it. I am in Lyx file1 at the end. I would
> >like to add the content of Lyx file2. If I follow your advice
> >Insert->File->LyX Document it does not give me a selection possibility
> >(for file2) but inserts something I might have had in the buffer.
>
> It should have inserted the contents of file2. (Did you save file2
> before doing this ?)

Yes I did. I have only file1 and file2 selected, but choosing insert does not 
insert file2 if I am at the end of file1.

Therefore I used copy/paste, as you suggested. I was afraid to do that, 
because selecting a long text usually/often crashes; but I found the 
select all 
under bearbeiten
and copied that. It worked.

Thanks

RE: import lyx (1.6.1) file

[Vincent van Ravesteijn - TNW]

 
>> >How do I import a lyx (1.6.1) file, in order to append it to an 
>> >existing one (also 1.6.1) in which I am currently working. I
remember 
>> >to have it in the 1.5 series, but now under File>import.
>>
>> Insert->File->LyX Document..
>>
>> Vincent
>
>Thanks, Vincent,
>
>But I still did not catch it. I am in Lyx file1 at the end. I would
>like to add the content of Lyx file2. If I follow your advice
>Insert->File->LyX Document it does not give me a selection possibility
>(for file2) but inserts something I might have had in the buffer. 

It should have inserted the contents of file2. (Did you save file2
before doing this ?)

>No luck either, if I select the content of file2 first (bearbeiten > 
>select all) and use your proposal.
>
>I am doing something stupid, I guess. 

If you have both files open you can always select everything and use
copy and paste to paste it in the other document. 

>Wolfgang

Vincent

Re: import lyx (1.6.1) file

[Wolfgang Engelmann]

Am Monday 27 April 2009 14:05:42 schrieb Vincent van Ravesteijn - TNW:
> >How do I import a lyx (1.6.1) file, in order to append it to an
> >existing one (also 1.6.1) in which I am currently working. I
> >remember to have it in the 1.5 series, but now under File>import.
>
> Insert->File->LyX Document..
>
> Vincent

Thanks, Vincent,

but I still did not catch it.
I am in Lyx file1 at the end. I would like to add the content of Lyx file2.
If I follow your advice
Insert->File->LyX Document
it does not give me a selection possibility (for file2) but inserts something 
I might have had in the buffer. 

No luck either, if I select the content of file2 first (bearbeiten > select 
all) and use your proposal.

I am doing something stupid, I guess. 

Wolfgang

RE: import lyx (1.6.1) file

[Vincent van Ravesteijn - TNW]

>How do I import a lyx (1.6.1) file, in order to append it to an
>existing one (also 1.6.1) in which I am currently working. I
>remember to have it in the 1.5 series, but now under File>import.

Insert->File->LyX Document..

Vincent

import lyx (1.6.1) file

[Wolfgang Engelmann]

How do I import a lyx (1.6.1) file, in order to append it to an existing one 
(also 1.6.1) in which I am currently working. I remember to have it in the 
1.5 series, but now under 
File>import 
I find only 3 different CJK, HTML, Latex, NoWeb, simple text and table.
Do I have to set it somewhere? 
I did not find it in the help menues (but might have overseen it)

Wolfgang

RE: Where is the autosave in LyX 1.6.1 (Windows)?

[Vincent van Ravesteijn - TNW]

> But auto-backups then are in the same directory - you haven't search
for them.

The auto-backups are rather hard to find for unnamed docs. This will be
fixed in 1.6.3.

Vincent

Re: Where is the autosave in LyX 1.6.1 (Windows)?

[Manveru]

2009/4/2 TJ McLaughlin :
>
> Today, for the second time, I was working on something in LyX and managed to
> crash it, losing my document. I had not yet saved the file (so the name in
> the title bar was "newfile1.lyx").
> Both LyX itself and the documentation say that there is an "auto-save"
> feature to create emergency backups. (LyX said before crashing that when it
> resumed, I would be prompted to open my auto-saved document--this did not
> happen.)
>
> I worked on the document for a good 40 minutes so the auto-save should have
> worked, right? /Does/ it work on the Windows version of LyX and if so, where
> does it put the backup files? I can't find them anywhere. Can anyone help me
> out?

It is really good practice, to type document title and then save it
under name in directory you want. I almost always do that as I often
leave editor (not LyX only) opened for very long periods of time doing
something else. But auto-backups then are in the same directory - you
haven't search for them.

-- 
Manveru
jabber: manv...@manveru.pl
 gg: 1624001
   http://www.manveru.pl

Re: Where is the autosave in LyX 1.6.1 (Windows)?

[Vincent van Ravesteijn]

TJ McLaughlin schreef:


Today, for the second time, I was working on something in LyX and 
managed to crash it, losing my document. I had not yet saved the file 
(so the name in the title bar was "newfile1.lyx").
Both LyX itself and the documentation say that there is an "auto-save" 
feature to create emergency backups. (LyX said before crashing that 
when it resumed, I would be prompted to open my auto-saved 
document--this did not happen.)


I worked on the document for a good 40 minutes so the auto-save should 
have worked, right? /Does/ it work on the Windows version of LyX and 
if so, where does it put the backup files? I can't find them anywhere. 
Can anyone help me out?


Thanks,

TJ McLaughlin


I fixed this problem a few days ago.

Your autosave file is either in the temporary directory, somewhere in 
Documents&Settings\user. There should be a number of directories called 
lyx_tmpdir.***.


Or: the autosave file is in the directory of another document that was 
opened when you created the new one.


Good luck.

Vincent

Where is the autosave in LyX 1.6.1 (Windows)?

[TJ McLaughlin]

Today, for the second time, I was working on something in LyX and 
managed to crash it, losing my document. I had not yet saved the file 
(so the name in the title bar was "newfile1.lyx").
Both LyX itself and the documentation say that there is an "auto-save" 
feature to create emergency backups. (LyX said before crashing that when 
it resumed, I would be prompted to open my auto-saved document--this did 
not happen.)


I worked on the document for a good 40 minutes so the auto-save should 
have worked, right? /Does/ it work on the Windows version of LyX and if 
so, where does it put the backup files? I can't find them anywhere. Can 
anyone help me out?


Thanks,

TJ McLaughlin

Re: 1.6.2 handling of graphics paths changed from 1.6.1.

[Uwe Stöhr]

Paul A. Rubin schrieb:


Shooting from the hip...


We found the problem, it was my fault that I accidentally forgot two third-party executables in the 
current installer release. I'll provide a new installer this weekend.


regards Uwe

Re: 1.6.2 handling of graphics paths changed from 1.6.1.

[Paul A. Rubin]

Jason K Howlett wrote:
I have a LyX document that includes graphics in the header, i.e., 
ERT:\lhead{\includegraphics{mypic.eps}}. In LyX 1.6.1 this worked 
perfectly when producing DVI. I recently upgraded to 1.6.2 (on Windows) 
and the graphic no longer is displayed in the DVI. I used the LyX 
mechanism for inserting the graphic in the document body and it shows up 
fine. When I inspect the generated DVI I see the following differences:


For the file in the header with the manual includegraphics: 
PSfile=""C:/Documents and Settings/xx/Desktop/mypaper/"/mypic.eps"
For the file inserted with the LyX dialog: 
PSfile="0C__Documents_and_Settings_xx_Desktop_mypaper_mypic.eps"


I understand the issue with DVI and quoted paths and the need to run 
clean_dvi.py, but I don't understand why this worked fine with 1.6.1 and 
now doesn't with 1.6.2. If I export Latex code and run pplatex on it 
manually the results are just fine. In fact, the resulting DVI doesn't 
have any path information at all. It is just PSfile="mypic.eps".



For comparison, when I use LyX 1.6.1 the DVI has the following:

For the file in the header with the manual includegraphics: 
PSfile="C:/Documents and Settings/xx/Desktop/mypaper//mypic.eps"
For the file inserted with the LyX dialog: 
PSfile="0C__Documents_and_Settings_xx_Desktop_mypaper_mypic.eps"


The quotes are not around the path. Why has this behavior changed and how 
can I work around the problem?




Shooting from the hip (I don't have 1.6.2 yet, and since I'm in the 
middle of a LyX-heavy critical project I'm not going to install it for a 
while), have you tried putting the full path to the graphic file 
(suitably quoted) in the includegraphics command in the header as a 
workaround?


/Paul

1.6.2 handling of graphics paths changed from 1.6.1.

[Jason K Howlett]

Hello,

I have a LyX document that includes graphics in the header, i.e., 
ERT:\lhead{\includegraphics{mypic.eps}}. In LyX 1.6.1 this worked 
perfectly when producing DVI. I recently upgraded to 1.6.2 (on Windows) 
and the graphic no longer is displayed in the DVI. I used the LyX 
mechanism for inserting the graphic in the document body and it shows up 
fine. When I inspect the generated DVI I see the following differences:

For the file in the header with the manual includegraphics: 
PSfile=""C:/Documents and Settings/xx/Desktop/mypaper/"/mypic.eps"
For the file inserted with the LyX dialog: 
PSfile="0C__Documents_and_Settings_xx_Desktop_mypaper_mypic.eps"

I understand the issue with DVI and quoted paths and the need to run 
clean_dvi.py, but I don't understand why this worked fine with 1.6.1 and 
now doesn't with 1.6.2. If I export Latex code and run pplatex on it 
manually the results are just fine. In fact, the resulting DVI doesn't 
have any path information at all. It is just PSfile="mypic.eps".


For comparison, when I use LyX 1.6.1 the DVI has the following:

For the file in the header with the manual includegraphics: 
PSfile="C:/Documents and Settings/xx/Desktop/mypaper//mypic.eps"
For the file inserted with the LyX dialog: 
PSfile="0C__Documents_and_Settings_xx_Desktop_mypaper_mypic.eps"

The quotes are not around the path. Why has this behavior changed and how 
can I work around the problem?

Thanks,

Jason K. Howlett
Simulation Lead ATG IFS
Raytheon Missile Systems

Re: Smart single quotes in LyX (1.6.1, Mac OS X 10.5.6)

[Grant Jacobs]

Thanks for your reply. This doesn't quite address what I was after: 
almost, but not quite.


In case it's of use to others I'm going to explain what I wanted 
again, then how I have a sort-of solution, or more accurately a 
solution that raises another problem in it's place.


I was asking for a means to set up LyX so that whenever I type a 
single quote ('), the single quote would be treated as a "smart" 
quote, i.e. LyX would interpret it as an open or close quote as 
appropriate.


(I was not trying to set some key sequence to generate a smart single 
quote, I already knew how to do that--that's actually what I wanted 
to *stop* having to do, a key sequence is already set for generating 
a "smart" single quote by default. I was trying to get a single quote 
to be treated as a smart quote without having to remember to type a 
"special" key sequence.)


Furthermore, what I really wanted was to still get a "straight" 
quote, using a key sequence. The overall effect wanted was that of 
having a key sequence that might by default generate a "smart quote", 
generate a straight quote and have the quote character default to a 
smart quote. This can be achieved with the double quotes; I was 
trying to achieve the same with a single quote.



If you try set "'" to be the "mapped" key in the fashion BH 
describes, LyX will complain that:


   Shortcut `'' is already bound to:
   self-insert
   You need to remove that binding before creating a new one.

These "self-insert" bindings seem to be set in a file held within the 
application bundle, so "strictly speaking" this solution should be 
out of bounds to an end user. Ideally what would nice was a means to 
have "'" act as a "smart quote" through the user interface, and 
hopefully in a way I will not have keep manually updating the binding 
each time I update LyX. This doesn't seem to be possible at present.


My eventual sort-of solution was to edit the latinkeys.bind file (in 
the 'bind' directory of the Resources section of the application), so 
that


   \bind "quoteright" "self-insert"

now reads:

   \bind "quoteright" "quote-insert single"

This certainly makes all single quotes appear as "smart quotes", 
except now I can't find a way to map cmd-' (or whatever) to generate 
a "straight" quote, as it insists on generating a "quote-insert 
single"!


While I suspect there will be a solution to this somehow, this does 
suggest to me that the system for applying character mappings has 
some weaknesses.



Grant


On Thu, Mar 19, 2009 at 9:53 PM, Grant Jacobs 
 wrote:


 Is there a means to make "smart" *single* quotes the default in the same way
 as is done for double quotes?


LyX > Preferences > Editing > Shortcuts

1. Enter "quote" in the "Show key-bindings containing" field
2. select "quote-insert single"
3. click the "Modify button"
4. click the "Clear" button on the dialog that pops up
5. type the key you want to bind smart single quotes to
6. click "OK"
7. click "Save"

Bennett



--
---
Grant Jacobs Ph.D. BioinfoTools
ph. +64 3 478 0095  (office, after 10am)   PO Box 6129,
or  +64 27 601 5917 (mobile)   Dunedin,
gjac...@bioinfotools.com   NEW ZEALAND.
   Bioinformatics tools: deriving knowledge from biological data  
Bioinformatics tools - software development - consulting - training

 18 years experience in bioinformatics ready to solve your problem
Check out the website for more details: http://www.bioinfotools.com

Re: Smart single quotes in LyX (1.6.1, Mac OS X 10.5.6)

[BH]

On Thu, Mar 19, 2009 at 9:53 PM, Grant Jacobs  wrote:
>
> Is there a means to make "smart" *single* quotes the default in the same way
> as is done for double quotes?

LyX > Preferences > Editing > Shortcuts

1. Enter "quote" in the "Show key-bindings containing" field
2. select "quote-insert single"
3. click the "Modify button"
4. click the "Clear" button on the dialog that pops up
5. type the key you want to bind smart single quotes to
6. click "OK"
7. click "Save"

Bennett

Smart single quotes in LyX (1.6.1, Mac OS X 10.5.6)

[Grant Jacobs]

Is there a means to make "smart" *single* quotes the default in the 
same way as is done for double quotes?


Or, alternatively, is there a simple means to have LyX recognise that 
if a user enters ' LyX should treat it as if the user had entered 
shift-alt-' (or shift-ctrl-')?


I suspect that they might be some way of persuading this to happen 
from the key mapping files, but I've already wasted too much time 
trying to figure this out. (In any event locate doesn't report any 
.kdef files, so I have no idea where to look for them them yet!)



Grant

--
---
Grant Jacobs Ph.D. BioinfoTools
ph. +64 3 478 0095  (office, after 10am)   PO Box 6129,
or  +64 27 601 5917 (mobile)   Dunedin,
gjac...@bioinfotools.com   NEW ZEALAND.
   Bioinformatics tools: deriving knowledge from biological data
Bioinformatics tools - software development - consulting - training
 18 years experience in bioinformatics ready to solve your problem
Check out the website for more details: http://www.bioinfotools.com

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Pavel Sanda]

Guenter Milde wrote:
> Maybe someone with right permission could change the topic to 
> "LyX should have an option of where to export".

or somebody with the right permissions could give long standing
contributors bigger rights in bugzilla.

pavel

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-11, Richard Heck wrote:
> M-L wrote:
>> On Mon, 09 Mar 2009 17:34:24 -0400
>> rgheck  wrote:
>>> M-L wrote:
 rgheck  wrote:

> As Jurgen said, export to 1.5.x should work on Windows, too. But
> you have to find the right file: FILENAME.lyx15.

>> But maybe not many are so stupid and would look for the new version file
>> by default, rather than assume the original is now altered?

The same effect can be achieved by a "destination file choosing"
dialogue (with the default file name and path pre-selected).
The added bonus is that you are able to modify the target
destination/name.

> If someone wants to file an enhancement request over at bugzilla about 
> this, and then cc me (rgh...@comcast.net),
> I'll see if I can get to it for 1.6.3. (We're frozen for 1.6.2, which
> should be out in a few days.)

I added the request for "where to export" also as choice from GUI 
to Bug # 4501 
"lyx -e  should have an option of where to export".

Maybe someone with right permission could change the topic to 
"LyX should have an option of where to export".

Günter

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Richard Heck]

M-L wrote:

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck  wrote:

  

M-L wrote:


On Mon, 09 Mar 2009 07:58:49 -0400
rgheck  wrote:
  
  

As Jurgen said, export to 1.5.x should work on Windows, too. But
you have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in
windows. It seems that was the problem and I didn't know a new file
was generated, just thought the original was converted. I sent the
wrong file and therefore LyX produced the error message on my Linux
box.

  
  

Perhaps it'd be worth our issuing a message after the conversion,
saying what file has been exported.

rh



Or maybe for dummies like me - that: the "new version" file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

  
If someone wants to file an enhancement request over at bugzilla about 
this, and then cc me (rgh...@comcast.net), I'll see if I can get to it 
for 1.6.3. (We're frozen for 1.6.2, which should be out in a few days.)


rh

Re:[SOLVED] lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Joe(theWordy)Philbrook]

It would appear that on Mar 10, Joe(theWordy)Philbrook did say:

> The biggest problem should be that I have about a half dozen .lyx files
> that I open all at once via a script when I work on the story.  But
> since that script finishes by backing up my .lyxfiles to a usbstick from
> which I can import the latest changes to my laptop, then I suppose
> that the version of the script on the linux with the lyx ver 1.6.1
> could also" mv ${filename}.lyx ${filename}-v161.lyx, then invoke
> lyx2lyx to save the lyx 1.5.6 version as ${filename}.lyx... That way
> my script will always open the 1.5.6 compatabe copy. 

Actually the script that opens those files with lyx calls another
which does the backup... For me the solution was to establish the
version of lyx2lyx from lyx 1.6.1 as a command line tool. then to
modify the back-up script so that it now contains:

#!/bin/bash
# tarLyxSTUFF use tar & gzip to backup the lyxSTUFF dir...
# special version for saba4... extra code to convert .lyx files that
# were written by lyx 1.6.1 from "lyxformat 345" to "lyxformat 276"
# which the more prevalent lyx 1.5.6 can process. via the lyx2lyx
# script from lyx 1.6.1. (See ~/bin2nd/lyx2lyx for details)
cd ~/com/lyxSTUFF
fixlist=`grep -l "lyxformat 345" *.lyx`
for InName in $fixlist
do
OutName=`echo $InName|sed 's/\(.lyx\)/.v_1_6_1-lyx/'`
echo "Preserving original $InName  as  $OutName"
cp $InName $OutName
echo "Processing $InName via lyx2lyx"
lyx2lyx -t 276 -o $InName $OutName
done
# end of 'extra' code for saba4
cd ~/com/uplo
echo "
the old current LyXstuff files in uplo were"
ls -l LyXstuff*
mv LyXstuff.tgz LyXstuffWAS.tgz
cd ~/com/lyxSTUFF
tar -czf ~/com/uplo/LyXstuff.tgz .
cd ~/com/uplo
echo "
the new current LyXstuff files in uplo are"
ls -l LyXstuff*


I went with .v_1_6_1-lyx rather than -v161.lyx because I don't want
the next run to redundantly process the .v_1_6_1-lyx files...

FYI ~/com is the mount point for a personal data partition mounted
   there for my primary login regardless of which linux distro I boot...
And ~/com/uplo is regularly backed up to my laptop. especially prior to
my taking it somewhere I can't get at my desktop...

-- 
|   ---   ___
|   <0>   <->  Joe (theWordy) Philbrook
|   ^   J(tWdy)P
|~\___/~ <>

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Joe(theWordy)Philbrook]

,
It would appear that on Mar 9, Guenter Milde did say:

> On 2009-03-09, Joe(theWordy)Philbrook wrote:
> 
> > One of my computers is running lyx 1.6.1 on which I
> > recently wrote a couple of documents. Then I had occasion
> > to modify one of the .lyx files on a different linux box. 
> > But the available version of lyx was only 1.5.6 and when I
> > tried to open the document I was informed that it had been
> > created by a different version of lyx. And that the
> > lyx2lyx script had failed. 
 
> LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know
> how to handle the new format.

Yeah, that makes sense. Conversely then I expect when ver 1.6.1 opens a
document from ver 1.5.6, it recognizes the old format and converts it
so silently that I didn't know it had even run this lyx2lyx thingy.
 
> > Is there a way to tell lyx 1.6.1 to save in an older lyx format?
> 
> Yes. File>Export>Lyx and then choose the desired version.

Good. Then at least if I KNOW I'll need to access the durned thing
ahead of time... 

> > OR is there a conversion script that can convert a 
> > (lyx version 0.6.1).lyx  file into something lyx 1.5.6 can open???

> Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.
> 
> You can 
> 
> * upgrade to 1.5.7 (save but maybe not possible)
> * replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
>   (on your own risk, backup the original),
> * place the lyx2lyx package in usr/local/, say and call "by hand".  

I don't think the one from 1.5.7 can handle it else I wouldn't have
had the error that got me to start this thread. But if the one from
1.6.1 can be called by hand, AND doesn't depend on specific libraries
that are only installed on the Linux that has lyx 1.6.1, then It
might be smart to at least put a copy of it in my ~/bin on the other
linux installations... Then If I happen to forget to export after
editing with the one instance of lyx ver 1.6.1 I'll still be able to
access the document when I'm using a different linux box.  

  (For assorted reasons I multi-boot several versions of
   linux. On Both my desktop AND my laptop. I never really
   know ahead of time which one I'll be using when I find
   the time to work on a book I'm trying to write.) 

The biggest problem should be that I have about a half dozen .lyx files
that I open all at once via a script when I work on the story.  But
since that script finishes by backing up my .lyxfiles to a usbstick from
which I can import the latest changes to my laptop, then I suppose
that the version of the script on the linux with the lyx ver 1.6.1
could also" mv ${filename}.lyx ${filename}-v161.lyx, then invoke
lyx2lyx to save the lyx 1.5.6 version as ${filename}.lyx... That way
my script will always open the 1.5.6 compatabe copy. 


NOTE: I just did a little testing and this can be made to work. But
it's not quite as simple as you described...

I found the lyx2lyx script and copied it's whole directory to a data
partiion. But when I ran:

cd ~/lyxstuff
/mnt/lyx2lyx/lyx2lyx -t 276 -o ${filename}.lyx ${filename}-v16.lyx

It coplained that /mnt/unicodesymbols wasn't there and output a zero
length ${filename}.lix file. But when I inserted all the non directory
files from /usr/share/lyx it worked.


-- 
|   ---   ___
|   <0>   <->  Joe (theWordy) Philbrook
|   ^   J(tWdy)P
|~\___/~ <>

Lyx 1.6.1 - T1{fontenc} not generated under WIndows (but ok under OSX)

[Hans-Georg.Stork]

I am using LyX under Windows and OSX. 

For the same file (class: article) OSX-LyX generates \usepackage[T1]{fontenc} 
whereas Windows-LyX does not. 

Result: LaTeX/TeX don't not do their job (plenty of error messages apparently 
related to unrecognised characters in the bibliography) for the Windows version 
whereas is works perfectly under OSX.

(NB: Of course I successfully tried the obvious remedy: add 
\usepackage[T1]{fontenc} to the user-defined Windows-LyX preamble. But that 
leaves me wondering why Windows-LyX does not do it in the first place, just 
like OSX-LyX does it.)

Re: problems with lyx 1.6.1

[rgheck]

Gesualdo Scutari wrote:

Thanks for your answer and your patience.
Actually I did: I use the browse button to select the bib file. SO, 
I'm sure that I give a full path to it.


I wouldn't be so sure. Look in the LaTeX file for the \bibliography 
command and see what's there.


rh


Thanks.

ALdo
Il giorno 10/mar/09, alle ore 20:05, rgheck ha scritto:


Gesualdo Scutari wrote:

Thanks for your answer.
I exported the lyx doc in tex and the only proble I see in the .log 
file is that there are undefined references. It seems that latex 
cannot find the bib file, which is in the same directory of the .tex 
file. In the tex file I call also other files that are in the same 
place and latex has no problem to see these files.


I also reinstalled the latex distribution and lyx as well. But I 
really don't know what else to do now?


When you add the bibtex file to your LyX document, make sure you give 
a full path to it. That should take care of the problem.


rh


Many thanks for your assistance.

Regards,

Aldo
Il giorno 09/mar/09, alle ore 20:04, rgheck ha scritto:


Gesualdo Scutari wrote:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my 
MAC OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use 
both article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in 
the dvi and there are no references at the end of the document. I 
use a bibtex file that works properly with any latex compiler.


Could you please help me? I was looking for a while on the web, 
but I cold not fix the problem.


Well, it seems that LaTeX can't find the bibliography file for some 
reason. The best way to debug this kind of thing is to export your 
LyX file to LaTeX and then process it from the command line. 
Hopefully, you'll then get the error message from LaTeX. Another 
option: While LyX is open, and after you've had a failed export, go 
to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on 
Linux) and process manually there. Then you're actually processing 
exactly what LyX would.


rh

Re: problems with lyx 1.6.1

[Gesualdo Scutari]

Thanks for your answer and your patience.
Actually I did: I use the browse button to select the bib file. SO,  
I'm sure that I give a full path to it.


Thanks.

ALdo
Il giorno 10/mar/09, alle ore 20:05, rgheck ha scritto:


Gesualdo Scutari wrote:

Thanks for your answer.
I exported the lyx doc in tex and the only proble I see in the .log  
file is that there are undefined references. It seems that latex  
cannot find the bib file, which is in the same directory of  
the .tex file. In the tex file I call also other files that are in  
the same place and latex has no problem to see these files.


I also reinstalled the latex distribution and lyx as well. But I  
really don't know what else to do now?


When you add the bibtex file to your LyX document, make sure you  
give a full path to it. That should take care of the problem.


rh


Many thanks for your assistance.

Regards,

Aldo
Il giorno 09/mar/09, alle ore 20:04, rgheck ha scritto:


Gesualdo Scutari wrote:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on  
my MAC OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use  
both article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in  
the dvi and there are no references at the end of the document. I  
use a bibtex file that works properly with any latex compiler.


Could you please help me? I was looking for a while on the web,  
but I cold not fix the problem.


Well, it seems that LaTeX can't find the bibliography file for  
some reason. The best way to debug this kind of thing is to export  
your LyX file to LaTeX and then process it from the command line.  
Hopefully, you'll then get the error message from LaTeX. Another  
option: While LyX is open, and after you've had a failed export,  
go to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on  
Linux) and process manually there. Then you're actually processing  
exactly what LyX would.


rh

Re: problems with lyx 1.6.1

[rgheck]

Gesualdo Scutari wrote:

Thanks for your answer.
I exported the lyx doc in tex and the only proble I see in the .log 
file is that there are undefined references. It seems that latex 
cannot find the bib file, which is in the same directory of the .tex 
file. In the tex file I call also other files that are in the same 
place and latex has no problem to see these files.


I also reinstalled the latex distribution and lyx as well. But I 
really don't know what else to do now?


When you add the bibtex file to your LyX document, make sure you give a 
full path to it. That should take care of the problem.


rh


Many thanks for your assistance.

Regards,

Aldo
Il giorno 09/mar/09, alle ore 20:04, rgheck ha scritto:


Gesualdo Scutari wrote:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my 
MAC OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use 
both article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in 
the dvi and there are no references at the end of the document. I 
use a bibtex file that works properly with any latex compiler.


Could you please help me? I was looking for a while on the web, but 
I cold not fix the problem.


Well, it seems that LaTeX can't find the bibliography file for some 
reason. The best way to debug this kind of thing is to export your 
LyX file to LaTeX and then process it from the command line. 
Hopefully, you'll then get the error message from LaTeX. Another 
option: While LyX is open, and after you've had a failed export, go 
to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on 
Linux) and process manually there. Then you're actually processing 
exactly what LyX would.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Uwe Stöhr wrote:
> Guenter Milde schrieb:

>> As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
>> and is easily overseen by a user, I propose to open a destination-chooser
>> (save-file dialogue) with export. 

> I propose to export to "name-lyx15.lyx" instead to "name.lyx15"

This would be an improvement. But still I would like to be able to set the
destination path and filename from LyX.

Example 1: 

* Export name.lyx (1.6 format) to the usb-stick at
  /media/usbdisk/name.lyx (1.5 format).
* take the usb-stick home and edit name.lyx with my old LyX 1.5,
* open it without any renaming etc,
* save back to the usb-stick (still 1.5 format of course),
* open with LyX 1.6,
...

Example 2: 

* At Feierabend, Export name.lyx to 1.5 format but overwriting the
  original.
* Use some syncing software to move all modified files to the usb-stick.
* -- as in Example 1.

Example 3:

* Export name.lyx to HTML with TTH, save it as name-tth.html
* Export name.lyx to HTML with LaTeX2HTML, save it as name-l2h.html
* Export name.lyx to HTML with L4H, save it as name-l4h.html
* Compare the results and decide which to publish on the web (or import
  with Word or ...).

Günter

Re: problems with lyx 1.6.1

[Gesualdo Scutari]

Thanks for your answer.
I exported the lyx  doc in tex and the only proble I see in the .log  
file is that there are undefined references. It seems that latex  
cannot find the bib file, which is in the same directory of the .tex  
file. In the tex file I call also other files that are in the same  
place and latex has no problem to see these files.


I also reinstalled the latex distribution and lyx as well. But I  
really don't know what else to do now?


Many thanks for your assistance.

Regards,

Aldo
Il giorno 09/mar/09, alle ore 20:04, rgheck ha scritto:


Gesualdo Scutari wrote:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my  
MAC OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use  
both article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in  
the dvi and there are no references at the end of the document. I  
use a bibtex file that works properly with any latex compiler.


Could you please help me? I was looking for a while on the web, but  
I cold not fix the problem.


Well, it seems that LaTeX can't find the bibliography file for some  
reason. The best way to debug this kind of thing is to export your  
LyX file to LaTeX and then process it from the command line.  
Hopefully, you'll then get the error message from LaTeX. Another  
option: While LyX is open, and after you've had a failed export, go  
to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on  
Linux) and process manually there. Then you're actually processing  
exactly what LyX would.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck  wrote:

> M-L wrote:
> > On Mon, 09 Mar 2009 07:58:49 -0400
> > rgheck  wrote:
> >   
> >> As Jurgen said, export to 1.5.x should work on Windows, too. But
> >> you have to find the right file: FILENAME.lyx15.
> >>
> >> 
> > Thank you for that. I will have to look for the right file in
> > windows. It seems that was the problem and I didn't know a new file
> > was generated, just thought the original was converted. I sent the
> > wrong file and therefore LyX produced the error message on my Linux
> > box.
> >
> >   
> Perhaps it'd be worth our issuing a message after the conversion,
> saying what file has been exported.
> 
> rh

Or maybe for dummies like me - that: the "new version" file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

Thanks again.
Charlie
-- 
Registered Linux User:- 329524
***
Mountains should be climbed with as little effort as possible and
without desire. The reality of your own nature should determine the
speed. If you become restless, speed up. If you become winded, slow
down. You climb the mountain in an equilibrium between restlessness and
exhaustion. Then, when you're no longer thinking ahead, each footstep
isn't just a means to an end but a unique event in
itself. ..Robert Pirsig

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[rgheck]

Uwe Stöhr wrote:

Guenter Milde schrieb:

As FILENAME.lyx15 will not be recognised as a LyX file by most file 
managers
and is easily overseen by a user, I propose to open a 
destination-chooser
(save-file dialogue) with export. 


I propose to export to "name-lyx15.lyx" instead to "name.lyx15"

Yes, that's been discussed many times and probably ought to be done now. 
But I think it'd still be worth at least telling the user what file has 
been exported. This is supposed to be done in the status bar, but it 
seems instantly to get over-written with the "buffer-export pdf" type 
message.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Uwe Stöhr]

Guenter Milde schrieb:


As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 


I propose to export to "name-lyx15.lyx" instead to "name.lyx15"

regards Uwe

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-09, M-L wrote:
> On Mon, 09 Mar 2009 07:58:49 -0400
> rgheck  wrote:

>> As Jurgen said, export to 1.5.x should work on Windows, too. But you 
>> have to find the right file: FILENAME.lyx15.

> Thank you for that. I will have to look for the right file in windows.
> It seems that was the problem and I didn't know a new file was
> generated, just thought the original was converted. I sent the wrong
> file and therefore LyX produced the error message on my Linux box.

As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 

(This would also solve the: "Why do I have to remove/rename a html file
(with a separate tool) if I want to compare the output of different html
export tools?" annoyance.)

Günter

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[rgheck]

M-L wrote:

On Mon, 09 Mar 2009 07:58:49 -0400
rgheck  wrote:
  
As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in windows.
It seems that was the problem and I didn't know a new file was
generated, just thought the original was converted. I sent the wrong
file and therefore LyX produced the error message on my Linux box.

  
Perhaps it'd be worth our issuing a message after the conversion, saying 
what file has been exported.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 09 Mar 2009 07:58:49 -0400
rgheck  wrote:

> Jürgen Spitzmüller wrote:
> > The method proposed by Siegfried works if (and only if) you do not
> > use a new feature of LyX 1.6 and if you do not use a feature whose
> > semantics was changed (which is the case for many features).
> >
> >   
> Let me just clarify what Jurgen means by this by giving an example.
> In LyX 1.5, a BibTeX inset would be written in the LyX file this way:
> 
> \begin_inset LatexCommand bibtex
> bibfiles "heck"
> options "plain"
> 
> \end_inset
> 
> In 1.6, it's like this:
> 
> \begin_inset CommandInset bibtex
> LatexCommand bibtex
> bibfiles "heck"
> options "plain"
> 
> \end_inset
> 
> There's a similar difference with citations and other "command"
> insets. Changing the format might work with these, if the parser
> happens to skip over the "CommandInset bibtex" bit that it doesn't
> recognize. But if that did work, it'd be by pure luck, and there are
> similar cases that won't work.
> 
> As Jurgen said, export to 1.5.x should work on Windows, too. But you 
> have to find the right file: FILENAME.lyx15.
> 
> Richard

Thank you for that. I will have to look for the right file in windows.
It seems that was the problem and I didn't know a new file was
generated, just thought the original was converted. I sent the wrong
file and therefore LyX produced the error message on my Linux box.

Thanks again to all for the explanations,
Charlie
-- 
Registered Linux User:- 329524
***
The nail that sticks up will be hammered down. --Japanese
proverb

***
Debian, just the best way to create magic
___

re:Re: Very frequent crashes in 1.6.1 (with loss of work)

[Van Damme Michael]

>rgheck wrote:
>>>   
>> I'll have a look at this under one of my Fedora 10 machines.
>>
>As I said in the bug report, I was unable to reproduce this problem 
>under F10, even fully updated. And that was using the test file attached 
>to the report, trying to follow the instructions given. It's possible 
>that the problem was caused by some kind of corruption of a key file and 
>was fixed by the re-install, not because anything got downgraded but 
>simply because the corrupt file got fixed.
>
>rh

This is absolutely possible (provided it wasn't a file of lyx itself, since I 
reinstalled it plenty of times). 
All I can say is that no other program seemed to have problems.
In a couple of weeks (when having a working lyx has become less of a priority) 
I'll upgrade again and we'll see.

Michael

Re: problems with lyx 1.6.1

[Richard Heck]

Florian Rubach wrote:

Gesualdo Scutari schrieb:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my 
MAC OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use both 
article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in the 
dvi and there are no references at the end of the document.  I use a 
bibtex file that works properly with any latex compiler.


Maybe it's a silly question, but is the path to your bibtex-file 
containing any whitespaces?



Not at all a silly question. Happens all the time!

rh

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Richard Heck]

rgheck wrote:

Van Damme Michael wrote:
I have downloaded version 1.6.2svn (from the svn server) and tried 
it, but the problem remains.

Is is quick enough to reproduce (or you comuputer fast enough) to 
run Lyx under valgrind until you hit the problem?


James



I've never used valgrind, but it is quick to reproduce. When my 
thesis is finished I'll look into it.


  

I'll have a look at this under one of my Fedora 10 machines.

As I said in the bug report, I was unable to reproduce this problem 
under F10, even fully updated. And that was using the test file attached 
to the report, trying to follow the instructions given. It's possible 
that the problem was caused by some kind of corruption of a key file and 
was fixed by the re-install, not because anything got downgraded but 
simply because the corrupt file got fixed.


rh

Re: problems with lyx 1.6.1

[Florian Rubach]

Gesualdo Scutari schrieb:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my MAC 
OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use both 
article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in the 
dvi and there are no references at the end of the document.  I use a 
bibtex file that works properly with any latex compiler
Maybe it's a silly question, but is the path to your bibtex-file 
containing any whitespaces?


Florian

Re: problems with lyx 1.6.1

[rgheck]

Gesualdo Scutari wrote:

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my MAC 
OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use both 
article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in the 
dvi and there are no references at the end of the document. I use a 
bibtex file that works properly with any latex compiler.


Could you please help me? I was looking for a while on the web, but I 
cold not fix the problem.


Well, it seems that LaTeX can't find the bibliography file for some 
reason. The best way to debug this kind of thing is to export your LyX 
file to LaTeX and then process it from the command line. Hopefully, 
you'll then get the error message from LaTeX. Another option: While LyX 
is open, and after you've had a failed export, go to LyX's temporary 
directory (it'd be /tmp/lyxdir.OTHERSTUFF on Linux) and process manually 
there. Then you're actually processing exactly what LyX would.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[rgheck]

Jürgen Spitzmüller wrote:
The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).


  
Let me just clarify what Jurgen means by this by giving an example. In 
LyX 1.5, a BibTeX inset would be written in the LyX file this way:


\begin_inset LatexCommand bibtex
bibfiles "heck"
options "plain"

\end_inset

In 1.6, it's like this:

\begin_inset CommandInset bibtex
LatexCommand bibtex
bibfiles "heck"
options "plain"

\end_inset

There's a similar difference with citations and other "command" insets. 
Changing the format might work with these, if the parser happens to skip 
over the "CommandInset bibtex" bit that it doesn't recognize. But if 
that did work, it'd be by pure luck, and there are similar cases that 
won't work.


As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.


Richard

RE: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Vincent van Ravesteijn - TNW]

>I created some files on LyX 1.6.1 in windows XP and then went to:
>
>[...]
>
>Then emailed them as an attachment and later picked it up on
>my Linux Debian Lenny machine and tried to open it with LyX
>1.5.5

I've heard this before. I think this was raised as a possible cause for
bug http://bugzilla.lyx.org/show_bug.cgi?id=5822. (I mean the different
OS'es and lyx2lyx).

Vincent

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
> I created some files on LyX 1.6.1 in windows XP and then went to:
>
> File - then to Export - then to LyX 1.5.x
>
> With each of them.
>
> Then emailed them as an attachment and later picked it up on my Linux
> Debian Lenny machine and tried to open it with LyX 1.5.5
>
> It wouldn't open but gave me the wrong version error message.

Maybe you picked the wrong file? Note that Export does not overwrite the 
original document, but creates a new one with the suffix *.lyx15 (this is to 
preserve the native new features of 1.6, which will end up in ERT if you re-
open the 1.5 file).

You can check this by the format number. The exported file (to 1.5.x) has
\lyxformat 276

while the 1.6.x file has
\lyxformat 345

To open the *.lyx15 file, you might need to change the suffix back to *.lyx 
(some versions know this suffix, though).

> So I can't tell you what went wrong, it didn't and wouldn't show
> anything but the error message, and when that was clicked off, just an
> empty LyX screen with LYX on it?
>
> So sorry, I can't give you some more details about what fails,
> because I don't know. The error message was nothing more than that. I
> just know it doesn't work for me.

A minimal example file would help as well.

> But I have done as stated above and changed the lines and that does
> work.
>
> I know - it doesn't help - it just works and the documents I have done
> this with, I am still working on and they are fine. It would appear
> that one way [the right way?] works for you and another works for me and
> some other people?

No. The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).

So if it works for you, it is pure luck.

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 11:21:45 +0100
Jürgen Spitzmüller  wrote:

> M-L wrote:
> > I recall that I once had to change many documents from LyX 1.6.1 and
> > deleted the first 6 or so lines at the top of the documents and
> > replaced them with 6 or so lines of the older version. I didn't
> > realise it was this simple. Anything that works is a nice
> > workaround.
> 
> Note that the possibility to corrupt your documents that way is high,
> and you might not even notice that in the first place. If you would
> give us some more details about _what_ fails, we might have a chance
> to fix the problem. Without further information, there's probably not
> much we can do.
> 
> Jürgen

I created some files on LyX 1.6.1 in windows XP and then went to:

File - then to Export - then to LyX 1.5.x 

With each of them.

Then emailed them as an attachment and later picked it up on my Linux
Debian Lenny machine and tried to open it with LyX 1.5.5

It wouldn't open but gave me the wrong version error message.

So I can't tell you what went wrong, it didn't and wouldn't show
anything but the error message, and when that was clicked off, just an
empty LyX screen with LYX on it?

So sorry, I can't give you some more details about _what_ fails,
because I don't know. The error message was nothing more than that. I
just know it doesn't work for me.

But I have done as stated above and changed the lines and that does
work.

I know - it doesn't help - it just works and the documents I have done
this with, I am still working on and they are fine. It would appear
that one way [the right way?] works for you and another works for me and
some other people?

Thank you,

Charlie

-- 
Registered Linux User:- 329524
***
The law will never make men free, it is men that have to make the law
free. .Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
> I recall that I once had to change many documents from LyX 1.6.1 and
> deleted the first 6 or so lines at the top of the documents and replaced
> them with 6 or so lines of the older version. I didn't realise it was this
> simple. Anything that works is a nice workaround.

Note that the possibility to corrupt your documents that way is high, and you 
might not even notice that in the first place. If you would give us some more 
details about _what_ fails, we might have a chance to fix the problem. Without 
further information, there's probably not much we can do.

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009, Siegfried Meunier-Guttin-Cluzel engaged keyboard and 
shared this with us all:
>--} Since I often have this problem, I've found a workaround ( not a nice
>--} one, but it works when the formats aren't too different).
>--} I simply change the number of the LyX format.
>--} Open your file with a text editor and see the second line e. g.
>--} \lyxformat 276
>--} Change this number to match the number used on the old file format and
>--} it can work.
>--} Of couse make backups, since it can be dangerous.
>--}
>--} Hope it helps.
>--} Siegfried.

Thank you.

I recall that I once had to change many documents from LyX 1.6.1 and deleted 
the first 6 or so lines at the top of the documents and replaced them with 6 
or so lines of the older version. I didn't realise it was this simple. 
Anything that works is a nice workaround.

So thank you.

Charlie

-- 
Registered Linux User:- 329524
***
I scarcely remember counting upon any Happiness—I look not for it if it be not 
in the present hour—nothing startles me beyond the Moment. The setting sun 
will always set me to rights—or if a Sparrow come before my Window I take 
part in its existence and pick about the Gravel. ---JOHN KEATS

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Siegfried Meunier-Guttin-Cluzel]

Since I often have this problem, I've found a workaround ( not a nice 
one, but it works when the formats aren't too different).

I simply change the number of the LyX format.
Open your file with a text editor and see the second line e. g.
\lyxformat 276
Change this number to match the number used on the old file format and 
it can work.

Of couse make backups, since it can be dangerous.

Hope it helps.
Siegfried.

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
> I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
> windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

What exactly doesn't work?

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 08:35:40 +0100
Jürgen Spitzmüller  wrote:

> Joe(theWordy)Philbrook wrote:
> > Is there a way to tell lyx 1.6.1 to save in an older lyx format?
> 
> File>Export>LyX 1.5.x
> 
> Jürgen

I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

No joy there at all.

Charlie
-- 
Registered Linux User:- 329524
***
Be true to your work, your word, and your
friend. ...Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

Joe(theWordy)Philbrook wrote:
> Is there a way to tell lyx 1.6.1 to save in an older lyx format?

File>Export>LyX 1.5.x

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Joe(theWordy)Philbrook wrote:

> One of my computers is running lyx 1.6.1 on which I recently wrote a
> couple of documents. Then I had occasion to modify one of the .lyx files 
> on a different linux box.  But the available version of lyx was only
> 1.5.6 and when I tried to open the document I was informed that it had
> been created by a different version of lyx. And that the lyx2lyx script
> had failed. 

> I'm reasonably certain I hadn't used any new advanced features from
> ver 1.6.1 that ver 1.5.6 doesn't have. 
...
> So I was a bit surprised that version 1.5.6 couldn't open the resulting
> document.

LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know how
to handle the new format.

> Is there a way to tell lyx 1.6.1 to save in an older lyx format?

Yes. File>Export>Lyx and then choose the desired version.

> OR is there a conversion script that can convert a (lyx version 1.6.1).lyx  
> file into something lyx 1.5.6 can open???

Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.

You can 

* upgrade to 1.5.7 (save but maybe not possible)
* replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
  (on your own risk, backup the original),
* place the lyx2lyx package in usr/local/, say and call "by hand".  

Günter

problems with lyx 1.6.1

[Gesualdo Scutari]

Dear all,

I'm writing because I have a serious problem using lyx 1.6.1 on my MAC  
OS 10.5.6 and MacTex 2008.
I'm used to write papers to be submitted to IEEE journals. I use both  
article class in lyx and IEEEtran class.
In both cases lyx cannot load the bibliography. I see only [?] in the  
dvi and there are no references at the end of the document.  I use a  
bibtex file that works properly with any latex compiler.


Could you please help me? I was looking for a while on the web, but I  
cold not fix the problem.


Many thanks in advance for your assistance.

Best regards,

Aldo

 

lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Joe(theWordy)Philbrook]

Hello. I happen to like lyx. for lots of things. But I need to be able
to access my documents via more than one computer. Not all of which
are easy to upgrade to newer software versions.

One of my computers is running lyx 1.6.1 on which I recently wrote a
couple of documents. Then I had occasion to modify one of the .lyx files 
on a different linux box.  But the available version of lyx was only
1.5.6 and when I tried to open the document I was informed that it had
been created by a different version of lyx. And that the lyx2lyx script
had failed. 

I'm reasonably certain I hadn't used any new advanced features from
ver 1.6.1 that ver 1.5.6 doesn't have. I started with a short document
that was created on ver 1.5.6 (or earlier)... Which I had opened with
ver 1.6.1 deleted a line. Added text to about 5 existing lines which i
modified the color of. Then inserted a few paragraphs of text. And did
a "Save As" new name. So I was a bit surprised that version 1.5.6
couldn't open the resulting document.

Is there a way to tell lyx 1.6.1 to save in an older lyx format?

OR is there a conversion script that can convert a (lyx version 1.6.1).lyx  
file into something lyx 1.5.6 can open???


-- 
|  ~^~   ~^~
|  Joe (theWordy) Philbrook
|  ^  J(tWdy)P
|\___/ <>

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Steve Litt]

On Sunday 08 March 2009 11:48:57 am James Mansion wrote:
> Van Damme Michael wrote:
> > I have downloaded version 1.6.2svn (from the svn server) and tried it,
> > but the problem remains.
>
> Is is quick enough to reproduce (or you comuputer fast enough) to run
> Lyx under valgrind until you hit the problem?

I should have thought of that!

SteveT

Steve Litt
Recession Relief Package
http://www.recession-relief.US

Re: Very frequent crashes in 1.6.1 (with loss of work)

[rgheck]

Van Damme Michael wrote:

I have downloaded version 1.6.2svn (from the svn server) and tried it, but the 
problem remains.
  
  
Is is quick enough to reproduce (or you comuputer fast enough) to run 
Lyx under valgrind until you hit the problem?


James



I've never used valgrind, but it is quick to reproduce. When my thesis is 
finished I'll look into it.

  

I'll have a look at this under one of my Fedora 10 machines.

rh

re:Re: Very frequent crashes in 1.6.1 (with loss of work)

[Van Damme Michael]

>> I have downloaded version 1.6.2svn (from the svn server) and tried it, but 
>> the problem remains.
>>   
>Is is quick enough to reproduce (or you comuputer fast enough) to run 
>Lyx under valgrind until you hit the problem?
>
>James

I've never used valgrind, but it is quick to reproduce. When my thesis is 
finished I'll look into it.

Michael

Re: Very frequent crashes in 1.6.1 (with loss of work)

[James Mansion]

Van Damme Michael wrote:

I have downloaded version 1.6.2svn (from the svn server) and tried it, but the 
problem remains.
  
Is is quick enough to reproduce (or you comuputer fast enough) to run 
Lyx under valgrind until you hit the problem?


James

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Pavel Sanda]

Van Damme Michael wrote:
> since I like lyx I will invest time to try to find out which package is the 
> cause.

please do then. it could help in the similar cases too...
pavel

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Van Damme Michael]

Pavel and Steve, thanks for your helpful comments.

>maybe. but there are striking similarities - lyx input frozen, no cpu load, bt 
>points somewhere
>in between qt<->xorg, libxcb used; (in this we enter there through 
>QInputContext::reset()).

It's true that there are many similarities. There are no messages to the 
console though, and when interrupting with gdb lyx is always in a kernel call.

> does this happen with all your files?

It does, but they are all of the same type (not too much text, a lot of 
equations, a lot of cross-references and some figures).
In the meantime, I have filed a bugreport (bug 5835), which includes a file and 
intructions that will provoke a guaranteed crash. These aren't the only ones, 
however, the lockup also occurs in other circumstances.

> of course you restarted X after downgrade, just for sure :)

I did :)  And since the problem was still there I rebooted just to be sure.

@ Steve:

There's a lot of sense in what you say, and since I like lyx I will invest time 
to try to find out which package is the cause. But not now. I only have three 
more weeks to finish my thesis, and since I'm behind shedule I need every hour 
I have.
As a temporary solution, I've done a full reinstall of fedora core 10, without 
any updates. This fixes the problem (for now).

Kind regards, 
Michael

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Stefano Franchi]

On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote:
> Van Damme Michael wrote:
> > Thank you for your reply.
> > I've compiled lyx-1.6.1 in debug mode (using the latest stable source
> > available on the lyx site) and ran it under gdb. Once locked-up, I
> > interrupted it in gdb and got the following backtrace:
> >
> > #0  0x00943416 in __kernel_vsyscall ()
> > #1  0x006a83d1 in select () from /lib/libc.so.6
> > #2  0x00911295 in ?? () from /usr/lib/libxcb.so.1
> > #3  0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
>
> ahh i have seen this backtrace
> i guess you are the next victim of "serious problems with LyX (semi-fatal
> crashes)" thread...
>
> http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html
>
> i dont remember if the issue was solved though.
Nope it wasn't

I am still there. I am jsut less vocal becaude I have just finished a major 
writing project and I have not been typing for hours a day as I was until 2 
weeks ago. That's when the crashes happened regularly. So I guess there is 
also some kind of entropy at work somewhere 



> if not try to downgrade your xorg packages, especially anything which pulls
> libxcb.so in.
>
> pavel


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

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Steve Litt]

On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote:

> On fedora, libxcb is in a separate package, but it has never been updated
> (the installed version is the one that came with fedora 10 originally). I
> have downgraded myx xorg packages to the previously installed version, but
> that still doesn't help.
>
> Michael

Hi Michael,

Now that you upgraded to 1.6.2 and downgraded xorg, it looks like there isn't 
any quickie workaround. That's too bad -- life would have been easier if 
there had been.

If I were in your shoes I'd try to find some situation, ANY situation, in 
which the problem disappears. Once you have a setup that intermittently 
crashes and one than never crashes, I'd exploit the differences to find the 
root cause, or at least narrow it down to the point where the developers 
would find it easy to fix.

I know nothing about Red Hat or YUM, but would it be possible to roll back all 
the updates you listed in your other email? If that were possible, you could 
then see whether the problem still (intermittently) occurs. Either way, it 
would yield valuable information.

Another thing I'd try is working for an hour or so with a trivially simple, 
short document. No figures, nothing but text. Does it crash or not? If not, 
perhaps there's something in the original document that makes crashes more 
likely, and if you can find it, you can:

1) Temporarily take it out of the doc
2) Submit a doc with only that element as an example for the developers.

Also try this: Create a brand new user for your system, put the document in 
that user's home directory, and edit the document as the new user. This could 
rule out or point to some user-specific piece of configuration.

Perhaps there's a clash with a running process. Try temporarily shutting off 
all non-essential processes, then power down and power up, and see whether 
this intermittent fails to appear after a few hours.

Just keep thinking of quick and easy diagnostic tests to rule out parts of the 
system. Sooner or later you'll identify factors that influence the frequency 
of these crashes, and when you do, you'll be very close to either solving it 
yourself, or making it easy for the developers to solve it.

I'm sorry you have to go through this. Intermittents are ugly in the best of 
times, and certainly not welcome when you're working on your thesis.

SteveT

Steve Litt
Recession Relief Package
http://www.recession-relief.US

Re: Re: Very frequent crashes in 1.6.1 (with loss of work)

[Pavel Sanda]

Van Damme Michael wrote:
> >> #0  0x00943416 in __kernel_vsyscall ()
> >> #1  0x006a83d1 in select () from /lib/libc.so.6
> >> #2  0x00911295 in ?? () from /usr/lib/libxcb.so.1
> >> #3  0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
> >
> >ahh i have seen this backtrace
> >i guess you are the next victim of "serious problems with LyX (semi-fatal 
> >crashes)" thread...
> 
> >http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ  
> >public.gmane.org/msg70837.html
> 
> 
> I think I'm experiencing a different problem. The thread you mention says 
> that while the interface becomes unresponsive, the user can still quit or 
> save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the 
> ctrl-... keys also stop working.

maybe. but there are striking similarities - lyx input frozen, no cpu load, bt 
points somewhere
in between qt<->xorg, libxcb used; (in this we enter there through 
QInputContext::reset()).

> I have downloaded version 1.6.2svn (from the svn server) and tried it, but 
> the problem remains.

does this happen with all your files?

> On fedora, libxcb is in a separate package, but it has never been updated 
> (the installed version is the one that came with fedora 10 originally).
> I have downgraded myx xorg packages to the previously installed version, but 
> that still doesn't help.

of course you restarted X after downgrade, just for sure :)
pavel

Re:Re: Very frequent crashes in 1.6.1 (with loss of work)

[Van Damme Michael]

Pavel Sanda wrote:

>> #0  0x00943416 in __kernel_vsyscall ()
>> #1  0x006a83d1 in select () from /lib/libc.so.6
>> #2  0x00911295 in ?? () from /usr/lib/libxcb.so.1
>> #3  0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
>
>ahh i have seen this backtrace
>i guess you are the next victim of "serious problems with LyX (semi-fatal 
>crashes)" thread...

>http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ  
>public.gmane.org/msg70837.html


I think I'm experiencing a different problem. The thread you mention says that 
while the interface becomes unresponsive, the user can still quit or save using 
ctrl-Q and ctrl-S. In my case, there is a full lockup, the ctrl-... keys also 
stop working.

I have downloaded version 1.6.2svn (from the svn server) and tried it, but the 
problem remains.

>i dont remember if the issue was solved though.
>if not try to downgrade your xorg packages, especially anything which pulls 
>libxcb.so in.

On fedora, libxcb is in a separate package, but it has never been updated (the 
installed version is the one that came with fedora 10 originally).
I have downgraded myx xorg packages to the previously installed version, but 
that still doesn't help.

Michael

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Pavel Sanda]

Pavel Sanda wrote:
> Van Damme Michael wrote:
> > 
> > Thank you for your reply.
> > I've compiled lyx-1.6.1 in debug mode (using the latest stable source 
> > available on the lyx site) and ran it under gdb. Once locked-up, I 
> > interrupted it in gdb and got the following backtrace:
> 
> > #0  0x00943416 in __kernel_vsyscall ()
> > #1  0x006a83d1 in select () from /lib/libc.so.6
> > #2  0x00911295 in ?? () from /usr/lib/libxcb.so.1
> > #3  0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
> 
> ahh i have seen this backtrace
> i guess you are the next victim of "serious problems with LyX (semi-fatal 
> crashes)" thread...
> 
> http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html
> 
> i dont remember if the issue was solved though.
> if not try to downgrade your xorg packages, especially anything which pulls 
> libxcb.so in.

looking in our bugzilla there are some fixes in the tree already for crashes 
with libxcb
included in bt. it maybe better if you try lyx 1.6.2 released soon (rc 
tomorrow) or directly 
checkout our branch from svn now :)

pavel

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Pavel Sanda]

Van Damme Michael wrote:
> 
> Thank you for your reply.
> I've compiled lyx-1.6.1 in debug mode (using the latest stable source 
> available on the lyx site) and ran it under gdb. Once locked-up, I 
> interrupted it in gdb and got the following backtrace:

> #0  0x00943416 in __kernel_vsyscall ()
> #1  0x006a83d1 in select () from /lib/libc.so.6
> #2  0x00911295 in ?? () from /usr/lib/libxcb.so.1
> #3  0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1

ahh i have seen this backtrace
i guess you are the next victim of "serious problems with LyX (semi-fatal 
crashes)" thread...

http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html

i dont remember if the issue was solved though.
if not try to downgrade your xorg packages, especially anything which pulls 
libxcb.so in.

pavel

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Van Damme Michael]

Thank you for your reply.
I've compiled lyx-1.6.1 in debug mode (using the latest stable source available 
on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb 
and got the following backtrace:

#0  0x00943416 in __kernel_vsyscall ()
#1  0x006a83d1 in select () from /lib/libc.so.6
#2  0x00911295 in ?? () from /usr/lib/libxcb.so.1
#3  0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#4  0x00152831 in ?? () from /usr/lib/libX11.so.6
#5  0x00152ba0 in ?? () from /usr/lib/libX11.so.6
#6  0x00153367 in _XReadEvents () from /usr/lib/libX11.so.6
#7  0x0013131b in XIfEvent () from /usr/lib/libX11.so.6
#8  0x001802fa in ?? () from /usr/lib/libX11.so.6
#9  0x0017f300 in ?? () from /usr/lib/libX11.so.6
#10 0x0017f7b7 in _XimRead () from /usr/lib/libX11.so.6
#11 0x0016b3e2 in ?? () from /usr/lib/libX11.so.6
#12 0x00158aba in XmbResetIC () from /usr/lib/libX11.so.6
#13 0x06d06f5d in ?? () from /usr/lib/libQtGui.so.4
#14 0x08583081 in lyx::frontend::GuiWorkArea::mousePressEvent (this=0x9e1bef0, 
e=0xbfffd5f8) at GuiWorkArea.cpp:690
#15 0x067ea6d9 in QWidget::event () from /usr/lib/libQtGui.so.4
#16 0x06b20943 in QFrame::event () from /usr/lib/libQtGui.so.4
#17 0x06bb711f in QAbstractScrollArea::viewportEvent ()
   from /usr/lib/libQtGui.so.4
#18 0x06bb96c5 in ?? () from /usr/lib/libQtGui.so.4
#19 0x003a53aa in QCoreApplicationPrivate::sendThroughObjectEventFilters ()
   from /usr/lib/libQtCore.so.4
#20 0x0679266a in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#21 0x0679ae81 in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0x08539997 in lyx::frontend::GuiApplication::notify (this=0x8ab30c8, 
receiver=0x9977148, event=0xbfffd5f8) at GuiApplication.cpp:1230
#23 0x003a61c1 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#24 0x0679a10e in QApplicationPrivate::sendMouseEvent ()
   from /usr/lib/libQtGui.so.4
#25 0x06804456 in ?? () from /usr/lib/libQtGui.so.4
#26 0x068037e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#27 0x0682be1a in ?? () from /usr/lib/libQtGui.so.4
#28 0x007fb238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#29 0x007fe8e3 in ?? () from /lib/libglib-2.0.so.0
#30 0x007feaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#31 0x003d07f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#32 0x0682b515 in ?? () from /usr/lib/libQtGui.so.4
#33 0x003a488a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#34 0x003a4a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#35 0x003a7105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#36 0x06792507 in QApplication::exec () from /usr/lib/libQtGui.so.4
#37 0x08539234 in lyx::frontend::GuiApplication::exec (this=0x8ab30c8)
at GuiApplication.cpp:1045
#38 0x081cbcf3 in lyx::LyX::exec (this=0xb450, ar...@0xb480, 
argv=0xb504) at LyX.cpp:343
#39 0x0807277d in main (argc=2, argv=0x0) at main.cpp:46

The latest qt upgrade (to package qt-4.4.3-10.fc10.i386) dates from January 
15th, long before the problem started. 

Kind regards,
Michael



 

Re: Very frequent crashes in 1.6.1 (with loss of work)

[Pavel Sanda]

Van Damme Michael wrote:
> If anyone has any suggestions I would be very grateful.

from the list you gave i would try what happen if you downgrade
xorg-* and also libpng could be related.
qt upgrade didnt happen?

the last resort is to compile lyx in debug mode, run it under gdb
and provide us backtrace.

pavel

Very frequent crashes in 1.6.1 (with loss of work)

[Van Damme Michael]

Hi all,

over the last few months, I've been writing my thesis in lyx (using it many 
hours every day). I'm using lyx-1.6.1 on fedora 10 (the version available 
through fedora's package manager yum).
Since this week, however, I'm experiencing very frequent crashes (being able to 
work for 15 minutes without a crash has become exceptional). Before, lyx almost 
never crashed. 

Most crashes seem to occur when moving the cursor with the arrow keys, 
especially when selecting things (moving around when shift is pressed), but 
sometimes also when editing formulas or just text. Sometimes it just locks up, 
sometimes it becomes extremely slow (it takes about 20 seconds to respond to a 
keypress, for instance) and then locks up. When it is very slow or locked up, 
there is no excessive cpu or ram usage. The only way to close the program is to 
kill it. I usually start it from an xterm, but there are no problem related 
messages dispayed in the terminal when it crashes. No emergency copy of the 
document is saved, all work that wasn't saved is lost in the crash.

Since the problem has started so suddenly, I suspect it may be caused by a 
package update (fedora very regularly offer package updates). I have a list of 
recently updated packages, but am quite clueless about which may cause the 
problem. Since I've only done relatively small edits since early last week, I 
don't exactly know which date the problem started, only that it was after 
february 24th, so I have included the (relatively long) list of updated 
packages since then at the and of this post.
No other programs are having problems, lyx seems to be the only one.

If anyone has any suggestions I would be very grateful.

Kind regards,
Michael

List of updated packages (from /var/log/yum.log):

Feb 25 01:41:27 Updated: gvfs-1.0.3-5.fc10.i386
Feb 25 01:41:27 Updated: libgcrypt-1.4.4-1.fc10.i386
Feb 25 01:41:28 Updated: 2:gimp-libs-2.6.5-1.fc10.i386
Feb 25 01:41:31 Updated: system-config-printer-libs-1.0.15-1.fc10.i386
Feb 25 01:41:35 Updated: ghex-2.24.0-2.fc10.i386
Feb 25 01:41:56 Updated: 2:gimp-2.6.5-1.fc10.i386
Feb 25 01:41:57 Updated: libgcrypt-devel-1.4.4-1.fc10.i386
Feb 25 01:41:57 Updated: gvfs-smb-1.0.3-5.fc10.i386
Feb 25 01:41:58 Updated: gvfs-obexftp-1.0.3-5.fc10.i386
Feb 25 01:41:58 Updated: gvfs-gphoto2-1.0.3-5.fc10.i386
Feb 25 01:41:58 Updated: gvfs-archive-1.0.3-5.fc10.i386
Feb 25 01:41:58 Updated: gvfs-fuse-1.0.3-5.fc10.i386
Feb 25 01:41:59 Updated: 1:wpa_supplicant-0.6.4-3.fc10.i386
Feb 25 01:42:19 Updated: gstreamer-plugins-good-0.10.13-1.fc10.i386
Feb 25 01:42:19 Updated: xorg-x11-server-common-1.5.3-13.fc10.i386
Feb 25 01:42:21 Updated: system-config-printer-1.0.15-1.fc10.i386
Feb 25 01:42:24 Updated: flash-plugin-10.0.22.87-release.i386
Feb 25 01:42:24 Updated: fontpackages-filesystem-1.20-1.fc10.noarch
Feb 25 01:42:25 Updated: xorg-x11-server-Xorg-1.5.3-13.fc10.i386
Feb 25 01:42:26 Updated: rpm-libs-4.6.0-1.fc10.i386
Feb 25 01:42:29 Updated: rpm-4.6.0-1.fc10.i386
Feb 25 01:42:29 Updated: rpm-devel-4.6.0-1.fc10.i386
Feb 25 01:42:30 Updated: rpm-build-4.6.0-1.fc10.i386
Feb 25 01:42:31 Updated: rpm-python-4.6.0-1.fc10.i386
Feb 25 01:42:47 Updated: rpm-4.6.0-1.fc10.i386
Feb 26 03:28:23 Updated: e2fsprogs-libs-1.41.4-1.fc10.i386
Feb 26 03:28:23 Updated: crontabs-1.10-26.fc10.noarch
Feb 26 03:28:26 Updated: e2fsprogs-1.41.4-1.fc10.i386
Feb 26 03:28:27 Updated: hal-cups-utils-0.6.19-1.fc10.i386
Feb 26 03:28:29 Updated: e2fsprogs-devel-1.41.4-1.fc10.i386
Feb 26 03:28:31 Updated: anacron-2.3-66.fc10.i386
Feb 27 03:42:22 Updated: 1:gdm-2.24.1-4.fc10.i386
Feb 27 03:42:23 Updated: 2:ntfs-3g-2009.2.1-2.fc10.i386
Feb 27 03:42:29 Updated: pygtk2-2.13.0-3.fc10.i386
Feb 27 03:42:29 Updated: libmusicbrainz3-3.0.2-4.fc10.i386
Feb 27 03:42:30 Updated: 2:libpng-1.2.35-1.fc10.i386
Feb 27 03:42:31 Updated: xorg-x11-drv-evdev-2.1.3-1.fc10.i386
Feb 27 03:42:31 Updated: pygtk2-libglade-2.13.0-3.fc10.i386
Feb 27 03:42:32 Updated: 1:gdm-user-switch-applet-2.24.1-4.fc10.i386
Feb 27 03:42:32 Updated: setup-2.7.4-4.fc10.noarch
Feb 28 22:49:40 Updated: pciutils-libs-3.0.2-3.fc10.i386
Feb 28 22:49:41 Updated: pciutils-3.0.2-3.fc10.i386
Feb 28 22:49:42 Updated: iok-1.3.1-1.fc10.i386
Feb 28 22:49:53 Updated: coreutils-6.12-19.fc10.i386
Feb 28 22:49:54 Updated: upstart-0.3.9-22.fc10.i386
Feb 28 22:49:54 Updated: pciutils-devel-3.0.2-3.fc10.i386
Mar 03 01:57:46 Updated: mplayer-1.0-0.104.20090204svn.fc10.i386
Mar 04 02:34:52 Updated: selinux-policy-3.5.13-46.fc10.noarch
Mar 04 02:34:53 Updated: kernel-firmware-2.6.27.19-170.2.35.fc10.noarch
Mar 04 02:35:04 Installed: system-config-date-1.9.36-1.fc10.noarch
Mar 04 02:35:08 Installed: system-config-date-docs-1.0.5-1.fc10.noarch
Mar 04 02:36:01 Updated: selinux-policy-targeted-3.5.13-46.fc10.noarch
Mar 04 02:36:09 Updated: kernel-headers-2.6.27.19-170.2.35.fc10.i386
Mar 04 02:36:38 Installed: kernel-devel-2.6.27.19-170.2.35.fc10.i686
Mar 04 02:36:43 Updated: gvfs-1.0.3-6.fc10.i386
Mar 04 

Re: LyX-1.6.1 boost problem on lenovoT61

[Pavel Sanda]

Hellmut Weber wrote:
> Hi,
> I'm setting up my Lenovo T61 with
> Intel(R) Core(TM)2 Duo CPU T9300  @ 2.50GHz
> using gentoo Linux.
>
> When trying to compile LyX-1.6.1 from the gentoo ebuild
> I run into problems with boost-1.34.1-r2 stable.
> I can merge boost-1.36.0 or boost-1.37.0, but in  these cases
> merge of lyx-1.6.1.crashes.
>
> Does anybody know what to do?

can you post log?
pavel

SV: incorrect germanic umlaut display in lyx 1.6.1

[Ingar Pareliussen]

>I actually came across a weird bug in LyX 1.6.1.
>I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1

It is probably the error in Qt4.5rc1, Qt4.5 is reported to have been fixed.

Ingar 

incorrect germanic umlaut display in lyx 1.6.1

[Jörg Müller-Barkei]

Hello,

I actually came across a weird bug in LyX 1.6.1.
I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1
release of Opensuse (of today!)
I'm a newbie to LaTeX and LyX and getting a little irritated.

Its as follows:
since today when I type a text in german I get these ( ÃÃÃ) characters
instead of these (üöä). BUt I get the correct characters when holding down
the CTRL-key while typing. I think this is rather inconvenient when typing
on a german keyboard configured for german (and all alanguage configurations
within LyX are correctly set to "german")

I haven't changed anything in the LyX or LaTeX config the last days (as far
as I can remember) but didn't come acreoss this bug before.

Sorry, I feel this might be a rather dumb question, but what can I do to
change this 

Thanks a lot for your help!

Greets from Berlin
Jörg

LyX-1.6.1 boost problem on lenovoT61

[Hellmut Weber]

Hi,
I'm setting up my Lenovo T61 with
Intel(R) Core(TM)2 Duo CPU T9300  @ 2.50GHz
using gentoo Linux.

When trying to compile LyX-1.6.1 from the gentoo ebuild
I run into problems with boost-1.34.1-r2 stable.
I can merge boost-1.36.0 or boost-1.37.0, but in  these cases
merge of lyx-1.6.1.crashes.

Does anybody know what to do?

On an older version of my system I'm running lyx-1.6.1 without any problem.

TIA

Hellmut

--
Dr. Hellmut Weber m...@hellmutweber.de
Degenfeldstraße 2 tel   +49-89-3081172
D-80803 München-Schwabing mobil +49-172-8450321
please: No DOCs, no PPTs. why: tinyurl.com/cbgq

Re: LyX 1.6.1 crash when pasting a branch inset

[Jürgen Spitzmüller]

Guenter Milde wrote:
> Strange:
>
> * I use a released version (LyX 1.6.1 from Debian/unstable)

OK, then it's a real crash, _next_ to the assertion (Richard's backtrace also 
indicates a crash).

> * LyX closed down suddenly,
>
>   with *.lyx.emergency savings that sometimes where corrupt, :-(

I know. It hit me as well now. We'll fix this for 1.6.2.

Jürgen

Re: LyX 1.6.1 crash when pasting a branch inset

[Guenter Milde]

On 2009-02-27, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> Is this a known bug that will be fixed in 1.6.2 ?

> BTW note that you faced an assertion, not a crash. In release mode,
> assertions do not shut down LyX.

Strange:

* I use a released version (LyX 1.6.1 from Debian/unstable)

* LyX closed down suddenly, 

  with *.lyx.emergency savings that sometimes where corrupt, :-(

  without saving changed GUI configuration,
  
  without updating the "last opened files" list.
  
No crash?
  
Günter

Re: LyX 1.6.1 crash when pasting a branch inset

[rgheck]

Vincent van Ravesteijn - TNW wrote:

As Guenter mentioned, he has a master with childs. Doing a cut and paste
in a child document does crash LyX 1.6.1. I have no current branch or
svn to test with.

  

OK, now I have it. Note that you get an infinite loop through
emergencyWriteAll() when this happens, so you need to set a breakpoint
there to get anything useful.

I think this must be related to the FIXME at line 300 of
CutAndPaste.cpp. The call to updateLabels() sends us to loadIfNeeded
eventually because we're in a child, and we end up calling
InsetBranch::buffer() before the buffer is actually set, which I think
happens later in updateLabels().

rh

=

gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) bt
bt
#0 lyx::BufferList::emergencyWrite (this=0x3076878, buf=0x36c2920) at
BufferList.cpp:236
#1 0x004eab89 in
std::for_each<__gnu_debug::_Safe_iterator<__gnu_cxx::__normal_iterator

__gnu_norm::vector > >,
__gnu_debug_def::vector > >,
boost::_bi::bind_t,
std::allocator >, boost::_mfi::mf1, std::allocator >, lyx::BufferList,
lyx::Buffer*>, boost::_bi::list2,
boost::arg<1> > > > (__fir...@0x7fff78ea63d0, __la...@0x7fff78ea63a0,
__f={f_ = {f_ = &lyx::BufferList::emergencyWrite(lyx::Buffer*)}, l_ =
{,boost::arg<1>
= { >> = 

{a1_ = {t_ = 0x3076878}}, }, }}) at
../boost/boost/bind/mem_fn_template.hpp:162
#2 0x004e49fb in lyx::BufferList::emergencyWriteAll
(this=0x3076878) at BufferList.cpp:223
#3 0x0061aaa7 in lyx::emergencyCleanup () at LyX.cpp:799
#4 0x0061adc5 in lyx::lyx_exit (exit_code=2028626656) at LyX.cpp:196
#5 0x00470b3e in boost::assertion_failed (expr=0xe68068 "false",
function=0xfc5340 "void lyx::doAssert(const char*, const char*, long
int)", file=0xfc5308 "lassert.cpp", line=23) at boost.cpp:47
#6 0x00dea51f in lyx::doAssert (expr=0xe68068 "false",
file=0xee11a6 "insets/Inset.cpp", line=138) at lassert.cpp:23
#7 0x0095a47e in lyx::Inset::buffer (this=)
at insets/Inset.cpp:138
#8 0x009580f0 in lyx::Inset::buffer (this=0x7fff78ea62e0) at
insets/Inset.cpp:148
#9 0x00980532 in lyx::InsetBranch::isBranchSelected
(this=0x7fff78ea62e0) at insets/InsetBranch.cpp:199
#10 0x0098057b in lyx::InsetBranch::isMacroScope
(this=0x7fff78ea62e0) at insets/InsetBranch.cpp:252
#11 0x00481b1a in lyx::Buffer::updateMacros (this=0x36b7250,
i...@0x7fff78ea70a0, sco...@0x7fff78ea7050) at Buffer.cpp:1934
#12 0x00484184 in lyx::Buffer::updateMacros (this=0x36b7250) at
Buffer.cpp:2017
#13 0x004846cf in lyx::Buffer::setParent (this=0x7fff78ea62e0,
buffer=0x3076878) at Buffer.cpp:1707
#14 0x009d99ad in lyx::InsetInclude::loadIfNeeded
(this=0x36cb520, pare...@0x36c2920) at insets/InsetInclude.cpp:417
#15 0x00481c7f in lyx::Buffer::updateMacros (this=0x36c2920,
i...@0x7fff78ea7bb0, scope=) at Buffer.cpp:1953
#16 0x00484184 in lyx::Buffer::updateMacros (this=0x36c2920) at
Buffer.cpp:2017
#17 0x0048460c in lyx::Buffer::updateLabels (this=0x36c2920,
childonly=false) at Buffer.cpp:2748
#18 0x00484411 in lyx::Buffer::updateLabels (this=0x36b7250,
childonly=false) at Buffer.cpp:2727
#19 0x007e7d98 in lyx::cap::pasteParagraphList (c...@0x3789cd8,
parli...@0x3792188, docclass=0x36c88b0, errorli...@0x138d0a0) at
CutAndPaste.cpp:840
#20 0x007e7f55 in lyx::cap::pasteFromStack (c...@0x3789cd8,
errorli...@0x138d0a0, sel_index=0) at CutAndPaste.cpp:858
#21 0x0070db5d in lyx::Text::dispatch (this=0x372b010,
c...@0x3789cd8, c...@0x7fff78eae840) at Text3.cpp:1025
#22 0x00a9fe34 in lyx::InsetText::doDispatch (this=0x372aff0,
c...@0x3789cd8, c...@0x7fff78eae840) at insets/InsetText.cpp:254
#23 0x0095887e in lyx::Inset::dispatch (this=0x372aff0,
c...@0x3789cd8, c...@0x7fff78eae840) at insets/Inset.cpp:216
#24 0x007de9a3 in lyx::Cursor::dispatch (this=0x3789cd8,
cm...@0x7fff78eb01d0) at Cursor.cpp:315
#25 0x0064e204 in lyx::LyXFunc::dispatch (this=0x3076740,
c...@0x7fff78eb01d0) at LyXFunc.cpp:1712
#26 0x0064fb85 in lyx::LyXFunc::processKeySym (this=0x3076740,
keys...@0x7fff78eb0330, state=lyx::ControlModifier) at LyXFunc.cpp:389
#27 0x00b33304 in lyx::frontend::GuiWorkArea::processKeySym
(this=, k...@0x7fff78eb0330,
mod=lyx::ControlModifier) at GuiWorkArea.cpp:462
#28 0x00b385bc in lyx::frontend::GuiWorkArea::keyPressEvent
(this=0x3781280, ev=0x7fff78eb0b90) at GuiWorkArea.cpp:919
#29 0x003ae35d5f15 in QWidget::event () from /usr/lib64/libQtGui.so.4
#30 0x003ae38cdd86 in QFrame::event () from /usr/lib64/libQtGui.so.4
#31 0x003ae39538ad in QAbstractScrollArea::event () from
/usr/lib64/libQtGui.so.4
#32 0x00b36d94 in lyx::frontend::GuiWorkArea::event
(this=0x3781280, e=0x3076878) at GuiWorkArea.cpp:

Re: LyX 1.6.1 crash when pasting a branch inset

[Jürgen Spitzmüller]

Vincent van Ravesteijn - TNW wrote:
> Confirmed.

The assert or the fix?

Jürgen

Re: LyX 1.6.1 crash when pasting a branch inset

[rgheck]

Vincent van Ravesteijn - TNW wrote:
 

  

Whenever I copy/kill and past a branch inset LyX dies with the error message

../../../src/support/lassert.cpp(21): ASSERTION false VIOLATED
IN ../../src/insets/Inset.cpp:137 terminate called after throwing
an instance of 'lyx::support::ExceptionMessage'
 what():  Inset::buffer_ member not initialized!
LyX Code: 36 name: Branch

in ~/.xsession-errors.

I use LyX 1.6.1 on Debian with a set of documents organised as
master with childs for each chapter (there are some branch
oddities in this setup but this might be unrelated).

Is this a known bug that will be fixed in 1.6.2 ?




Confirmed.

  
What were you confirming? Just doing the obvious sort of thing, I can't 
reproduce under svn.


rh

RE: LyX 1.6.1 crash when pasting a branch inset

[Vincent van Ravesteijn - TNW]

 

> Whenever I copy/kill and past a branch inset LyX dies with the error message
>
>../../../src/support/lassert.cpp(21): ASSERTION false VIOLATED
>IN ../../src/insets/Inset.cpp:137 terminate called after throwing
>an instance of 'lyx::support::ExceptionMessage'
>  what():  Inset::buffer_ member not initialized!
>LyX Code: 36 name: Branch
>
>in ~/.xsession-errors.
>
>I use LyX 1.6.1 on Debian with a set of documents organised as
>master with childs for each chapter (there are some branch
>oddities in this setup but this might be unrelated).
>
>Is this a known bug that will be fixed in 1.6.2 ?
>

Confirmed.

Vincent

Re: LyX 1.6.1 crash when pasting a branch inset

[Jürgen Spitzmüller]

Guenter Milde wrote:
> Is this a known bug that will be fixed in 1.6.2 ?

Not that I know (although we have fixed many crashes and asserts, so this one 
might have been resolved en passant).

In any case, I cannot reproduce with 1.6.3svn (but probably I need a more 
detailed recipe).

BTW note that you faced an assertion, not a crash. In release mode, assertions 
do not shut down LyX.

Jürgen

LyX 1.6.1 crash when pasting a branch inset

[Guenter Milde]

Whenever I copy/kill and past a branch inset LyX dies with the error message

../../../src/support/lassert.cpp(21): ASSERTION false VIOLATED IN 
../../src/insets/Inset.cpp:137
terminate called after throwing an instance of 'lyx::support::ExceptionMessage'
  what():  Inset::buffer_ member not initialized!
LyX Code: 36 name: Branch

in ~/.xsession-errors.

I use LyX 1.6.1 on Debian with a set of documents organised as master
with childs for each chapter (there are some branch oddities in this setup
but this might be unrelated).

Is this a known bug that will be fixed in 1.6.2 ?

Re: Compiling lyx-1.6.1 on a Linux-machine

[rgheck]

pascal.voll...@nexgo.de wrote:

Hello,

After having installed 1.6.1 successfully on a Windows machine and being very happy with the result I wanted to do the same for my Linux-machine at home. Now, I get a compiler error and I do not yet understand what is going wrong. 


These are basically the steps I follow.

extract qt-x11-opensource-src-4.4.3.tar.gz
./configure
gmake
gmake install
extract lyx-1.6.1.tar.gz
./configure --with-qt4-dir=
make

  

Is there some particular reason you're compiling qt yourself?


and here comes the compiler error:

 g++ -DHAVE_CONFIG_H -I. -I.. "-DBOOST_USER_CONFIG=" -I../boost -O2 
-MT named_slot_map.lo -MD -MP -MF .deps/named_slot_map.Tpo -c 
libs/signals/src/named_slot_map.cpp -o named_slot_map.o
libs/signals/src/named_slot_map.cpp:22: error: 'stored_group' was not declared 
in this scope
libs/signals/src/named_slot_map.cpp:22: error: template argument 1 is invalid
(..)

I use gcc version 4.1.0.

Any idea what could be broken?

  

No. That's declared in one of the included files.

rh

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Lance Simmons]

On Mon, Feb 23, 2009 at 5:18 AM, Helge Hafting  wrote:
>
> So it is possible to have LyX 1.6.1, and everything else from stable.

I have much experience mixing stable and testing and unstable and experimental.
Too much experience.  I want a pure stable installation for the next year or
so, so I can ignore system administration and do my own work, which is not
computer-related.  I've had good luck in the past installing stable Debian and
having a year or two of peace and quiet.  Testing and unstable are like
cigarettes and alcohol.  They seem harmless enough, but for people with
addictive personalities, they lead to trouble!

-- 
Lance Simmons

Compiling lyx-1.6.1 on a Linux-machine

[pascal . vollmer]

Hello,

After having installed 1.6.1 successfully on a Windows machine and being very 
happy with the result I wanted to do the same for my Linux-machine at home. 
Now, I get a compiler error and I do not yet understand what is going wrong. 

These are basically the steps I follow.

extract qt-x11-opensource-src-4.4.3.tar.gz
./configure
gmake
gmake install
extract lyx-1.6.1.tar.gz
./configure --with-qt4-dir=
make

and here comes the compiler error:

 g++ -DHAVE_CONFIG_H -I. -I.. "-DBOOST_USER_CONFIG=" -I../boost -O2 
-MT named_slot_map.lo -MD -MP -MF .deps/named_slot_map.Tpo -c 
libs/signals/src/named_slot_map.cpp -o named_slot_map.o
libs/signals/src/named_slot_map.cpp:22: error: 'stored_group' was not declared 
in this scope
libs/signals/src/named_slot_map.cpp:22: error: template argument 1 is invalid
(..)

I use gcc version 4.1.0.

Any idea what could be broken?

Thanks in advance
Pascal





Pascal Vollmer
Email: pascal.voll...@ieee.org

Erwischt! Bei Arcor sehen Sie die besten Promi-Bilder riesengroß und in 
Top-Qualität. Hier finden Sie die schönsten Schnappschüsse auf dem roten 
Teppich, lernen die Frauen des Womanizers Boris Becker kennen und schauen den 
Royals ins Wohnzimmer. Viel Spaß auf Ihrer virtuellen Reise durch die Welt der 
Stars und Sternchen: http://vip.arcor.de.

lyx 1.6.1 not running

[Srinivas Nedunuri]

Just installed Lyx 1.6.1 on my Windows XP, using the "alternative" installer
(small). The installation went through OK, but when I launch it, nothing
happens. I can see a lyx.exe process but that's about it. There's no Lyx app
running in the Task Manager Applications tab. I tried ending the process and
relaunching but the same thing happens. Its been going for a good 5-10 
minutes now

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Helge Hafting]

Lance Simmons wrote:

On Wed, Feb 18, 2009 at 11:36 AM, Richard Heck 
wrote:

Better yet, upgrade to 1.5.7 (I think that's the number...last
1.5.x anyway), which can read 1.6. docs.


The reason the issue about 1.5.5 came up is my switching from Debian
unstable to Debian stable (now that there's a new stable Debian
release).  If I'm going to switch back to unstable Debian, or a
stable/non-stable mix, I might as well keep LyX 1.6.1.


You are aware that it is possibly to install LyX 1.6.1 (and perhaps
a _few_ dependant packages) from unstable, without pulling in everything
else that is new in unstable?

So it is possible to have LyX 1.6.1, and everything else from stable.

Helge Hafting

Re: Rotating floats doesn't work after upgrade to 1.6.1 on MAC OS X

[Bennett Helm]

On Fri, Feb 20, 2009 at 7:06 AM, Juergen Spitzmueller
 wrote:
> christiaan pauw wrote:
>
>> Indeed!
>> "texhash" in users mode doesn't work but it does work in administrator
>> mode (I used sudo).
>
> Good. Note that you always must run "texhash" as administrator if you
> install new files into the main TEXMF tree. AFAIR this is not needed (on
> the Mac) if you copy the files to /library/texmf instead.

That's right.

Bennett

Re: Rotating floats doesn't work after upgrade to 1.6.1 on MAC OS X

[Juergen Spitzmueller]

christiaan pauw wrote:

> Indeed!
> "texhash" in users mode doesn't work but it does work in administrator
> mode (I used sudo).

Good. Note that you always must run "texhash" as administrator if you
install new files into the main TEXMF tree. AFAIR this is not needed (on
the Mac) if you copy the files to /library/texmf instead.

Jürgen

Re: Rotating floats doesn't work after upgrade to 1.6.1 on MAC OS X

[christiaan pauw]

Indeed!
"texhash" in users mode doesn't work but it does work in administrator mode
(I used sudo). After running "texhash" in administrator  mode "kpsewhich"
returns ./rotfloat.sty from anywhere and not just from the directory in
which the file is located. I tried my LyX document and it worked.

Thanks a lot for your help

regards
Christiaan

2009/2/20 Juergen Spitzmueller 

> christiaan pauw wrote:
>
> > It returns
> >
> > ./rotfloat.sty
>
> Does it help if you run "texhash" (in administrator mode)?
>
> Jürgen
>
>

Re: Rotating floats doesn't work after upgrade to 1.6.1 on MAC OS X

[Juergen Spitzmueller]

christiaan pauw wrote:

> It returns
> 
> ./rotfloat.sty

Does it help if you run "texhash" (in administrator mode)?

Jürgen

Re: Rotating floats doesn't work after upgrade to 1.6.1 on MAC OS X

[christiaan pauw]

Hi
It returns

./rotfloat.sty

Does that mean anything?

regards
Christiaan

2009/2/18 Juergen Spitzmueller 

> christiaan pauw wrote:
>
> > I can see rotfloat.sty in the list of styles under Tool>Tex Information.
>
> what does "kpsewhich rotfloat.sty" return?
>
> Jürgen



>
> Hi
>>
> I recently upgraded to 1.6.1. I have a document with a number of tables in
> floats rotated sideways. It used to work fine in LyX1.5.  Now I cannot
> produce pdf output anymore. The error message reads
>
> "LaTeX Error: File `rotfloat.sty' not found." I cannot find a way to
> update packages with texlive (and TeXShop) in Mac OS X like one does with
> MikTex on Windows so  I searched the internet and manually copied rotfloat.sty
> to:   /usr/local/texlive/2007basic/texmf-dist/tex/latex/rotfloat/rotfloat
> .sty
>
>
> I can see rotfloat.sty in the list of styles under Tool>Tex Information.
>

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[M-L]

On Fri, 20 Feb 2009, Lance Simmons engaged keyboard and shared this with us 
all:
>--} On Thu, Feb 19, 2009 at 5:25 PM, Robert Orr 
> wrote: --} >
>--} > Why do you want to downgrade?
>--}
>--} Last week Debian released its new stable version, Lenny.  Debian stable
> is rock --} solid; all release-critical bugs have been worked out.  The
> packages are --} somewhat older than Debian testing or unstable, but they
> all work, and they all --} work together with the other stable packages. 
> Lenny has LyX 1.5.5. --}

Great script Lance, thanks, but I had already done it manually just by 
stripping everything to the "\begin_body" section.

I don't know how I got LyX 1.6.1 but think that my sources list was still 
programmed to testing and apt-get upgraded, before I changed it to Lenny. I 
usually keep this system as testing without change, but have to have it 
reliable for a few months and might then change back to testing. LyX 1.6.1 
didn't work very well at all, a few glitches. 

I wish I had your script before I changed all the documents I'd worked on with 
1.6.1

Thanks for that.
Charlie
-- 
Registered Linux User:- 329524
***
People with opinions just go around bothering one another. -- THE BUDDHA

***
Debian, just the best way to create magic
___

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Lance Simmons]

On Thu, Feb 19, 2009 at 5:25 PM, Robert Orr  wrote:
>
> Why do you want to downgrade?

Last week Debian released its new stable version, Lenny.  Debian stable is rock
solid; all release-critical bugs have been worked out.  The packages are
somewhat older than Debian testing or unstable, but they all work, and they all
work together with the other stable packages.  Lenny has LyX 1.5.5.

-- 
Lance Simmons

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Robert Orr]

Why do you want to downgrade?    



What influenced you to go back to 1.5.5?




--- On Thu, 2/19/09, rgheck  wrote:

From: rgheck 
Subject: Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?
To: "Lance Simmons" 
Cc: lyx-users@lists.lyx.org
Date: Thursday, February 19, 2009, 5:41 PM

Lance Simmons wrote:
> I'm sure there are much better ways to do this, and plenty of
> pitfalls to the way I did it, but it converted about 600 LyX files
> to the 1.5.x format, without any apparent problems, and in about 5
> seconds.  I checked many files in different directories at random,
> and haven't found any problems.  If I ever do find problems, I have
> the old documents backed up on various media, so I think I'm set.
>
>   
Are scripts great?!

rh




  

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[rgheck]

Lance Simmons wrote:

I'm sure there are much better ways to do this, and plenty of
pitfalls to the way I did it, but it converted about 600 LyX files
to the 1.5.x format, without any apparent problems, and in about 5
seconds.  I checked many files in different directories at random,
and haven't found any problems.  If I ever do find problems, I have
the old documents backed up on various media, so I think I'm set.

  

Are scripts great?!

rh

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Lance Simmons]

On Wed, Feb 18, 2009 at 11:15 AM, Vincent van Ravesteijn - TNW
wrote:
>
>>How can I convert the 1.6.1 documents to the older 1.5.5 format?
>
> In LyX 1.6.1, choose File->Export->LyX 1.5.x

I did a shell script to convert all my LyX documents to 1.5.x.  I
had about 600 LyX documents with many different formats, going back
several years to LyX 1.3.  Now they are all in the same format.

First a script:

  #!/bin/sh

  # filename of script is ~/bin/lyxconvert

  python -tt /usr/share/lyx/lyx2lyx/lyx2lyx -t 276 "$1" > /tmp/temp.lyx

  mv -f /tmp/temp.lyx "$1"

  exit 0

Then:

  find ./ -name '*.lyx' -execdir ~/bin/lyxconvert '{}' ';'

Then:

  uninstall LyX 1.6.1, install Lyx 1.5.5

Now all the packages installed on my machine are Debian stable and
all my LyX documents are in 1.5.x format.  I'm a happy camper.

I'm sure there are much better ways to do this, and plenty of
pitfalls to the way I did it, but it converted about 600 LyX files
to the 1.5.x format, without any apparent problems, and in about 5
seconds.  I checked many files in different directories at random,
and haven't found any problems.  If I ever do find problems, I have
the old documents backed up on various media, so I think I'm set.

This seemed like it might be useful for converting all one's LyX
files to a single format, so please let me know if there are obvious
errors in what I did.

-- 
Lance Simmons

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Pavel Sanda]

Sven Hoexter wrote:
> I hope to finish my Debian Application soon[1] so that I can provide again
> LyX packages on backports.org for the current Debian stable release.
> Will take some time though to get this all sorted out and done.

i dont know much about the exact debian policy for updating packages
but from the users point of view it would be good if debian stable release
contain always the last member of stable releases. in a way its better to have
lyx 1.5.7 in stable distro than lyx 1.6.1.

pavel

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Sven Hoexter]

On Wed, Feb 18, 2009 at 02:13:13PM -0600, Lance Simmons wrote:
> On Wed, Feb 18, 2009 at 11:36 AM, Richard Heck 
> wrote:
> >
> > Better yet, upgrade to 1.5.7 (I think that's the number...last
> > 1.5.x anyway), which can read 1.6. docs.
> 
> The reason the issue about 1.5.5 came up is my switching from Debian
> unstable to Debian stable (now that there's a new stable Debian
> release).  If I'm going to switch back to unstable Debian, or a
> stable/non-stable mix, I might as well keep LyX 1.6.1.

I hope to finish my Debian Application soon[1] so that I can provide again
LyX packages on backports.org for the current Debian stable release.
Will take some time though to get this all sorted out and done.

Oh and yes the freeze length for Lenny and the start point has been
suboptimal for the LyX packages in Debian.

Sven

[1] May or June is something that's realistic. 
-- 
If God passed a mic to me to speak
I'd say stay in bed, world
Sleep in peace
   [The Cardigans - 03:45: No sleep]

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Lance Simmons]

On Wed, Feb 18, 2009 at 11:36 AM, Richard Heck 
wrote:
>
> Better yet, upgrade to 1.5.7 (I think that's the number...last
> 1.5.x anyway), which can read 1.6. docs.

The reason the issue about 1.5.5 came up is my switching from Debian
unstable to Debian stable (now that there's a new stable Debian
release).  If I'm going to switch back to unstable Debian, or a
stable/non-stable mix, I might as well keep LyX 1.6.1.

-- 
Lance Simmons

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[James C. Sutherland]

On Feb 18, 2009, at 10:15 AM, Vincent van Ravesteijn - TNW wrote:




I've switched from Debian unstable to the new stable release, but now
now I have a few dozen LyX 1.6.1 documents that LyX 1.5.5 says it
cannot convert.

How can I convert the 1.6.1 documents to the older 1.5.5 format?


In LyX 1.6.1, choose File->Export->LyX 1.5.x





Or install 1.5.7, which can read 1.6.x documents.

Re: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Richard Heck]

Vincent van Ravesteijn - TNW wrote:
 
  

I've switched from Debian unstable to the new stable release, but now
now I have a few dozen LyX 1.6.1 documents that LyX 1.5.5 says it 
cannot convert.


How can I convert the 1.6.1 documents to the older 1.5.5 format?



In LyX 1.6.1, choose File->Export->LyX 1.5.x

  
Better yet, upgrade to 1.5.7 (I think that's the number...last 1.5.x 
anyway), which can read 1.6. docs.


rh

RE: Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Vincent van Ravesteijn - TNW]

 
>I've switched from Debian unstable to the new stable release, but now
>now I have a few dozen LyX 1.6.1 documents that LyX 1.5.5 says it 
>cannot convert.
>
>How can I convert the 1.6.1 documents to the older 1.5.5 format?

In LyX 1.6.1, choose File->Export->LyX 1.5.x

>--
>Lance Simmons

Vincent

Howto downgrade LyX 1.6.1 documents to LyX 1.5.5 documents?

[Lance Simmons]

I've switched from Debian unstable to the new stable release, but now now I
have a few dozen LyX 1.6.1 documents that LyX 1.5.5 says it cannot convert.

How can I convert the 1.6.1 documents to the older 1.5.5 format?

-- 
Lance Simmons

Re: Rotating floats doesn't work after upgrade to 1.6.1 on MAC OS X

[Konrad Hofbauer]

christiaan pauw wrote:

Hi Everybody
I recently upgraded to 1.6.1. I have a document with a number of tables in
floats rotated sideways. It used to work fine in LyX 1.5.  Now I cannot
produce pdf output anymore. The error message reads
"LaTeX Error: File `rotfloat.sty' not found." I cannot find a way to update
packages with texlive (and TeXShop) in Mac OS X like one does with MikTex on
Windows so  I searched the internet and manually copied rotfloat.sty to:
  /usr/local/texlive/2007basic/texmf-dist/tex/latex/rotfloat/rotfloat.sty


If you have a solid internet connection (i.e., you are fine with 
downloading 1GB), you could also just trash your old latex installation 
and install <http://www.tug.org/mactex/>.


/Konrad

P.S. That said, what you try to do should work nevertheless.