On Mon, Oct 12, 2015 at 04:49:07AM +0200, Stephan Witt wrote: > Am 12.10.2015 um 04:15 schrieb Scott Kostyshak <skost...@lyx.org>: > > > On Sun, Oct 11, 2015 at 10:51:17AM +0200, Stephan Witt wrote: > >> Am 11.10.2015 um 00:01 schrieb Scott Kostyshak <skost...@lyx.org>: > >> > >>> On Sat, Oct 10, 2015 at 09:26:34PM +0200, Stephan Witt wrote: > >>>> Am 10.10.2015 um 20:40 schrieb Scott Kostyshak <skost...@lyx.org>: > >>>> > >>>>> On Sat, Oct 10, 2015 at 01:16:42PM -0500, jken...@ssc.wisc.edu wrote: > >>>>>>> On Sat, Oct 10, 2015 at 08:40:28AM -0500, jken...@ssc.wisc.edu wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>>> On Thu, Oct 08, 2015 at 03:32:48PM +0200, Stephan Witt wrote: > >>>>>>>>>> This is really interesting. > >>>>>>>>>> > >>>>>>>>>> LyX 2.2.0 fixes some problem on latest Mac OS "El Capitan". > >>>>>>>>>> I guess the fix is there because of the change to Qt5. > >>>>>>>>> > >>>>>>>>> John, was the "can't preview PDF" issue that users of El Capitan > >>>>>>>> have > >>>>>>>>> reported also fixed with the 2.2.0 snapshot? > >>>>>>>>> > >>>>>>>>> Scott > >>>>>>>> > >>>>>>>> Yes, that problem seems to be fixed. I tried command-R and > >>>>>>>> command-T, > >>>>>>>> and both work, and clicking the view icon works too. > >>>>>>> > >>>>>>> Good to know. > >>>>>>> > >>>>>>>> I have SIP disabled -- should I re-enable SIP and see if it still > >>>>>>>> works? > >>>>>>> > >>>>>>> No, not now at least. I would have asked you to re-enable SIP, confirm > >>>>>>> that the problem exists with 2.1.4 and that the problem does not exist > >>>>>>> with LyX 2.2dev. I don't want you to spend the time to do that at this > >>>>>>> point, unless you are curious yourself. > >>>>>> > >>>>>> This of course made me curious (and as far as time is concerned, the > >>>>>> work you guys have done has already saved me lots and lots of time). > >>>>>> SIP doesn't seem to have anything to do with either the preview > >>>>>> problem or the palette problem. The palette problem exists in LyX > >>>>>> 2.1.4 under El Capitan, and the problem disappears in 2.2.0dev (April > >>>>>> 14, 2014). > >>>>> > >>>>> Great, thanks for testing! > >>>>> > >>>>>> I can't reproduce the preview PDF problem in either LyX version under > >>>>>> El Capitan. > >>>>> > >>>>> Good to know. This means we need to find a tester who does have the > >>>>> preview problem to see if 2.2.0dev makes things better. > >>>> > >>>> In theory the problem with SIP is the mismatch of the PATH setting in > >>>> preferences and the real file system. "In the past" the MacTeX installer > >>>> puts the things to /Library/TeX/texbin and adds sym links to /usr/bin > >>>> to reduce problems with missing PATH settings. With SIP enabled > >>>> these sym links are forbidden and will be removed. So the program has > >>>> to add /Library/TeX/texbin to the PATH explicitly. This has to be done > >>>> within the LyX binary (the user preferences) because of the 2nd "security > >>>> feature" - the settings in .profile of the user are not used for programs > >>>> launched from the desktop icon (e.g. the so called dock). This makes the > >>>> MacTeX installation invisible for LyX. > >>>> > >>>> The 2.1.4 binary is distributed with /Library/TeX/texbin in PATH as setup > >>>> default value. But users who are doing an upgrade doesn't benefit from > >>>> this > >>>> because of the settings migration. LyX has no good mechanism to adjust > >>>> the > >>>> settings on upgrade to some new version. This may be improved within the > >>>> 2.2.0 release, but I don't know of an acceptable way. > >>> > >>> Thanks for the explanation. By upgrade do you mean ugrade of LyX or OS > >>> X? I don't actually understand what it means to upgrade LyX. Does it > >>> mean to use the old user directory with the new version? > >> > >> Yes, I meant the LyX upgrade. If one does the "install" of a new version > >> one only copies the contents from the disk image to the current programs > >> folder (this is /Applications on Mac OS X). LyX compares the timestamp of > >> it's executable and the lyxrc file on start and runs configure.py if the > >> executable is the newer one or lyxrc is missing. > >> > >> If you've updated e.g. from 2.1.3 to 2.1.4 the lyxrc should be there and > >> the preferences are read and possibly migrated by LyX's scripts. If you're > >> running 2.2.x the first time a copy of the 2.1 preferences is made by > >> configure.py (only on the Mac platform because of complaints of some Linux > >> developers) and the migration is done on the fresh copy of course. > > > > If I understand then, 2.2 will not solve the problem then if the user > > previously had installed 2.1.4 because you describe the preferences file > > is copied. Is that right? > > > >> ATM, there is no mechanism to adjust parts of the PATH environment > >> the user has in the preferences by configure.py. > > > > I suppose the only way would be to update the preferences format and use > > prefs2prefs.py? > > Perhaps. I didn't had a good idea until now. I have to give it a try. > To complicate the matter it's a platform dependent issue. > > >>> So if someone does a fresh installation of LyX 2.2.0dev on El Capitan > >>> there should be no problem? > >> > >> Yes, this should be true for both 2.1.4 and 2.2.0. The lyxrc.dist.in > >> of 2.1.4 already contains the directory "/Library/TeX/texbin" in PATH. > >> The TeX distribution should be found and usable by LyX this way. > > > > Ah so the reason why it appeared that 2.2.0 solved the problem was > > because people with El Capitan installing LyX were doing a fresh > > installation? > > I'm not sure about that. If the user changes the PATH preference manually > to include /Library/TeX/texbin too it solves the problem for this user. > Depending on the work flow it's solved for both versions or the current one. > For doing a "fresh install" you need to remove the preferences manually > at file system level or to use a new account. > > (Side note: Switching to a new hardware is no guarantee for having a new user. > Usually the switch is accompanied with the use of the migration utility and > with it's help the users and the installed non-system-software is copied to > the new hardware while installing the OS - it's magic and it works > fantastically.) > > As John said it's ok for him on both versions now. Probably he did the change > in 2.1.4 before trying 2.2.0. So it is a false positive, probably. > It isn't related to the LyX 2.2.0 upgrade.
Thanks for the explanations, Stephan. Scott
