Am Donnerstag, 7. März 2019 16:18:54 CET schrieb Patrick Dupre <pdu...@gmx.com>: > Hello, > > I also tried to run configure.py manually (see the attached configure.log > generated). > Then I copied this file into the home directory, and loaded lyx. > But lyx immediately generates a new configure.log file (which is shorter: > it stops at > DEBUG: Failed to remove file texput.log) > > Thank for your help.
configure should create following files:
lyxrc.defaults
preferences
bbxFiles.lst cbxFiles.lst lyxmodules.lst textclass.lst
bibFiles.lst clsFiles.lst packages.lst xtemplates.lst
bstFiles.lst lyxciteengines.lst styFiles.lst
The log-output shows:
WARNING: Failed to find tex2lyx on your system.
This means, that your PATH is not set correctly. 'tex2lyx.exe' is part of lyx,
should be in the same dir as 'lyx.exe'.
DEBUG: Failed to remove file chklatex.log
this repeats for all .lst file ...
which from my POV shows, that you don't have the privilege to write into the
user dir.
Kornel
>
> >
> > Am Dienstag, 5. März 2019 20:44:43 CET schrieb Patrick Dupre
> > <pdu...@gmx.com>:
> > > Hello,
> > >
> > > Do you think that it is an issue with Miktex or Lyx.
> >
> > No, I think it has to do with your Windows version.
> >
> > > Lyx has been installed as Administrator with shared access.
> > > Would be try in single user ?
> >
> > That should not make any difference. Lyx is _executed_ under the permissions
> > of the user. And the created files should respect this.
> > No, what puzzles is that
> > 1.) either lyx could create a file but could not delete it afterwards
> > or
> > 2.) lyx detected a non-existant file (which then of course cannot be
> > deleted)
> >
> > I am _not_ a Windows expert though.
> >
> > >
> > > Thank.
> >
> > Kornel
> >
> > P.S.
> > Please reply to list, maybe someone else knows what is going on.
> >
> >
>
signature.asc
Description: This is a digitally signed message part.
