Dear LyX Experts, I am stuck with a problem that seems to have been sorted out a few years ago (ticket 3004). The case was about lyx not being able to import a .nw (noweb) file, previously exported by lyx from a respective .lyx file (to test the noweb import function). I asked help from the lyx-users list some days ago but nobody there seems to be familiar with this subject.
The result of the import test was reported in ticket 3004 to be a garbled .lyx file, and that's just what I have encountered (= "layout Standard" where I would expect "layout Scrab"). The ticket mentions that a particular user preferences were the culprit, but the details have been lost in the mists of time. I am currently running Debian (Squeeze) and Lyx 1.6.4, installed from .deb packages, in two machines. They both share this "feature". I have tried out inter alia /usr/share/lyx/examples/Literate.lyx, converted it to .nw with lyx, then back with $tex2lyx -n -f Literate.nw (using lyx and straight from the command line, also with option -c "literate-article"). No luck... I checked that the tex2lyx binary was replaced when updating to 1.6.4 (from the file's date, he import has not worked properly for me in earlier lyx versions either). I have not noticed anything amiss with the .nw files with emacs. When I look at the imported .lyx files it seems that tex2lyx does not recognise "<<chunkname>>=", signalling the start of the code chunk, and act accordingly (=apply scrap style to the code chunks). That kind of code seems to be in place, however, in http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/src/tex2 lyx/text.cpp. To my knowledge I have not fooled around with the lyx's literate format preferences, and when I checked them they were defaults (peeked also in ~/.lyx/preferences, no lines concerning tex2lyx there (lyx reports that it uses "tex2lyx -n -f $$i $$o" when I look via menus). So I suspect that the root of the problem might lie with tex2lyx. http://wiki.lyx.org/Tools/Noweb discusses many tricky issues but not this one. Sorry to trouble you about something that might turn out to be a simple error, but the solution evades me. Thanks in advance, Arto
