Am 06.12.2015 um 13:52 schrieb Georg Baum:

http://www.lyx.org/trac/changeset/d879599cec4902a1a3ea7aa7a8d7d24815701036/lyxgit
or

http://www.lyx.org/trac/changeset/42536a561606290ebdb90c46badbb451487f5293/lyxgit

None of these did change a path.

they did:

-\origin /systemlyxdir/doc/
+\origin unavailable

- Do not change the paths in general if the files can be found using the
relative paths. Has the additional benefit that this is also the wanted
behaviour if I copy a whole directory of LyX files (including referenced
graphics) to a new location. Disadvantage would be that the machinery does
now depend on the presence of external files, and it is not guaranteed that
the file that is found is the correct one.

I would prefer that but don#t know enough about the background of such a change.

That is not true. I know why this doesn't work. That is why the
installer exists: you need to specify the PATH variable linking to Perl
(e.g for texindy), Python (for our scripts), ImageMagick which needs
also Ghostscript, rsvg and/or Inkscape.

If this is the only issue then you can run LyX from within MSVC easily:
You can specify environment variables for debugging in MSVC, so you can set
the correct PATH once in MSVC and then save a lot of time by not requiring
installation for each tiny source change. I don't know by heart how to do
it, but I can look it up if you want.

Well, nobody can tell me how to do this.

regards Uwe

Reply via email to