Michael Schmitt wrote: > Dear Angus, > > AFAICS, package.tar.gz is not a patch against LyX 1.3 or 1.4, right?
Of course not. It's an attempt to define the various paths that LyX needs to operate in a way that makes sense on the various operating systems. > Do you also have a recipe on how to integrate your package into LyX 1.3? No. It's a work in progress. It's also Christmas and I would like to have a bit of a life... > Michael Michael, I think that the quickest, easiest solution for now is to apply the attached patch to a clean 1.3.x tree. I believe that it is very similar to the changes taht you have in your own, personal tree. Note, however, the code in os_win32.C - homepath_ = GetEnvPath("HOMEDRIVE") + GetEnvPath("HOMEPATH"); + homepath_ = GetEnv("USERPROFILE"); + if (homepath_.empty()) { + string const homedrive = GetEnv("HOMEDRIVE"); + string const homepath = GetEnv("HOMEPATH"); + homepath_ = internal_path(homedrive + homepath); + } >From the post '"HOME" on Windows?', 20 Dec: ------------------------------------------------------------------------ On *nix we specify "HOME" with homepath_ = GetEnvPath("HOME"); On Windows, where $HOME doesn't exist, we currently use: homepath_ = GetEnvPath("HOMEDRIVE") + GetEnvPath("HOMEPATH"); Trouble is, this doesn't seem very robust. The lyx_init.txt output that I posted earlier this morning indicates that HOMEDRIVE=C: HOMEPATH=\ LOGNAME=Angus USERNAME=Angus USERPROFILE=C:\Documents and Settings\Angus ------------------------------------------------------------------------ This explains the current result of C//.lyx-136cvs for your .lyx dir (you could always have started 'lyx -userdir foo'...) I'd hope that you'll now get the equivalent of C:/Documents and Settings/Angus/.lyx-136cvs If not, I'm sure that you can get something similar to work. Hard coding, even... There is no warranty associated with the attached patch. It will *not* be applied to the LyX sources. -- Angus
win32_31Dec04.diff.bz2
Description: BZip2 compressed data