Some notes to self (and JMarc of course :)

I've just spent an evening doing some real work with LyX, so I tried out the Windows version of LyX 1.3.x installed at
C:\Program Files\LyX.


As a result
* we now have a new version of clean_dvi.py,
* I've discovered that my intermediate dvi format must still
  have a .dvi extension (rather than, say, .dvi2) and
* I've also discovered that
  C:\Program Files\LyX\Resources\lyx\configure *must* have
  unix-style line endings or common versions of sed (mine, for
  example :) get horribly confused by chkconfig.sed.

There's nothing like trying things out for real, is there? I even managed to get some of that real work done, though not as much as I might have.

A couple of bugs/potential problems still remain:

Leaving the logic to check whether a "file name has spaces" in the file browser means that I can't change my bind file in the preferences dialog. (C:\Program Files\LyX\Resources\lyx\bind\emacs.bind)

Also, I found that we are unable to launch any executables as
C:\Program Files\LyX\bin\foo.exe because the executable cannot be quoted. Hence the new version of clean_dvi.py on the wiki.


Yes, Windows is weird.

In general, we should add LyX\bin to the PATH and simply invoke foo.exe. Not sure that this is a problem in practice (the PATH already contains the directory, but we may try and invoke stuff with an absolute path).

Angus



Reply via email to