On Mon, Jun 26, 2006 at 06:39:20PM +0200, Jean-Marc Lasgouttes wrote: > - what shall we do wrt cygwin (Enrico, I know it is the 137th time I > ask this question, sorry).
ATM the only problem is with external_path() returning a path-style depending on the checkbutton about path-styles for latex. I am going to put together a patch fixing this issue and at the same time renaming the misleading \cygwin_path_fix_needed switch. As I already said several times, cygwin itself has no problems with any path style (all posix functions deal with whatever style), but now it is sensible that external_path() returns windows-style paths, because it is used when a native windows API function is called (as done in the fonts patch by Joost, for example). The way I rearranged src/support/os_cygwin.C, any path style can be input from configuration files and/or the GUI and it always work right (I have been testing it for months now). Personally, I always patch LyX such that internal_path() returns windows-style paths (with forward slashes), too. This is because in this way I have no problems with native apps (the MikTeX tex4ht, for example) and accept the risk that a badly ported cygwin app thinks that a path is not absolute if it doesn't start with '/' (so far I have encountered none, tetex apart, of course). IMO, the kind of path-styles returned by internal_path() should be configurable, but I am not going to endorse this change and will keep it for my personal use. BTW it works for me. > - Reading of configuration now goes like this: LyX first reads the file > lyxrc.init (if it exists). If lib/configure.py is newer than Isn't this lyxrc.dist ? > either lyxrc.defaults, textclass.lst or packages.lst, it is re-run > before loading lyxrc.defaults and preferences. -- Enrico
