Re: #11483: Ver. 3.2.3 17 May 2018 -- Problem with inserting Graphics into Figure float when AVAST Anti virus is installed

[Jerry]

wישא ןמכםרצשאןםמ ?

On Wed, Feb 13, 2019 at 5:02 PM LyX Ticket Tracker  wrote:

> #11483: Ver. 3.2.3   17 May 2018   -- Problem with inserting Graphics into
> Figure
> float when AVAST Anti virus is installed
> -+--
>  Reporter:  dag  |   Owner:  lasgouttes
>  Type:  defect   |  Status:  closed
>  Priority:  normal   |   Milestone:
> Component:  general  | Version:  unspecified
>  Severity:  normal   |  Resolution:  worksforme
>  Keywords:   |
> -+--
> Changes (by spitz):
>
>  * keywords:  infoneeded =>
>  * status:  new => closed
>  * resolution:   => worksforme
>
>
> Comment:
>
>  Closing unless we get more information.
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor
>

test - ignore

[Jerry]

test - ignore

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Mar 3, 2016, at 5:34 PM, Guillaume Munch <g...@lyx.org> wrote:

> Le 03/03/2016 23:48, Jerry a écrit :
>> the behavior is the same--Reconfigure
>> runs quickly without and crashing luatex, and the Python command
>> appears to be running very long
>> 
> 
> I am not sure I understand.
> 
What I was trying to say is that LyX 2.1 behaves the same as 2.2. 2.1 and 2.2 
originally had the same path which I posted earlier and which had some (for my 
system) nonsensical stuff at the beginning. You inquired about whether I had 
changed the path for 2.1, which I had not. So I tested 2.1 with the original 
path (I couldn't find anywhere that I had tested 2.1 with respect to this 
problem). 2.1 behaved the same as 2.2 when it had the original path. Then I 
shortened the path for 2.1 just as I had for 2.2. Then I re-tested 2.1 and with 
the shortened path it behaves the same as 2.2 when its path was shortened. The 
testing for both 2.1 and 2.2 involved running Reconfigure and also running each 
version's Python script in a terminal.

I hope that is more clear.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 28, 2016, at 12:36 PM, Guillaume Munch <g...@lyx.org> wrote:

> 
> Le 27/02/2016 03:44, Jerry a écrit :
>> If I remove
>> /Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:
>> 
>> from the front of the PATH prefix and run Reconfigure, it runs in
>> 15-20 seconds. The first time I saw a luatex instance in Activity
>> Monitor but on subsequent runs it did not appear--I suppose it's
>> possible that it ran so quickly that Activity Monitor did not have a
>> chance to show it.
>> 
>> This of course has no effect on running
>> 
>> python -tt "/Applications/Words/LyXOuterFolder/LyX
>> 2.2.0beta2/LyX.app/Contents/Resources/configure.py"
>> --with-version-suffix=-2.2
>> --binary-dir="/Applications/Words/LyXOuterFolder/LyX
>> 2.2.0beta2/LyX.app/Contents/MacOS/"
>> 
>> from a terminal session which still stays on +Indexing TeX files...
>> for about 34 minutes.
>> 
> 
Sorry for the late reply. I was sick for a few days.

> Have you changed the value of PATH under both lyx 2.1 and 2.2 ?

No, only 2.2. 2.1 has the same path as 2.2 before I changed it.

The behavior seems the same under 2.1 as 2.2. I shortened the path in 2.1 as I 
described for 2.2 and the behavior is the same--Reconfigure runs quickly 
without and crashing luatex, and the Python command

python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.1.4/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.1 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.1.4/LyX.app/Contents/MacOS/"

appears to be running very long, paused on "+Indexing TeX files...". (It is 
running as I type this.)

Jerry
> 
> I still do not understand why the above makes the two issues seem
> unrelated whereas in your description below I get the impression that
> closing the luatex processes makes you skip the 34-minute waiting time.
> 
>>>>> The luatex process starts almost as soon as I hit Reconfigure.
>>>>> I Quit it (force quit not required) using Activity Monitor.
>>>>> LyX is unresponsive for about a minute, then the message
>>>>> 
>>>>> The system has been reconfigured. You need to restart LyX to
>>>>> make use of any updated document class specifications.
>>>>> 
>>>>> appears. At that point, LyX seems to operate normally. Also it
>>>>> operates normally after quitting and relaunching.
> 

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 26, 2016, at 8:54 AM, Stephan Witt <st.w...@gmx.net> wrote:

> 
>> Am 26.02.2016 um 16:41 schrieb Guillaume Munch <g...@lyx.org>:
>> 
>> Le 26/02/2016 10:08, Jerry a écrit :
>>> I don't know if you could infer that from my previous comments, but
>>> more or less what happens.
>> 
>> I could infer, more or less :)
>> 
>>> The luatex process starts almost as soon
>>> as I hit Reconfigure. I Quit it (force quit not required) using
>>> Activity Monitor. LyX is unresponsive for about a minute, then the
>>> message
>>> 
>>> The system has been reconfigured. You need to restart LyX to make use
>>> of any updated document class specifications.
>>> 
>>> appears. At that point, LyX seems to operate normally. Also it
>>> operates normally after quitting and relaunching.
>> 
>> This makes me think that we experienced the same issue. I would suggest to 
>> make sure that LyX does not call inadvertently the wrong luatex binary from 
>> your older texlive 2013 installation.
> 
> To achieve this please verify the PATH settings in LyX preferences. 
> They don’t have to match the PATH settings in Terminal. But this
> entry defines the PATH environment for external system commands.
> 
> Stephan

The PATH prefix in Preferences is

/Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:/opt/local/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/usr/sbin:/sbin

also
$ echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/texbin:/usr/local/bin:/usr/local/sbin:/Applications:/usr/local/ada/bin

Parsing the PATH prefix from Preferences a little...

On my system, I have a /Library/TeX/ *but there is no texbin in it*. However, 
it does contain this:
/Library/TeX/.scripts
/Library/TeX/Distributions
/Library/TeX/Documentation
/Library/TeX/Local -> symlink to /usr/local/texlive/texmf-local
/Library/TeX/Root ->  symlink to /usr/local/texlive/2013 which does contain a 
bin directory

I have a /usr/texbin which is a symlink to 
/usr/local/texlive/2013/bin/x86_64-darwin

I have no /sw/

I have no /opt/local/teTeX/

I have stuff in the remaining paths on this list.

If I remove 
/Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin: from the 
front of the PATH prefix and run Reconfigure, it runs in 15-20 seconds. The 
first time I saw a luatex instance in Activity Monitor but on subsequent runs 
it did not appear--I suppose it's possible that it ran so quickly that Activity 
Monitor did not have a chance to show it.

This of course has no effect on running 

python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"

from a terminal session which still stays on +Indexing TeX files... for about 
34 minutes.

Jerry

> 
>> If you're sure it is running the most recent version, then you could try to 
>> temporarily remove non-essential fonts and see if it gets quicker. (I do not 
>> know how to safely do this on your OS.)
> 

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 26, 2016, at 3:27 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:

> Le 26/02/2016 11:09, Jerry a écrit :
>> 
>> On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
>> 
>>> Le 25/02/2016 10:01, Jerry a écrit :
>>>> When I ran the Python command in a terminal, it proceeded quickly to 
>>>> "+Indexing TeX files..." and stayed there for about 34 minutes and 
>>>> everything else took no more than about a minute--just as before 
>>>> installing texlive-fonts-recommended.
>>> 
>>> Does this mean that running "python scripts/TeXFiles.py" is the command 
>>> that is slow?
>>> 
>>> JMarc
>> 
>> I don't know.
> 
> Could you try to run it like you ran by hand configure.py? To be frank I'd be 
> suprised to find out that the is the culprit, but the message "+Indexing TeX 
> files... " would point to that, unless I am mistaken.

Sorry for my lazy answer but I sort of didn't understand it. Running 
TeXFiles.py resulted in about 8-9 minutes spent in each of "Indexing files of 
type cls|sty|bst|bib". Processor usage by Python was low at around 4%. The rest 
of the remaining running time was negligible by comparison.
> 
> Also, there is a question you may already have answered. What happens if you 
> interrupt the running confogure.py with Ctrl+C? Does python give you a 
> backtrace showing where it is in the configure.py script?

I ran 

python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"

and hit Ctrl-C while "+Indexing TeX files..." was displayed. This gave the 
following backtrace:

+Indexing TeX files... 
^CTraceback (most recent call last):
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py", line 1612, in 
Traceback (most recent call last):
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/scripts/TeXFiles.py", line 107, in 

for root,path,files in os.walk(dir):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 276, in walk
names = listdir(top)
KeyboardInterrupt
rescanTeXFiles()
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py", line 1525, in 
rescanTeXFiles
tfp = cmdOutput("python -tt " + '"' + os.path.join(srcdir, 'scripts', 
'TeXFiles.py') + '"')
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py", line 76, in cmdOutput
output = pipe.stdout.read()
KeyboardInterrupt

Jerry

> JMarc
> 

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:

> Le 25/02/2016 10:01, Jerry a écrit :
>> When I ran the Python command in a terminal, it proceeded quickly to 
>> "+Indexing TeX files..." and stayed there for about 34 minutes and 
>> everything else took no more than about a minute--just as before installing 
>> texlive-fonts-recommended.
> 
> Does this mean that running "python scripts/TeXFiles.py" is the command that 
> is slow?
> 
> JMarc

I don't know.
Jerry

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 25, 2016, at 9:15 AM, Guillaume Munch <g...@lyx.org> wrote:

> Le 25/02/2016 00:54, Jerry a écrit :
>> On Feb 24, 2016, at 6:49 AM, Guillaume Munch <g...@lyx.org> wrote:
>> 
>>> I may have had a similar issue involving LuaTeX taking huge amounts
>>> of time to configure, at some point, with LyX 2.1 and TeXLive
>>> 2012/2013. It got solved by upgrading TeXLive. Jerry, do you have
>>> lots of fonts installed?
>> 
>> I'm not sure what you mean. If I take your question literally, the
>> answer is, it seems like everything I do on my computer results in
>> more fonts being installed, so I would say "yes," approximately 10^9.
>> I can be more precise if you like. OK--according to Font Book, there
>> are about 450 families and most have several fonts in each family.
>> 
> 
> This has been a factor for me in the past, though it's been a while ago,
> and I never really investigated the problem. When I had this problem I
> would simply force-close the luatex processes, then lyx would
> immediately continue as expected. If I infer correctly from your other
> messages, if you only force-close the luatex processes and not lyx then
> it continues normally?
> 
I don't know if you could infer that from my previous comments, but more or 
less what happens. The luatex process starts almost as soon as I hit 
Reconfigure. I Quit it (force quit not required) using Activity Monitor. LyX is 
unresponsive for about a minute, then the message 

The system has been reconfigured.
You need to restart LyX to make use of any
updated document class specifications.

appears. At that point, LyX seems to operate normally. Also it operates 
normally after quitting and relaunching.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 5:48 PM, Jerry <lancebo...@qwest.net> wrote:

> 
> On Feb 24, 2016, at 3:04 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> 
>> Le 24/02/2016 10:06, Jerry a écrit :
>>> I have two TeX installations. One I installed from the TUG (I think that's 
>>> what it's called) binary installer, probably TeXlive-2013, and the other as 
>>> part of MacPorts, macports.org; this -> "texlive-bin @2015_8+x11 (active)" 
>>> I think is relevant information for the active version from MacPorts. LyX 
>>> is seeing the MacPorts version since all of MacPorts is in /opt/local. The 
>>> TUG version from 2013 is at /usr/local/texlive/2013. I think that is 
>>> probably the whole wad since it is 3.4 GB. I have been thinking about 
>>> deleting it and relying on the well-maintained MacPorts version.
>> 
>> Do you have the package texlive-fonts-recommended installed?
> 
> I'm not sure how to tell, so I did the macports command, port...
> $ port installed texlive-fonts-recommended
> None of the specified ports are installed.
> 
> so I would say, "no". I also searched my system for 
> "texlive-fonts-recommended" and turned up only 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/tex/texlive-fonts-recommended
> which is a portfile which is not a "yes."
> 
> However, I suspect that texlive might install fonts in the places where OS X 
> normally expects to find fonts and not in /opt/local where the rest of 
> MacPorts lives--I have a question to the macports list about that.
> 
> FWIW, the OS X font manager indicates a number of entries for Latin Modern 
> and TeX Gyre. When I put T1 into the manager's filter field, four Latin 
> Modern families appear in the list. These _might_ have been installed by my 
> other TeXLive installation from 2013 which is in /usr/something. Of course 
> the basic Postscript fonts are also installed.
> 
>> 
>> Note that we should probably not require the ec fonts to be installed. This 
>> is very old code that I wrote at the time where these fonts were something 
>> modern. It seems that it was in LyX 0.11.17, which means that it was written 
>> almost 20 years ago :)
>> 
>> I would propose to remove this code and set the document encoding to T1 by 
>> default. This whole font encoding thing has to be rethought, but I am not 
>> competent in this respect.
>> 
>> JMarc
>> 
I checked with the list at MacPorts and found that the fonts are installed in 
the MacPorts directory, not the usual OS X font locations. So I installed 
texlive-fonts-recommended and ran Reconfigure. The running time was similar, 
luatex crashed as before, I got the dialog about the Python script not 
completing, I let it run, and instead of reporting immediately that the system 
was reconfigured and I had to re-start LyX, it took maybe 30 seconds before 
that happened.

When I ran the Python command in a terminal, it proceeded quickly to "+Indexing 
TeX files..." and stayed there for about 34 minutes and everything else took no 
more than about a minute--just as before installing texlive-fonts-recommended.

I've again attached the Python output.

Jerry

Last login: Thu Feb 25 01:21:42 on ttys002
Hello, Jerry. Your profile is at ~/.profile.
MBPro:~ jerrybauck$ python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"
checking for a Latex2e program...
+checking for "latex"...  yes
checking for a DVI postprocessing program...
+checking for "pplatex"...  no
checking for pLaTeX, the Japanese LaTeX...
+checking for "platex"...  yes
checking for a java interpreter...
+checking for "java"...  yes
checking for a perl interpreter...
+checking for "perl"...  yes
checking for a Tgif viewer and editor...
+checking for "tgif"...  no
checking for a FIG viewer and editor...
+checking for "xfig"...  no
+checking for "jfig3-itext.jar"...  no
+checking for "jfig3.jar"...  no
checking for a Dia viewer and editor...
+checking for "dia"...  no
checking for an OpenDocument drawing viewer and editor...
+checking for "libreoffice"...  no
+checking for "lodraw"...  no
+checking for "ooffice"...  no
+checking for "oodraw"...  no
+checking for "soffice"...  no
checking for a Grace viewer and editor...
+checking for "xmgrace"...  no
checking for a FEN viewer and editor...
+checking for "xboard"...  no
checking for a SVG viewer and editor...
+checking for "inkscap

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 6:49 AM, Guillaume Munch <g...@lyx.org> wrote:

> I may have had a similar issue involving LuaTeX taking huge amounts of
> time to configure, at some point, with LyX 2.1.3 and TeXLive 2012/2013.
> It got solved by upgrading TeXLive. Jerry, do you have lots of fonts
> installed?

I'm not sure what you mean. If I take your question literally, the answer is, 
it seems like everything I do on my computer results in more fonts being 
installed, so I would say "yes," approximately 10^9. I can be more precise if 
you like. OK--according to Font Book, there are about 450 families and most 
have several fonts in each family.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 2:32 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:

> Le 24/02/2016 05:18, Jerry a écrit :
>> +checking for default encoding (this may take a long time)
>> 
>> kpathsea: Running mktextfm ecrm1000
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
>> abbreviation  for ecrm1000.
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
>> mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
>> input ecrm1000
>> This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) 
>> (preloaded base=mf)
> 
> It looks like your installation is missing some LaTeX fonts. I see you have 
> texlive 2015, but could you give details on how you did install it?

It is installed by the package manager MacPorts, macports.org. As I understand 
it, MacPorts is a port of the BSD ports package manager. It is mostly 
well-maintained and Apple pays a full-time person to help the cause. I didn't 
explicitly install it but I'm sure it was installed as a dependency of some 
other package but not LyX as I've never used MacPorts to install LyX. FWIW, the 
first two items on my PATH variable are /opt/local/bin:/opt/local/sbin.
> 
> One possibility is that you have a wrong luatex binary somewhere on your 
> path: 
> http://tex.stackexchange.com/questions/116332/latex-compilation-of-simple-document-fails
> 
> What does the command "which luatex" return?

/opt/local/bin/luatex
As noted before, /opt/local/ is where all of MacPorts is installed, and only 
MacPorts.
Also:

$ luatex
This is LuaTeX, Version beta-0.80.0 (TeX Live 2015/MacPorts 2015_8) (rev 5238) 
 restricted \write18 enabled.

> 
> JMarc

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 3:04 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:

> Le 24/02/2016 10:06, Jerry a écrit :
>> I have two TeX installations. One I installed from the TUG (I think that's 
>> what it's called) binary installer, probably TeXlive-2013, and the other as 
>> part of MacPorts, macports.org; this -> "texlive-bin @2015_8+x11 (active)" I 
>> think is relevant information for the active version from MacPorts. LyX is 
>> seeing the MacPorts version since all of MacPorts is in /opt/local. The TUG 
>> version from 2013 is at /usr/local/texlive/2013. I think that is probably 
>> the whole wad since it is 3.4 GB. I have been thinking about deleting it and 
>> relying on the well-maintained MacPorts version.
> 
> Do you have the package texlive-fonts-recommended installed?

I'm not sure how to tell, so I did the macports command, port...
$ port installed texlive-fonts-recommended
None of the specified ports are installed.

so I would say, "no". I also searched my system for "texlive-fonts-recommended" 
and turned up only 
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/tex/texlive-fonts-recommended
which is a portfile which is not a "yes."

However, I suspect that texlive might install fonts in the places where OS X 
normally expects to find fonts and not in /opt/local where the rest of MacPorts 
lives--I have a question to the macports list about that.

FWIW, the OS X font manager indicates a number of entries for Latin Modern and 
TeX Gyre. When I put T1 into the manager's filter field, four Latin Modern 
families appear in the list. These _might_ have been installed by my other 
TeXLive installation from 2013 which is in /usr/something. Of course the basic 
Postscript fonts are also installed.

> 
> Note that we should probably not require the ec fonts to be installed. This 
> is very old code that I wrote at the time where these fonts were something 
> modern. It seems that it was in LyX 0.11.17, which means that it was written 
> almost 20 years ago :)
> 
> I would propose to remove this code and set the document encoding to T1 by 
> default. This whole font encoding thing has to be rethought, but I am not 
> competent in this respect.
> 
> JMarc
> 
> 

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 23, 2016, at 9:46 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Tue, Feb 23, 2016 at 09:18:50PM -0700, Jerry wrote:
>> 
>> On Feb 23, 2016, at 3:28 PM, Scott Kostyshak <skost...@lyx.org> wrote:
> 
>>> Jerry does this happen even when Flexiglass is not running?
>> 
>> Yes. The behavior is the same, which is, using a non-new LyX but running 
>> Reconfigure, one instance of luatex hitting 200-250 MB (it can vary 10s of 
>> MB between Activity Monitor updates, which is about 3 seconds--Activity 
>> Monitor is I believe eye candy over tops) and roughly 20-100% of a single 
>> CPU. That luatex crashes in 4-5 minutes. The message about the Python 
>> command not finishing is displayed. Clicking "let it run" causes a message 
>> displayed that the system has been reconfigured and to restart LyX. LyX does 
>> not crash.
>> 
>> I'll try to remember to quit Flexiglass when doing LyX testing but I 
>> probably use it a hundred+ times a day.
> 
> I imagine it is hard. Actually the useful thing is to know whether you
> can reproduce bugs that you find when Flexiglass is not running. So you
> do not always have to remember to turn it off, but maybe it is hard to
> remember to do it even in these cases.
> 
>>> Can you run that python command manually in a terminal?
>> Yes
>>> Can you
>>> reproduce the freeze when you do this?
>> No. The command ran for 35 minutes with almost of it with the line 
>> "+Indexing TeX files..." displayed.
> 
> This is important information. 35 minutes is not normal. For me it takes 9 
> seconds (although I would not be surprised if it takes up to a couple of 
> minutes on some computers).
> 
>> There were two Python instances during this time, one possibly spawned by 
>> the other. It (they) appear(s) to have finished normally. In my home 
>> directory the following files and directories--all empty--were created. I'm 
>> going to trash them.
> 
> I forgot to specify that normally this command would be run from your
> LyX user directory (which you can find the location of in Help > About).
> 
>> +Indexing TeX files... 
> 
> So this is where it pauses for a long time? How many minutes out of the
> 35?

Almost all--I'd guess 33-34.
> 
>> +checking for default encoding (this may take a long time)
> 
> This is the only place where we say that it might take a long time. Does
> the script pause here for a while?

I didn't notice it stopping for very long at all here or otherwise except as 
noted. I kept part of the terminal window visible as I did other things on my 
computer so I might have missed some details, but my strong impression is that 
everything flew by except the Indexing TeX files line. I would be happy to run 
it again if that would be helpful.

Jerry
> 
>> kpathsea: Running mktextfm ecrm1000
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
>> abbreviation  for ecrm1000.
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
>> mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
>> input ecrm1000
>> This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) 
>> (preloaded base=mf)
>> 
>> 
>> kpathsea: Running mktexmf ecrm1000
>> ! I can't find file `ecrm1000'.
>> <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000
>> 
>> Please type another input file name
>> ! Emergency stop.
>> <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000
>> 
>> Transcript written on mfput.log.
>> grep: ecrm1000.log: No such file or directory
>> mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
>> ecrm1000' failed to make ecrm1000.tfm.
>> kpathsea: Appending font creation commands to missfont.log.
> 
> This doesn't look normal. I'm not sure if it's LyX's fault or your TeX
> installation. Whatever it is, LyX should at least exit with error here,
> no?

I have two TeX installations. One I installed from the TUG (I think that's what 
it's called) binary installer, probably TeXlive-2013, and the other as part of 
MacPorts, macports.org; this -> "texlive-bin @2015_8+x11 (active)" I think is 
relevant information for the active version from MacPorts. LyX is seeing the 
MacPorts version since all of MacPorts is in /opt/local. The TUG version from 
2013 is at /usr/local/texlive/2013. I think that is probably the whole wad 
since it is 3.4 GB. I have been thinking about deleting it and relying on the 
well-maintained MacPorts version.

Jerry
> 
>> Python terminal output.txt
>>> 
>>> To make sure I understand correctly, you experienced 

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 23, 2016, at 3:28 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Fri, Feb 19, 2016 at 08:08:27PM -0700, Jerry wrote:
>> 
>> On Feb 18, 2016, at 9:49 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>> 
>>> On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
>>>> *Every*time* I first launch a new version of LyX, something like this 
>>>> happens: 
>>> 
>>> So to confirm, this is nothing new in 2.2.0 right? You remember seeing
>>> this in 2.1.x?
>>> 
>>>> LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with 
>>>> maybe 5 MB RAM but two luatex processes start up. Over a few minutes, they 
>>>> ramp up so that each consumes 200+ MB and up to nearly 100% CPU usage. (I 
>>>> have two cores.) The RAM and CPU usage vary somewhat, and take a few 
>>>> minutes to reach those numbers. I force-quit both luatex and LyX itself. 
>>>> Relaunch. One luatex process starts, along with LyX which is unresponsive. 
>>>> The luatex process crashes after a few minutes. I force-quit LyX. 
>>>> Relaunch, and then LyX runs normally.
>>>> 
>>>> This has happened for a long time, over several dev and release versions 
>>>> of LyX. However, this process has always terminated with LyX running 
>>>> successfully.
>>>> 
>>>> This just happened with 2.2.0beta2.
>>> 
>>> I'm guessing this is because of reconfigure. Can you do the following to
>>> confirm that it is because of reconfigure?
>>> 
>>> Click on LyX > Reconfigure. Does this reproduce the large RAM
>>> consumption and the 100% CPU spike?
>>> 
>>> Scott
>> 
>> Yes. Luatex ran one process, eventually hitting ~100% and ~200 MB, then 
>> crashed after about 4-5 minutes. I didn't see Python in call stack of the 
>> crash log but I did get this message in a dialog box:
>> 
>> The command
>> python -tt "/Applications/Words/LyXOuterFolder/LyX 
>> 2.2.0beta2/LyX.app/Contents/Resources/configure.py" 
>> --with-version-suffix=-2.2 
>> --binary-dir="/Applications/Words/LyXOuterFolder/LyX 
>> 2.2.0beta2/LyX.app/Contents/MacOS/"
>> has not yet completed.
>> 
>> Do you want to stop it?
>> 
>> I clicked on Continue or whatever the choice was and immediately got:
>> 
>> The system has been reconfigured.
>> You need to restart LyX to make use of any
>> updated document class specifications.
>> 
>> I quit LyX and relaunched, then ran Reconfigure again with the same result.
> 
> Jerry does this happen even when Flexiglass is not running?

Yes. The behavior is the same, which is, using a non-new LyX but running 
Reconfigure, one instance of luatex hitting 200-250 MB (it can vary 10s of MB 
between Activity Monitor updates, which is about 3 seconds--Activity Monitor is 
I believe eye candy over tops) and roughly 20-100% of a single CPU. That luatex 
crashes in 4-5 minutes. The message about the Python command not finishing is 
displayed. Clicking "let it run" causes a message displayed that the system has 
been reconfigured and to restart LyX. LyX does not crash.

I'll try to remember to quit Flexiglass when doing LyX testing but I probably 
use it a hundred+ times a day.
> 
> Can you run that python command manually in a terminal?
Yes
> Can you
> reproduce the freeze when you do this?
No. The command ran for 35 minutes with almost of it with the line "+Indexing 
TeX files..." displayed. There were two Python instances during this time, one 
possibly spawned by the other. It (they) appear(s) to have finished normally. 
In my home directory the following files and directories--all empty--were 
created. I'm going to trash them.

configure.log
lyxrc.defaults
packages.lst
textclass.lst
lyxmodules.lst
bibFiles.lst
bstFiles.lst
styFiles.lst
clsFiles.lst
bind
clipart
doc
examples
images
kbd
layouts
scripts
templates
ui

> What is the last line of output
> before the script freezes?
It doesn't freeze--see above.
> Can you copy and save the entire output from
> running that script manually?
It is attached.Last login: Tue Feb 23 03:19:16 on ttys002
MBPro:~ me$ python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"
checking for a Latex2e program...
+checking for "latex"...  yes
checking for a DVI postprocessing program...
+checking for "pplatex"...  no
checking for pLaTeX, the Japanese LaTeX...
+checking for "platex"...  yes

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 18, 2016, at 9:49 AM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
>> *Every*time* I first launch a new version of LyX, something like this 
>> happens: 
> 
> So to confirm, this is nothing new in 2.2.0 right? You remember seeing
> this in 2.1.x?
> 
>> LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with 
>> maybe 5 MB RAM but two luatex processes start up. Over a few minutes, they 
>> ramp up so that each consumes 200+ MB and up to nearly 100% CPU usage. (I 
>> have two cores.) The RAM and CPU usage vary somewhat, and take a few minutes 
>> to reach those numbers. I force-quit both luatex and LyX itself. Relaunch. 
>> One luatex process starts, along with LyX which is unresponsive. The luatex 
>> process crashes after a few minutes. I force-quit LyX. Relaunch, and then 
>> LyX runs normally.
>> 
>> This has happened for a long time, over several dev and release versions of 
>> LyX. However, this process has always terminated with LyX running 
>> successfully.
>> 
>> This just happened with 2.2.0beta2.
> 
> I'm guessing this is because of reconfigure. Can you do the following to
> confirm that it is because of reconfigure?
> 
> Click on LyX > Reconfigure. Does this reproduce the large RAM
> consumption and the 100% CPU spike?
> 
> Scott

Yes. Luatex ran one process, eventually hitting ~100% and ~200 MB, then crashed 
after about 4-5 minutes. I didn't see Python in call stack of the crash log but 
I did get this message in a dialog box:

 The command
python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"
has not yet completed.

Do you want to stop it?

I clicked on Continue or whatever the choice was and immediately got:

 The system has been reconfigured.
You need to restart LyX to make use of any
updated document class specifications.

I quit LyX and relaunched, then ran Reconfigure again with the same result.

Jerry

New versions of LyX always hang multiple times. OS X

[Jerry]

*Every*time* I first launch a new version of LyX, something like this happens: 

LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with maybe 5 
MB RAM but two luatex processes start up. Over a few minutes, they ramp up so 
that each consumes 200+ MB and up to nearly 100% CPU usage. (I have two cores.) 
The RAM and CPU usage vary somewhat, and take a few minutes to reach those 
numbers. I force-quit both luatex and LyX itself. Relaunch. One luatex process 
starts, along with LyX which is unresponsive. The luatex process crashes after 
a few minutes. I force-quit LyX. Relaunch, and then LyX runs normally.

This has happened for a long time, over several dev and release versions of 
LyX. However, this process has always terminated with LyX running successfully.

This just happened with 2.2.0beta2.

Jerry

Re: Pixmap cache is broken for master

[Jerry]

On Oct 13, 2015, at 8:29 AM, Stephan Witt <st.w...@gmx.net> wrote:

> Am 13.10.2015 um 16:43 schrieb Jean-Marc Lasgouttes <lasgout...@lyx.org>:
> 
>> Le 13/10/2015 12:32, Jerry a écrit :
>>> 
>>> Another difference is that the cached bitmaps (second line) do not use
>>> subpixel antialiasing, the rendering method on OS X. (There used to be a
>>> website explaining how Woz did this on the Apple II.) I don't know if
>>> this affects the metrics.
>> 
>> Stephan, this is a part I will not be able to deal with.
> 
> I think it's the same effect, Zhexuan describes with "the font becomes very 
> thin and less pleasant to read on a retina display". This is a matter or 
> choosing an appropriate screen font. If the user wants a stronger one it 
> should be possible to switch to another font for on-screen rendering. 

The reason the "font becomes very thin" with bitmap caching is due to the 
different rendering method that I mentioned in my previous post on this thread, 
specifically, the bitmaps that are cached are rendered without subpixel 
antialiasing. I believe that it might not be possible to efficiently save 
subpixel-antialiased characters on OS X because each character can be rendered 
in different ways, depending on its placement on the screen--OS X characters 
are not constrained to a grid.

I don't know if the following is a well-kept secret, but on OS X, you can zoom 
the screen to the position of the cursor by holding Control while executing a 
two-finger swipe upward (and zoom back out by swiping down). This is how it 
becomes easy to see how text is rendered. To achieve this, System Preferences 
-> Accessibility -> Zoom then check Use scroll gesture with modifier keys to 
zoom, and uncheck Smooth images.

Using this zooming, it is quite easy to see how characters are rendered, and to 
find instances of a character that are rendered in different ways.

I believe that Microsoft finally defaulted to subpixel rendering a few years 
ago but they might still constrain characters to lie on a grid which if true 
would make caching in that case a reasonable exercise, I suppose, since each 
instance of a character would be the same.

So, (further speculating) if the cached characters are constrained to lie on a 
grid while the subpixel versions are not so constrained, I would guess that 
that could affect the width of words.

Sorry if this is rehashing old stuff to you folks.

Yes, choice of screen fonts can partially mitigate the problem but characters 
will always be thin and fuzzy compared to their subpixel versions of the same 
font.

Jerry

> 
>> But already we should be able to find out why the pixmaps are too short.
> 
> Yes hopefully, now I've tried 5.6.0-alpha Qt and it doesn't improve the 
> situation.
> 
> Stephan
> 
>> Also, the bearing computation will be completely wrong with bidi text.
>> 
>> JMarc
> 

Re: Pixmap cache is broken for master

[Jerry]

On Oct 11, 2015, at 8:19 PM, Stephan Witt  wrote:

> Stephan
> 




Another difference is that the cached bitmaps (second line) do not use subpixel 
antialiasing, the rendering method on OS X. (There used to be a website 
explaining how Woz did this on the Apple II.) I don't know if this affects the 
metrics.

Re: mailing list test

[Jerry]

On Sep 6, 2015, at 12:23 PM, Stephan Witt <st.w...@gmx.net> wrote:

> Am 06.09.2015 um 20:09 schrieb Richard Heck <rgh...@lyx.org>:
> 
>> On 09/05/2015 04:11 AM, Stephan Witt wrote:
>>> Sorry for this test, but I don't get any mails for lyx-devel and lyx-users 
>>> anymore since the 8th of August or so.
>>> 
>>> I tried to subscribe again and to mail to help for lyx-devel without any 
>>> response.
>>> 
>>> So, I'll see if this message show up in the mail archive.
>> 
>> Weird. This message did get through.
> 
> I'm not on the list of the subscribers anymore. Posts are allowed for 
> everyone.
> I don't know what's wrong with my mail address.
> 
> Stephan

I've had similar problems with both dev and users' lists and just now started 
receiving messages again. I received an automated message from the dev list a 
couple days ago, replied as advised, got a message that I was already 
subscribed, and now am getting messages from both list once again.

Jerry

Re: Build questions for OS X

[Jerry]

On Jul 8, 2015, at 3:32 AM, Stephan Witt st.w...@gmx.net wrote:

 Am 08.07.2015 um 12:06 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 7, 2015, at 10:54 PM, Stephan Witt st.w...@gmx.net wrote:
 
 Am 08.07.2015 um 01:20 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 7, 2015, at 12:38 PM, Georg Baum georg.b...@post.rwth-aachen.de 
 wrote:
 
 Jean-Marc Lasgouttes wrote:
 
 Le 07/07/2015 01:07, Jerry a écrit :
 CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
 pars.insert(next(pars.begin(), pit),
 ^~~~
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
   candidate function [with _ForwardIter =
   std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
   std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 
 We had this error before. It probably means that your clang version 
 provides 
 a std::next from the C++11 standard even if no C++11 standard is 
 requested 
 on the command line. Since we do not try to detect ourselves anymore 
 whether 
 C++98 or C++11 is used, we will probably see this more and more in the 
 future, and at some point in time we'll need to set the compiler 
 commandline 
 option --std=C++98 if configure was not called with --enable-cxx11.
 
 What happens if you add --enable-cxx1 to the configure command-line?
 
 This should mean of course --enable-cxx11.
 
 
 Georg
 
 
 PS: The config log file looks good at a first glance. clang and libc++ 
 are 
 correctly detected.
 
 I added --enable-cxx11 to configure and removed the space--as discussed 
 elsewhere in this thread--from the path to the Qt5 things. The compiler 
 problems have gone away but now there appear to be problems linking Qt. 
 Recall that the Qt version that I am attempting to reach is 5.5 downloaded 
 from Qt's own web site.
 
 Here is my build script:
 
 
 
 #!/bin/bash
 
 #  Create a build directory if one does not already exist.
 cd /Applications/Words/LyXOuterFolder/git
 mkdir -p build
 
 # Clean out any previous build products but leave the build directory (*).
 rm -rf /Applications/Words/LyXOuterFolder/git/build/*
 rm -rf /Applications/Words/LyXOuterFolder/git/Contents/
 
 cd /Applications/Words/LyXOuterFolder/git/lyx/
 ./autogen.sh
 
 # Move to build directory and run configure that is in lyx directory.
 cd /Applications/Words/LyXOuterFolder/git/build/
 ../lyx/configure \
 --with-version-suffix=-2.X \
 --with-libiconv-prefix=/usr/lib \
 --with-x=no \
 --disable-stdlib-debug \
 --enable-cxx11 \
 --prefix=/Applications/Words/LyXOuterFolder/git \
 --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/
 make
 make install-strip
 
 
 
 Here are the last few lines with errors. The linker might have found my 
 Qt4 installation from MacPorts. I don't know if it is 32-bit or 64-bit or 
 both. /opt/local/ is the MacPorts stuff. FWIW the referenced library is 
 here:
 
 /Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a
 
 
 CXXLDlyx
 Undefined symbols for architecture x86_64:
 decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
  std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
 lyx::frontend::GuiWorkArea*, void(void 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*), 
 referenced from:
   
 boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
 void::invoke(boost::detail::function::function_buffer) in 
 liblyxqt4.a(GuiWorkArea.o)
 ld: symbol(s) not found for architecture x86_64
 clang: error: linker command failed with exit code 1 (use -v to see 
 invocation)
 make[4]: *** [lyx] Error 1
 make[3]: *** [install-recursive] Error 1
 make[2]: *** [install] Error 2
 make[1]: *** [install-recursive] Error 1
 make: *** [install-strip] Error 2
 
 
 
 Attached is my config log. It contains the lines
 
 configure:2893: checking whether Qt5 is requested
 configure:2902: result: no
 
 This means you didn't add --enable-qt5=yes - but this is only useful for 
 systems
 with Qt4 and Qt5 installed side by side (like Linux distros typically do) 
 and
 with different names for QtCore et al.
 
 The problem with Qt detection here is the complete ignorance of the 
 --with-qt-dir
 command line option given to configure. I don't know how this should work 
 intentionally
 but your Qt4 MacPorts Qt-version wins because of the position of 
 /opt/local/bin in
 PATH and configure trying to detect Qt with pkg-config with without using 
 the value
 given by --with-qt-dir.
 
 Why this doesn't work at the end I don't know - I don't have the MacPorts 
 Qt package.
 
 Regards, Stephan
 
 PS. I fear, you'll have a long way to go if you want to solve all issues 
 coming along

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 10:54 PM, Stephan Witt st.w...@gmx.net wrote:

 Am 08.07.2015 um 01:20 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 7, 2015, at 12:38 PM, Georg Baum georg.b...@post.rwth-aachen.de 
 wrote:
 
 Jean-Marc Lasgouttes wrote:
 
 Le 07/07/2015 01:07, Jerry a écrit :
 CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
   pars.insert(next(pars.begin(), pit),
   ^~~~
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
 candidate function [with _ForwardIter =
 std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
 std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 
 We had this error before. It probably means that your clang version 
 provides 
 a std::next from the C++11 standard even if no C++11 standard is requested 
 on the command line. Since we do not try to detect ourselves anymore 
 whether 
 C++98 or C++11 is used, we will probably see this more and more in the 
 future, and at some point in time we'll need to set the compiler 
 commandline 
 option --std=C++98 if configure was not called with --enable-cxx11.
 
 What happens if you add --enable-cxx1 to the configure command-line?
 
 This should mean of course --enable-cxx11.
 
 
 Georg
 
 
 PS: The config log file looks good at a first glance. clang and libc++ are 
 correctly detected.
 
 I added --enable-cxx11 to configure and removed the space--as discussed 
 elsewhere in this thread--from the path to the Qt5 things. The compiler 
 problems have gone away but now there appear to be problems linking Qt. 
 Recall that the Qt version that I am attempting to reach is 5.5 downloaded 
 from Qt's own web site.
 
 Here is my build script:
 
 
 
 #!/bin/bash
 
 #  Create a build directory if one does not already exist.
 cd /Applications/Words/LyXOuterFolder/git
 mkdir -p build
 
 # Clean out any previous build products but leave the build directory (*).
 rm -rf /Applications/Words/LyXOuterFolder/git/build/*
 rm -rf /Applications/Words/LyXOuterFolder/git/Contents/
 
 cd /Applications/Words/LyXOuterFolder/git/lyx/
 ./autogen.sh
 
 # Move to build directory and run configure that is in lyx directory.
 cd /Applications/Words/LyXOuterFolder/git/build/
 ../lyx/configure \
   --with-version-suffix=-2.X \
   --with-libiconv-prefix=/usr/lib \
   --with-x=no \
   --disable-stdlib-debug \
   --enable-cxx11 \
   --prefix=/Applications/Words/LyXOuterFolder/git \
   
 --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/
 make
 make install-strip
 
 
 
 Here are the last few lines with errors. The linker might have found my Qt4 
 installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
 /opt/local/ is the MacPorts stuff. FWIW the referenced library is here:
 
 /Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a
 
 
 CXXLDlyx
 Undefined symbols for architecture x86_64:
 decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
  std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
 lyx::frontend::GuiWorkArea*, void(void 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*), 
 referenced from:
 
 boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
 void::invoke(boost::detail::function::function_buffer) in 
 liblyxqt4.a(GuiWorkArea.o)
 ld: symbol(s) not found for architecture x86_64
 clang: error: linker command failed with exit code 1 (use -v to see 
 invocation)
 make[4]: *** [lyx] Error 1
 make[3]: *** [install-recursive] Error 1
 make[2]: *** [install] Error 2
 make[1]: *** [install-recursive] Error 1
 make: *** [install-strip] Error 2
 
 
 
 Attached is my config log. It contains the lines
 
 configure:2893: checking whether Qt5 is requested
 configure:2902: result: no
 
 This means you didn't add --enable-qt5=yes - but this is only useful for 
 systems
 with Qt4 and Qt5 installed side by side (like Linux distros typically do) and
 with different names for QtCore et al.
 
 The problem with Qt detection here is the complete ignorance of the 
 --with-qt-dir
 command line option given to configure. I don't know how this should work 
 intentionally
 but your Qt4 MacPorts Qt-version wins because of the position of 
 /opt/local/bin in
 PATH and configure trying to detect Qt with pkg-config with without using the 
 value
 given by --with-qt-dir.
 
 Why this doesn't work at the end I don't know - I don't have the MacPorts Qt 
 package.
 
 Regards, Stephan
 
 PS. I fear, you'll have a long way to go if you want to solve all issues 
 coming along
 this route. In case you want to ditch the MacPort route and go for Qt5 - I 
 tried it with
 Qt5.5.0 now

Re: Build questions for OS X

[Jerry]

On Jul 8, 2015, at 4:48 PM, Jerry lancebo...@qwest.net wrote:

 
 On Jul 8, 2015, at 9:09 AM, Stephan Witt st.w...@gmx.net wrote:
 
 Am 08.07.2015 um 13:08 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 8, 2015, at 3:32 AM, Stephan Witt st.w...@gmx.net wrote:
 
 Am 08.07.2015 um 12:06 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 7, 2015, at 10:54 PM, Stephan Witt st.w...@gmx.net wrote:
 
 Am 08.07.2015 um 01:20 schrieb Jerry lancebo...@qwest.net:
 
 This means you didn't add --enable-qt5=yes - but this is only useful for 
 systems
 with Qt4 and Qt5 installed side by side (like Linux distros typically 
 do) and
 with different names for QtCore et al.
 
 The problem with Qt detection here is the complete ignorance of the 
 --with-qt-dir
 command line option given to configure. I don't know how this should 
 work intentionally
 but your Qt4 MacPorts Qt-version wins because of the position of 
 /opt/local/bin in
 PATH and configure trying to detect Qt with pkg-config with without 
 using the value
 given by --with-qt-dir.
 
 Why this doesn't work at the end I don't know - I don't have the 
 MacPorts Qt package.
 
 Regards, Stephan
 
 PS. I fear, you'll have a long way to go if you want to solve all issues 
 coming along
 this route. In case you want to ditch the MacPort route and go for Qt5 - 
 I tried it with
 Qt5.5.0 now and this is broken too. They've fixed the issue with RPATH 
 dyld at runtime
 lookup of the Qt-frameworks and now the LyX binary aborts on startup 
 because of this.
 I have to get a working environment with Qt5.5.0 myself first before I 
 can tell you
 the recipe for building LyX this way.
 
 So I gather that somehow configure is ignoring --with-qt-dir and 
 defaulting to the path precedence. Would it help if I prepended 
 /Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks
 to the front of PATH so that it finds Qt5 first?
 
 No, I don't think so. IMHO, the problem is in configure using the
 /opt/local/bin/pkg-config utility first and trying the given qt-dir
 as a fallback only.
 
 I'm not sure I follow everything in your PS. I can use MacPorts to 
 install qt5-mac 5.4.2 (5.5 is not yet available at MacPorts). Is that 
 worth a try while also adding --enable-qt5=yes? (I need to keep MacPorts 
 Qt4 around for other stuff, I assume.)
 
 This one I cannot answer. I'd try it probably.
 
 But I fear this conflicts with the MacPorts way of doing things.
 I'd guess you have to choose the active port of Qt after having
 both versions installed and MacPorts will create some links to
 the active version for you. I don't know.
 
 Regards, Stephan
 
 Hmmm It looks like there are activate and deactivate commands for 
 MacPorts. I don't know how they handle things if one programs wants one 
 version and another program wants another version. Seems like this wouldn't 
 be allowed in general but I might get away with playing around for a bit.
 
 I've put a change in to add the necessary -rpath options to the linker 
 command line.
 These are required to use the self-made Qt5.5.x and probably for the 
 frameworks built by Digia.
 Look at git commit 6e9bd23a1f1888b2022335b2d05a3f770ada935a
 
 I'm not sure if this is enough to use the Digia frameworks.
 
 Regards, Stephan
 
 I tried building with your changes. Using the same script as before, errors 
 occur as such:
 
 CXXLDlyx
 Undefined symbols for architecture x86_64:
  
 decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
  std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
 lyx::frontend::GuiWorkArea*, void(void 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*), 
 referenced from:
  
 boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
 void::invoke(boost::detail::function::function_buffer) in 
 liblyxqt4.a(GuiWorkArea.o)
 ld: symbol(s) not found for architecture x86_64
 clang: error: linker command failed with exit code 1 (use -v to see 
 invocation)
 make[4]: *** [lyx] Error 1
 make[3]: *** [install-recursive] Error 1
 make[2]: *** [install] Error 2
 make[1]: *** [install-recursive] Error 1
 make: *** [install-strip] Error 2
 
 I added --enable-qt5=yes to the configure line and got this:
 
 checking for QT_CORE... checking for QT_FRONTEND... checking for X... disabled
 checking for Qt library name... failed
 configure: error: cannot compile a simple Qt executable. Check you have the 
 right $QTDIR.
 make: *** No targets specified and no makefile found.  Stop.
 make: *** No rule to make target `install-strip'.  Stop.
 
 Jerry

I tried to build again but (1) removed the --enable-qt5=yes argument and (2) 
removed the path to the Qt5 frameworks, 
--with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/,
 thinking that the Qt4 things might be found in MacPorts.

The result is the same as the previous attempt, summarized immediately

Re: Build questions for OS X

[Jerry]

On Jul 8, 2015, at 9:09 AM, Stephan Witt st.w...@gmx.net wrote:

 Am 08.07.2015 um 13:08 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 8, 2015, at 3:32 AM, Stephan Witt st.w...@gmx.net wrote:
 
 Am 08.07.2015 um 12:06 schrieb Jerry lancebo...@qwest.net:
 
 
 On Jul 7, 2015, at 10:54 PM, Stephan Witt st.w...@gmx.net wrote:
 
 Am 08.07.2015 um 01:20 schrieb Jerry lancebo...@qwest.net:
 
 This means you didn't add --enable-qt5=yes - but this is only useful for 
 systems
 with Qt4 and Qt5 installed side by side (like Linux distros typically do) 
 and
 with different names for QtCore et al.
 
 The problem with Qt detection here is the complete ignorance of the 
 --with-qt-dir
 command line option given to configure. I don't know how this should work 
 intentionally
 but your Qt4 MacPorts Qt-version wins because of the position of 
 /opt/local/bin in
 PATH and configure trying to detect Qt with pkg-config with without using 
 the value
 given by --with-qt-dir.
 
 Why this doesn't work at the end I don't know - I don't have the MacPorts 
 Qt package.
 
 Regards, Stephan
 
 PS. I fear, you'll have a long way to go if you want to solve all issues 
 coming along
 this route. In case you want to ditch the MacPort route and go for Qt5 - 
 I tried it with
 Qt5.5.0 now and this is broken too. They've fixed the issue with RPATH 
 dyld at runtime
 lookup of the Qt-frameworks and now the LyX binary aborts on startup 
 because of this.
 I have to get a working environment with Qt5.5.0 myself first before I 
 can tell you
 the recipe for building LyX this way.
 
 So I gather that somehow configure is ignoring --with-qt-dir and 
 defaulting to the path precedence. Would it help if I prepended 
 /Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks
 to the front of PATH so that it finds Qt5 first?
 
 No, I don't think so. IMHO, the problem is in configure using the
 /opt/local/bin/pkg-config utility first and trying the given qt-dir
 as a fallback only.
 
 I'm not sure I follow everything in your PS. I can use MacPorts to install 
 qt5-mac 5.4.2 (5.5 is not yet available at MacPorts). Is that worth a try 
 while also adding --enable-qt5=yes? (I need to keep MacPorts Qt4 around 
 for other stuff, I assume.)
 
 This one I cannot answer. I'd try it probably.
 
 But I fear this conflicts with the MacPorts way of doing things.
 I'd guess you have to choose the active port of Qt after having
 both versions installed and MacPorts will create some links to
 the active version for you. I don't know.
 
 Regards, Stephan
 
 Hmmm It looks like there are activate and deactivate commands for 
 MacPorts. I don't know how they handle things if one programs wants one 
 version and another program wants another version. Seems like this wouldn't 
 be allowed in general but I might get away with playing around for a bit.
 
 I've put a change in to add the necessary -rpath options to the linker 
 command line.
 These are required to use the self-made Qt5.5.x and probably for the 
 frameworks built by Digia.
 Look at git commit 6e9bd23a1f1888b2022335b2d05a3f770ada935a
 
 I'm not sure if this is enough to use the Digia frameworks.
 
 Regards, Stephan
 
I tried building with your changes. Using the same script as before, errors 
occur as such:

CXXLDlyx
Undefined symbols for architecture x86_64:
  
decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
 std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
lyx::frontend::GuiWorkArea*, void(void (lyx::frontend::GuiWorkArea::*)(), 
lyx::frontend::GuiWorkArea*), referenced from:
  boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
(lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
void::invoke(boost::detail::function::function_buffer) in 
liblyxqt4.a(GuiWorkArea.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [lyx] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2

I added --enable-qt5=yes to the configure line and got this:

checking for QT_CORE... checking for QT_FRONTEND... checking for X... disabled
checking for Qt library name... failed
configure: error: cannot compile a simple Qt executable. Check you have the 
right $QTDIR.
make: *** No targets specified and no makefile found.  Stop.
make: *** No rule to make target `install-strip'.  Stop.

Jerry

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 10:54 PM, Stephan Witt <st.w...@gmx.net> wrote:

> Am 08.07.2015 um 01:20 schrieb Jerry <lancebo...@qwest.net>:
> 
>> 
>> On Jul 7, 2015, at 12:38 PM, Georg Baum <georg.b...@post.rwth-aachen.de> 
>> wrote:
>> 
>>> Jean-Marc Lasgouttes wrote:
>>> 
>>>> Le 07/07/2015 01:07, Jerry a écrit :
>>>>> CXX  CutAndPaste.o
>>>>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>>>>   pars.insert(next(pars.begin(), pit),
>>>>>   ^~~~
>>>>> 
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>>>> note:
>>>>> candidate function [with _ForwardIter =
>>>>> std::__1::__list_iterator<lyx::Paragraph, void *>]
>>>>> next(_ForwardIter __x,
>>>>> ^
>>>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>>> std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>>>>> inline It next(It i, Diff n = 1)
>>> 
>>> We had this error before. It probably means that your clang version 
>>> provides 
>>> a std::next from the C++11 standard even if no C++11 standard is requested 
>>> on the command line. Since we do not try to detect ourselves anymore 
>>> whether 
>>> C++98 or C++11 is used, we will probably see this more and more in the 
>>> future, and at some point in time we'll need to set the compiler 
>>> commandline 
>>> option --std=C++98 if configure was not called with --enable-cxx11.
>>> 
>>>> What happens if you add --enable-cxx1 to the configure command-line?
>>> 
>>> This should mean of course --enable-cxx11.
>>> 
>>> 
>>> Georg
>>> 
>>> 
>>> PS: The config log file looks good at a first glance. clang and libc++ are 
>>> correctly detected.
>>> 
>> I added --enable-cxx11 to configure and removed the space--as discussed 
>> elsewhere in this thread--from the path to the Qt5 things. The compiler 
>> problems have gone away but now there appear to be problems linking Qt. 
>> Recall that the Qt version that I am attempting to reach is 5.5 downloaded 
>> from Qt's own web site.
>> 
>> Here is my build script:
>> 
>> 
>> 
>> #!/bin/bash
>> 
>> #  Create a build directory if one does not already exist.
>> cd /Applications/Words/LyXOuterFolder/git
>> mkdir -p build
>> 
>> # Clean out any previous build products but leave the build directory (*).
>> rm -rf /Applications/Words/LyXOuterFolder/git/build/*
>> rm -rf /Applications/Words/LyXOuterFolder/git/Contents/
>> 
>> cd /Applications/Words/LyXOuterFolder/git/lyx/
>> ./autogen.sh
>> 
>> # Move to build directory and run configure that is in lyx directory.
>> cd /Applications/Words/LyXOuterFolder/git/build/
>> ../lyx/configure \
>>   --with-version-suffix=-2.X \
>>   --with-libiconv-prefix=/usr/lib \
>>   --with-x=no \
>>   --disable-stdlib-debug \
>>   --enable-cxx11 \
>>   --prefix=/Applications/Words/LyXOuterFolder/git \
>>   
>> --with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/"
>> make
>> make install-strip
>> 
>> 
>> 
>> Here are the last few lines with errors. The linker might have found my Qt4 
>> installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
>> /opt/local/ is the MacPorts stuff. FWIW the referenced library is here:
>> 
>> /Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a
>> 
>> 
>> CXXLDlyx
>> Undefined symbols for architecture x86_64:
>> "decltype(*(std::__1::forward<lyx::frontend::GuiWorkArea*&>(fp0)).*fp(std::__1::forward<>(fp1)))
>>  std::__1::__invoke> lyx::frontend::GuiWorkArea*&, void>(void 
>> (lyx::frontend::GuiWorkArea::*&&&)(), lyx::frontend::GuiWorkArea*&&&)", 
>> referenced from:
>> 
>> boost::detail::function::void_function_obj_invoker0<std::__1::__bind> (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*>, 
>> void>::invoke(boost::detail::function::function_buffer&) in 
>> liblyxqt4.a(GuiWorkArea.o)
>> ld: symbol(s) not found for architecture x86_64
>> clang: error: linker command failed with exit code 1 (use -v to see 
>> invocation)
>> 

Re: Build questions for OS X

[Jerry]

On Jul 8, 2015, at 3:32 AM, Stephan Witt <st.w...@gmx.net> wrote:

> Am 08.07.2015 um 12:06 schrieb Jerry <lancebo...@qwest.net>:
> 
>> 
>> On Jul 7, 2015, at 10:54 PM, Stephan Witt <st.w...@gmx.net> wrote:
>> 
>>> Am 08.07.2015 um 01:20 schrieb Jerry <lancebo...@qwest.net>:
>>> 
>>>> 
>>>> On Jul 7, 2015, at 12:38 PM, Georg Baum <georg.b...@post.rwth-aachen.de> 
>>>> wrote:
>>>> 
>>>>> Jean-Marc Lasgouttes wrote:
>>>>> 
>>>>>> Le 07/07/2015 01:07, Jerry a écrit :
>>>>>>> CXX  CutAndPaste.o
>>>>>>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>>>>>> pars.insert(next(pars.begin(), pit),
>>>>>>> ^~~~
>>>>>>> 
>>>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>>>>>> note:
>>>>>>>   candidate function [with _ForwardIter =
>>>>>>>   std::__1::__list_iterator<lyx::Paragraph, void *>]
>>>>>>> next(_ForwardIter __x,
>>>>>>> ^
>>>>>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>>>>>   std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>>>>>>> inline It next(It i, Diff n = 1)
>>>>> 
>>>>> We had this error before. It probably means that your clang version 
>>>>> provides 
>>>>> a std::next from the C++11 standard even if no C++11 standard is 
>>>>> requested 
>>>>> on the command line. Since we do not try to detect ourselves anymore 
>>>>> whether 
>>>>> C++98 or C++11 is used, we will probably see this more and more in the 
>>>>> future, and at some point in time we'll need to set the compiler 
>>>>> commandline 
>>>>> option --std=C++98 if configure was not called with --enable-cxx11.
>>>>> 
>>>>>> What happens if you add --enable-cxx1 to the configure command-line?
>>>>> 
>>>>> This should mean of course --enable-cxx11.
>>>>> 
>>>>> 
>>>>> Georg
>>>>> 
>>>>> 
>>>>> PS: The config log file looks good at a first glance. clang and libc++ 
>>>>> are 
>>>>> correctly detected.
>>>>> 
>>>> I added --enable-cxx11 to configure and removed the space--as discussed 
>>>> elsewhere in this thread--from the path to the Qt5 things. The compiler 
>>>> problems have gone away but now there appear to be problems linking Qt. 
>>>> Recall that the Qt version that I am attempting to reach is 5.5 downloaded 
>>>> from Qt's own web site.
>>>> 
>>>> Here is my build script:
>>>> 
>>>> 
>>>> 
>>>> #!/bin/bash
>>>> 
>>>> #  Create a build directory if one does not already exist.
>>>> cd /Applications/Words/LyXOuterFolder/git
>>>> mkdir -p build
>>>> 
>>>> # Clean out any previous build products but leave the build directory (*).
>>>> rm -rf /Applications/Words/LyXOuterFolder/git/build/*
>>>> rm -rf /Applications/Words/LyXOuterFolder/git/Contents/
>>>> 
>>>> cd /Applications/Words/LyXOuterFolder/git/lyx/
>>>> ./autogen.sh
>>>> 
>>>> # Move to build directory and run configure that is in lyx directory.
>>>> cd /Applications/Words/LyXOuterFolder/git/build/
>>>> ../lyx/configure \
>>>> --with-version-suffix=-2.X \
>>>> --with-libiconv-prefix=/usr/lib \
>>>> --with-x=no \
>>>> --disable-stdlib-debug \
>>>> --enable-cxx11 \
>>>> --prefix=/Applications/Words/LyXOuterFolder/git \
>>>> --with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/"
>>>> make
>>>> make install-strip
>>>> 
>>>> 
>>>> 
>>>> Here are the last few lines with errors. The linker might have found my 
>>>> Qt4 installation from MacPorts. I don't know if it is 32-bit or 64-bit or 
>>>> both. /opt/local/ is the MacPorts stuff. FWIW the referenced library is 
>>>> here:
>>>> 
>>>> /Applications/Words/LyXOuterFolder/git/build/src/frontends

Re: Build questions for OS X

[Jerry]

On Jul 8, 2015, at 9:09 AM, Stephan Witt <st.w...@gmx.net> wrote:

> Am 08.07.2015 um 13:08 schrieb Jerry <lancebo...@qwest.net>:
> 
>> 
>> On Jul 8, 2015, at 3:32 AM, Stephan Witt <st.w...@gmx.net> wrote:
>> 
>>> Am 08.07.2015 um 12:06 schrieb Jerry <lancebo...@qwest.net>:
>>> 
>>>> 
>>>> On Jul 7, 2015, at 10:54 PM, Stephan Witt <st.w...@gmx.net> wrote:
>>>> 
>>>>> Am 08.07.2015 um 01:20 schrieb Jerry <lancebo...@qwest.net>:
>>>>> 
>>>>> This means you didn't add --enable-qt5=yes - but this is only useful for 
>>>>> systems
>>>>> with Qt4 and Qt5 installed side by side (like Linux distros typically do) 
>>>>> and
>>>>> with different names for QtCore et al.
>>>>> 
>>>>> The problem with Qt detection here is the complete ignorance of the 
>>>>> --with-qt-dir
>>>>> command line option given to configure. I don't know how this should work 
>>>>> intentionally
>>>>> but your Qt4 MacPorts Qt-version wins because of the position of 
>>>>> /opt/local/bin in
>>>>> PATH and configure trying to detect Qt with pkg-config with without using 
>>>>> the value
>>>>> given by --with-qt-dir.
>>>>> 
>>>>> Why this doesn't work at the end I don't know - I don't have the MacPorts 
>>>>> Qt package.
>>>>> 
>>>>> Regards, Stephan
>>>>> 
>>>>> PS. I fear, you'll have a long way to go if you want to solve all issues 
>>>>> coming along
>>>>> this route. In case you want to ditch the MacPort route and go for Qt5 - 
>>>>> I tried it with
>>>>> Qt5.5.0 now and this is broken too. They've fixed the issue with RPATH 
>>>>> dyld at runtime
>>>>> lookup of the Qt-frameworks and now the LyX binary aborts on startup 
>>>>> because of this.
>>>>> I have to get a working environment with Qt5.5.0 myself first before I 
>>>>> can tell you
>>>>> the recipe for building LyX this way.
>>>> 
>>>> So I gather that somehow configure is ignoring --with-qt-dir and 
>>>> defaulting to the path precedence. Would it help if I prepended 
>>>> /Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks
>>>> to the front of PATH so that it finds Qt5 first?
>>> 
>>> No, I don't think so. IMHO, the problem is in configure using the
>>> /opt/local/bin/pkg-config utility first and trying the given qt-dir
>>> as a fallback only.
>>> 
>>>> I'm not sure I follow everything in your PS. I can use MacPorts to install 
>>>> qt5-mac 5.4.2 (5.5 is not yet available at MacPorts). Is that worth a try 
>>>> while also adding --enable-qt5=yes? (I need to keep MacPorts Qt4 around 
>>>> for other stuff, I assume.)
>>> 
>>> This one I cannot answer. I'd try it probably.
>>> 
>>> But I fear this conflicts with the MacPorts way of doing things.
>>> I'd guess you have to choose the active port of Qt after having
>>> both versions installed and MacPorts will create some links to
>>> the active version for you. I don't know.
>>> 
>>> Regards, Stephan
>> 
>> Hmmm It looks like there are activate and deactivate commands for 
>> MacPorts. I don't know how they handle things if one programs wants one 
>> version and another program wants another version. Seems like this wouldn't 
>> be allowed in general but I might get away with playing around for a bit.
> 
> I've put a change in to add the necessary -rpath options to the linker 
> command line.
> These are required to use the self-made Qt5.5.x and probably for the 
> frameworks built by Digia.
> Look at git commit 6e9bd23a1f1888b2022335b2d05a3f770ada935a
> 
> I'm not sure if this is enough to use the Digia frameworks.
> 
> Regards, Stephan
> 
I tried building with your changes. Using the same script as before, errors 
occur as such:

CXXLDlyx
Undefined symbols for architecture x86_64:
  
"decltype(*(std::__1::forward<lyx::frontend::GuiWorkArea*&>(fp0)).*fp(std::__1::forward<>(fp1)))
 std::__1::__invoke(void (lyx::frontend::GuiWorkArea::*&&&)(), 
lyx::frontend::GuiWorkArea*&&&)", referenced from:
  boost::detail::function::void_function_obj_invoker0<std::__1::__bind, 
void>::invoke(boost::detail::function::function_buffer&) in 
liblyxqt4.a(GuiWorkArea.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [lyx] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2

I added --enable-qt5=yes to the configure line and got this:

checking for QT_CORE... checking for QT_FRONTEND... checking for X... disabled
checking for Qt library name... failed
configure: error: cannot compile a simple Qt executable. Check you have the 
right $QTDIR.
make: *** No targets specified and no makefile found.  Stop.
make: *** No rule to make target `install-strip'.  Stop.

Jerry

Re: Build questions for OS X

[Jerry]

On Jul 8, 2015, at 4:48 PM, Jerry <lancebo...@qwest.net> wrote:

> 
> On Jul 8, 2015, at 9:09 AM, Stephan Witt <st.w...@gmx.net> wrote:
> 
>> Am 08.07.2015 um 13:08 schrieb Jerry <lancebo...@qwest.net>:
>> 
>>> 
>>> On Jul 8, 2015, at 3:32 AM, Stephan Witt <st.w...@gmx.net> wrote:
>>> 
>>>> Am 08.07.2015 um 12:06 schrieb Jerry <lancebo...@qwest.net>:
>>>> 
>>>>> 
>>>>> On Jul 7, 2015, at 10:54 PM, Stephan Witt <st.w...@gmx.net> wrote:
>>>>> 
>>>>>> Am 08.07.2015 um 01:20 schrieb Jerry <lancebo...@qwest.net>:
>>>>>> 
>>>>>> This means you didn't add --enable-qt5=yes - but this is only useful for 
>>>>>> systems
>>>>>> with Qt4 and Qt5 installed side by side (like Linux distros typically 
>>>>>> do) and
>>>>>> with different names for QtCore et al.
>>>>>> 
>>>>>> The problem with Qt detection here is the complete ignorance of the 
>>>>>> --with-qt-dir
>>>>>> command line option given to configure. I don't know how this should 
>>>>>> work intentionally
>>>>>> but your Qt4 MacPorts Qt-version wins because of the position of 
>>>>>> /opt/local/bin in
>>>>>> PATH and configure trying to detect Qt with pkg-config with without 
>>>>>> using the value
>>>>>> given by --with-qt-dir.
>>>>>> 
>>>>>> Why this doesn't work at the end I don't know - I don't have the 
>>>>>> MacPorts Qt package.
>>>>>> 
>>>>>> Regards, Stephan
>>>>>> 
>>>>>> PS. I fear, you'll have a long way to go if you want to solve all issues 
>>>>>> coming along
>>>>>> this route. In case you want to ditch the MacPort route and go for Qt5 - 
>>>>>> I tried it with
>>>>>> Qt5.5.0 now and this is broken too. They've fixed the issue with RPATH 
>>>>>> dyld at runtime
>>>>>> lookup of the Qt-frameworks and now the LyX binary aborts on startup 
>>>>>> because of this.
>>>>>> I have to get a working environment with Qt5.5.0 myself first before I 
>>>>>> can tell you
>>>>>> the recipe for building LyX this way.
>>>>> 
>>>>> So I gather that somehow configure is ignoring --with-qt-dir and 
>>>>> defaulting to the path precedence. Would it help if I prepended 
>>>>> /Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks
>>>>> to the front of PATH so that it finds Qt5 first?
>>>> 
>>>> No, I don't think so. IMHO, the problem is in configure using the
>>>> /opt/local/bin/pkg-config utility first and trying the given qt-dir
>>>> as a fallback only.
>>>> 
>>>>> I'm not sure I follow everything in your PS. I can use MacPorts to 
>>>>> install qt5-mac 5.4.2 (5.5 is not yet available at MacPorts). Is that 
>>>>> worth a try while also adding --enable-qt5=yes? (I need to keep MacPorts 
>>>>> Qt4 around for other stuff, I assume.)
>>>> 
>>>> This one I cannot answer. I'd try it probably.
>>>> 
>>>> But I fear this conflicts with the MacPorts way of doing things.
>>>> I'd guess you have to choose the active port of Qt after having
>>>> both versions installed and MacPorts will create some links to
>>>> the active version for you. I don't know.
>>>> 
>>>> Regards, Stephan
>>> 
>>> Hmmm It looks like there are activate and deactivate commands for 
>>> MacPorts. I don't know how they handle things if one programs wants one 
>>> version and another program wants another version. Seems like this wouldn't 
>>> be allowed in general but I might get away with playing around for a bit.
>> 
>> I've put a change in to add the necessary -rpath options to the linker 
>> command line.
>> These are required to use the self-made Qt5.5.x and probably for the 
>> frameworks built by Digia.
>> Look at git commit 6e9bd23a1f1888b2022335b2d05a3f770ada935a
>> 
>> I'm not sure if this is enough to use the Digia frameworks.
>> 
>> Regards, Stephan
>> 
> I tried building with your changes. Using the same script as before, errors 
> occur as such:
> 
> CXXLDlyx
> Undefined symbo

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 12:38 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote:

 Jean-Marc Lasgouttes wrote:
 
 Le 07/07/2015 01:07, Jerry a écrit :
   CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
 pars.insert(next(pars.begin(), pit),
 ^~~~
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
   candidate function [with _ForwardIter =
   std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
   std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 
 We had this error before. It probably means that your clang version provides 
 a std::next from the C++11 standard even if no C++11 standard is requested 
 on the command line. Since we do not try to detect ourselves anymore whether 
 C++98 or C++11 is used, we will probably see this more and more in the 
 future, and at some point in time we'll need to set the compiler commandline 
 option --std=C++98 if configure was not called with --enable-cxx11.
 
 What happens if you add --enable-cxx1 to the configure command-line?
 
 This should mean of course --enable-cxx11.
 
 
 Georg
 
 
 PS: The config log file looks good at a first glance. clang and libc++ are 
 correctly detected.
 
I added --enable-cxx11 to configure and removed the space--as discussed 
elsewhere in this thread--from the path to the Qt5 things. The compiler 
problems have gone away but now there appear to be problems linking Qt. Recall 
that the Qt version that I am attempting to reach is 5.5 downloaded from Qt's 
own web site.

Here is my build script:



#!/bin/bash

#  Create a build directory if one does not already exist.
cd /Applications/Words/LyXOuterFolder/git
mkdir -p build

# Clean out any previous build products but leave the build directory (*).
rm -rf /Applications/Words/LyXOuterFolder/git/build/*
rm -rf /Applications/Words/LyXOuterFolder/git/Contents/

cd /Applications/Words/LyXOuterFolder/git/lyx/
./autogen.sh

# Move to build directory and run configure that is in lyx directory.
cd /Applications/Words/LyXOuterFolder/git/build/
../lyx/configure \
--with-version-suffix=-2.X \
--with-libiconv-prefix=/usr/lib \
--with-x=no \
--disable-stdlib-debug \
--enable-cxx11 \
--prefix=/Applications/Words/LyXOuterFolder/git \

--with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/
make
make install-strip



Here are the last few lines with errors. The linker might have found my Qt4 
installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
/opt/local/ is the MacPorts stuff. FWIW the referenced library is here:

/Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a


  CXXLDlyx
Undefined symbols for architecture x86_64:
  
decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
 std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
lyx::frontend::GuiWorkArea*, void(void (lyx::frontend::GuiWorkArea::*)(), 
lyx::frontend::GuiWorkArea*), referenced from:
  boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
(lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
void::invoke(boost::detail::function::function_buffer) in 
liblyxqt4.a(GuiWorkArea.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [lyx] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2



Attached is my config log. It contains the lines

configure:2893: checking whether Qt5 is requested
configure:2902: result: no

Jerry



config.log
Description: Binary data

Re: Build questions for OS X

[Jerry]

On Jul 6, 2015, at 11:26 PM, Stephan Witt st.w...@gmx.net wrote:

 Can you send us your config.log privately, please?
 
 Stephan

Done. Sent to Stephan, JMarc, and Georg.
Jerry

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 4:20 PM, Jerry lancebo...@qwest.net wrote:

 The linker might have found my Qt4 installation from MacPorts. I don't know 
 if it is 32-bit or 64-bit or both.

It is 64-bit only.
Jerry

Re: Build questions for OS X

[Jerry]

On Jul 6, 2015, at 11:26 PM, Stephan Witt <st.w...@gmx.net> wrote:

> Can you send us your config.log privately, please?
> 
> Stephan

Done. Sent to Stephan, JMarc, and Georg.
Jerry

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 12:38 PM, Georg Baum <georg.b...@post.rwth-aachen.de> wrote:

> Jean-Marc Lasgouttes wrote:
> 
>> Le 07/07/2015 01:07, Jerry a écrit :
>>>   CXX  CutAndPaste.o
>>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>> pars.insert(next(pars.begin(), pit),
>>> ^~~~
>>> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>> note:
>>>   candidate function [with _ForwardIter =
>>>   std::__1::__list_iterator<lyx::Paragraph, void *>]
>>> next(_ForwardIter __x,
>>> ^
>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>   std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>>> inline It next(It i, Diff n = 1)
> 
> We had this error before. It probably means that your clang version provides 
> a std::next from the C++11 standard even if no C++11 standard is requested 
> on the command line. Since we do not try to detect ourselves anymore whether 
> C++98 or C++11 is used, we will probably see this more and more in the 
> future, and at some point in time we'll need to set the compiler commandline 
> option --std=C++98 if configure was not called with --enable-cxx11.
> 
>> What happens if you add --enable-cxx1 to the configure command-line?
> 
> This should mean of course --enable-cxx11.
> 
> 
> Georg
> 
> 
> PS: The config log file looks good at a first glance. clang and libc++ are 
> correctly detected.
> 
I added --enable-cxx11 to configure and removed the space--as discussed 
elsewhere in this thread--from the path to the Qt5 things. The compiler 
problems have gone away but now there appear to be problems linking Qt. Recall 
that the Qt version that I am attempting to reach is 5.5 downloaded from Qt's 
own web site.

Here is my build script:



#!/bin/bash

#  Create a build directory if one does not already exist.
cd /Applications/Words/LyXOuterFolder/git
mkdir -p build

# Clean out any previous build products but leave the build directory (*).
rm -rf /Applications/Words/LyXOuterFolder/git/build/*
rm -rf /Applications/Words/LyXOuterFolder/git/Contents/

cd /Applications/Words/LyXOuterFolder/git/lyx/
./autogen.sh

# Move to build directory and run configure that is in lyx directory.
cd /Applications/Words/LyXOuterFolder/git/build/
../lyx/configure \
--with-version-suffix=-2.X \
--with-libiconv-prefix=/usr/lib \
--with-x=no \
--disable-stdlib-debug \
--enable-cxx11 \
--prefix=/Applications/Words/LyXOuterFolder/git \

--with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/"
make
make install-strip



Here are the last few lines with errors. The linker might have found my Qt4 
installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
/opt/local/ is the MacPorts stuff. FWIW the referenced library is here:

/Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a


  CXXLDlyx
Undefined symbols for architecture x86_64:
  
"decltype(*(std::__1::forward<lyx::frontend::GuiWorkArea*&>(fp0)).*fp(std::__1::forward<>(fp1)))
 std::__1::__invoke(void (lyx::frontend::GuiWorkArea::*&&&)(), 
lyx::frontend::GuiWorkArea*&&&)", referenced from:
  boost::detail::function::void_function_obj_invoker0<std::__1::__bind, 
void>::invoke(boost::detail::function::function_buffer&) in 
liblyxqt4.a(GuiWorkArea.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [lyx] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2



Attached is my config log. It contains the lines

configure:2893: checking whether Qt5 is requested
configure:2902: result: no

Jerry



config.log
Description: Binary data

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 4:20 PM, Jerry <lancebo...@qwest.net> wrote:

> The linker might have found my Qt4 installation from MacPorts. I don't know 
> if it is 32-bit or 64-bit or both.

It is 64-bit only.
Jerry

Re: Build questions for OS X

[Jerry]

On Jul 5, 2015, at 10:58 PM, Stephan Witt st.w...@gmx.net wrote:
snip
 If anything I have said above makes it look like I have a clue what I am 
 doing it is wrong--I'm at least 50% clueless here.
 
 Which version/installation of Qt you'll use is determined by the 
 --with-qt-dir switch for autotools builds.
 In case you're using cmake as build system you have to set your PATH variable 
 appropriately.
 The directory where qmake is installed should come first, e.g. my cmake build 
 scripts contains
 export PATH=/Users/Shared/LyX/qt-5.4.2-frameworks-cocoa-x86_64/bin:${PATH}
 
 Regards, Stephan

Thanks for those remarks, Stephan.

Here is what I have done. I downloaded part of Qt from 
https://www.qt.io/download/; from the installer program provided therefrom, I 
selected only the gcc pre-built option. What I got was Qt Creator.app with 
frameworks installed inside the app bundle. This is version 5.5, new as of only 
a few days ago. The paths to the LyX repo and Qt frameworks are this:

/Applications/Words/LyXOuterFolder/git/lyx/
/Applications/Words/LyXOuterFolder/git/qt/Qt Creator.app/Contents/Frameworks/

I ran the following script which is slightly modified from the script in 
INSTALL.MacOSX:


#!/bin/bash
cd /Applications/Words/LyXOuterFolder/git/lyx/
  ./autogen.sh
  ./configure \
  --with-version-suffix=-2.3 \
  --with-libiconv-prefix=/usr/lib \
  --with-x=no \
  --disable-stdlib-debug \
  --prefix=/Applications/Words/LyXOuterFolder/git \
  --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
Creator.app/Contents/Frameworks/
  make
  make install-strip


I used the superstition of setting the version to 2.3 hoping that it might not 
clobber version 2.2 stuff in the Applications Support folder.

The process failed with these apparent C++ errors:




/Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
make[7]: Nothing to be done for `install-exec-am'.
make[7]: Nothing to be done for `install-data-am'.
Making install in .
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
Making install in .
  CXX  CutAndPaste.o
CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
pars.insert(next(pars.begin(), pit),
^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note: 
  candidate function [with _ForwardIter = 
std::__1::__list_iteratorlyx::Paragraph, void *]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
inline It next(It i, Diff n = 1)
  ^
CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
pars.insert(next(pars.begin(), pit + 1),
^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note: 
  candidate function [with _ForwardIter = 
std::__1::__list_iteratorlyx::Paragraph, void *]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
inline It next(It i, Diff n = 1)
  ^
CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
ParagraphList copy_pars(next(pars.begin(), startpit),
^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note: 
  candidate function [with _ForwardIter = 
std::__1::__list_const_iteratorlyx::Paragraph, void
  *]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_const_iteratorlyx::Paragraph, void *, Diff = long]
inline It next(It i, Diff n = 1)
  ^
3 errors generated.
make[4]: *** [CutAndPaste.o] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2




These notwithstanding, it looks like there could be Qt problems later. I 
spotted the following lines:

checking whether Qt5 is requested... no

and

Configuration
...
  Qt Frontend:
  Qt version:  4.8.7
...

Qt 4.8.7 is my MacPorts installation.

FWIW, I see that in config.log, this appears:

--with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
Creator.app/Contents/Frameworks/
  ^ note space

Notice that the quotes from my script have been removed.

Jerry

Re: Build questions for OS X

[Jerry]

On Jul 6, 2015, at 4:45 PM, Stephan Witt st.w...@gmx.net wrote:
 
 The process failed with these apparent C++ errors:
 
 I think I've seen these errors with Xcode 6 and the accompanying clang 
 compiler.
 It has something to do with cxx11 if I'm not mistaken. Sorry, I forgot the 
 details.
 I'm on Xcode 5 and Mac OS X 10.8.6 for my daily work.

I'm on OS X 10.9.5 and Xcode 5.1.1 so maybe it's not an Xcode issue. These 
problems appear to be either C coding errors or a clang error. In either case 
it will stop my build efforts because I don't know how to write C etc. FWIW I 
still have an older Xcode, 3.2.6, at /Developer/Applications/Xcode.app.

Should I report a bug for this?

Jerry

 
 /Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
 make[7]: Nothing to be done for `install-exec-am'.
 make[7]: Nothing to be done for `install-data-am'.
 Making install in .
 make[6]: Nothing to be done for `install-exec-am'.
 make[6]: Nothing to be done for `install-data-am'.
 Making install in .
 CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
   pars.insert(next(pars.begin(), pit),
   ^~~~
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
  note: 
 candidate function [with _ForwardIter = 
 std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
 std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 ^
 CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
   pars.insert(next(pars.begin(), pit + 1),
   ^~~~
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
  note: 
 candidate function [with _ForwardIter = 
 std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
 std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 ^
 CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
   ParagraphList copy_pars(next(pars.begin(), startpit),
   ^~~~
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
  note: 
 candidate function [with _ForwardIter = 
 std::__1::__list_const_iteratorlyx::Paragraph, void
 *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
 std::__1::__list_const_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 ^
 3 errors generated.
 make[4]: *** [CutAndPaste.o] Error 1
 make[3]: *** [install-recursive] Error 1
 make[2]: *** [install] Error 2
 make[1]: *** [install-recursive] Error 1
 make: *** [install-strip] Error 2
 
 
 
 
 These notwithstanding, it looks like there could be Qt problems later. I 
 spotted the following lines:
 
 checking whether Qt5 is requested... no
 
 and
 
 Configuration
 ...
 Qt Frontend:
 Qt version: 4.8.7
 ...
 
 Qt 4.8.7 is my MacPorts installation.
 
 FWIW, I see that in config.log, this appears:
 
 --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
 Creator.app/Contents/Frameworks/
 ^ note space
 
 Notice that the quotes from my script have been removed.
 
 Yes, that's the difference between the ideal and the real world.
 Unix is able to handle spaces in path names as long as nobody makes a mistake.
 One has to quote every path name variable in scripts - it is not automatic.
 Since the configure script is generated by auto tools I think it would be
 easier to solve it pragmatically instead of getting it right.
 
 The practical solution is to rename your Qt Creator application name and
 remove the space from path name. I think it doesn't break the app -
 at least it should not.
 
 Regards, Stephan

Re: Build questions for OS X

[Jerry]

On Jul 5, 2015, at 10:58 PM, Stephan Witt <st.w...@gmx.net> wrote:

>> If anything I have said above makes it look like I have a clue what I am 
>> doing it is wrong--I'm at least 50% clueless here.
> 
> Which version/installation of Qt you'll use is determined by the 
> --with-qt-dir switch for autotools builds.
> In case you're using cmake as build system you have to set your PATH variable 
> appropriately.
> The directory where qmake is installed should come first, e.g. my cmake build 
> scripts contains
> export PATH="/Users/Shared/LyX/qt-5.4.2-frameworks-cocoa-x86_64/bin:${PATH}"
> 
> Regards, Stephan

Thanks for those remarks, Stephan.

Here is what I have done. I downloaded part of Qt from 
https://www.qt.io/download/; from the installer program provided therefrom, I 
selected only the gcc pre-built option. What I got was Qt Creator.app with 
frameworks installed inside the app bundle. This is version 5.5, new as of only 
a few days ago. The paths to the LyX repo and Qt frameworks are this:

/Applications/Words/LyXOuterFolder/git/lyx/
/Applications/Words/LyXOuterFolder/git/qt/Qt Creator.app/Contents/Frameworks/

I ran the following script which is slightly modified from the script in 
INSTALL.MacOSX:


#!/bin/bash
cd /Applications/Words/LyXOuterFolder/git/lyx/
  ./autogen.sh
  ./configure \
  --with-version-suffix=-2.3 \
  --with-libiconv-prefix=/usr/lib \
  --with-x=no \
  --disable-stdlib-debug \
  --prefix=/Applications/Words/LyXOuterFolder/git \
  --with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt 
Creator.app/Contents/Frameworks/"
  make
  make install-strip


I used the superstition of setting the version to 2.3 hoping that it might not 
clobber version 2.2 stuff in the Applications Support folder.

The process failed with these apparent C++ errors:




/Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
make[7]: Nothing to be done for `install-exec-am'.
make[7]: Nothing to be done for `install-data-am'.
Making install in .
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
Making install in .
  CXX  CutAndPaste.o
CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
pars.insert(next(pars.begin(), pit),
^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note: 
  candidate function [with _ForwardIter = 
std::__1::__list_iterator<lyx::Paragraph, void *>]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
inline It next(It i, Diff n = 1)
  ^
CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
pars.insert(next(pars.begin(), pit + 1),
^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note: 
  candidate function [with _ForwardIter = 
std::__1::__list_iterator<lyx::Paragraph, void *>]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
inline It next(It i, Diff n = 1)
  ^
CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
ParagraphList copy_pars(next(pars.begin(), startpit),
^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note: 
  candidate function [with _ForwardIter = 
std::__1::__list_const_iterator<lyx::Paragraph, void
  *>]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_const_iterator<lyx::Paragraph, void *>, Diff = long]
inline It next(It i, Diff n = 1)
  ^
3 errors generated.
make[4]: *** [CutAndPaste.o] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2




These notwithstanding, it looks like there could be Qt problems later. I 
spotted the following lines:

checking whether Qt5 is requested... no

and

Configuration
...
  Qt Frontend:
  Qt version:  4.8.7
...

Qt 4.8.7 is my MacPorts installation.

FWIW, I see that in config.log, this appears:

--with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
Creator.app/Contents/Frameworks/
      ^ note space

Notice that the quotes from my script have been removed.

Jerry

Re: Build questions for OS X

[Jerry]

On Jul 6, 2015, at 4:45 PM, Stephan Witt <st.w...@gmx.net> wrote:
>> 
>> The process failed with these apparent C++ errors:
> 
> I think I've seen these errors with Xcode 6 and the accompanying clang 
> compiler.
> It has something to do with cxx11 if I'm not mistaken. Sorry, I forgot the 
> details.
> I'm on Xcode 5 and Mac OS X 10.8.6 for my daily work.

I'm on OS X 10.9.5 and Xcode 5.1.1 so maybe it's not an Xcode issue. These 
problems appear to be either C coding errors or a clang error. In either case 
it will stop my build efforts because I don't know how to write C etc. FWIW I 
still have an older Xcode, 3.2.6, at /Developer/Applications/Xcode.app.

Should I report a bug for this?

Jerry

> 
>> /Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
>> make[7]: Nothing to be done for `install-exec-am'.
>> make[7]: Nothing to be done for `install-data-am'.
>> Making install in .
>> make[6]: Nothing to be done for `install-exec-am'.
>> make[6]: Nothing to be done for `install-data-am'.
>> Making install in .
>> CXX  CutAndPaste.o
>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>   pars.insert(next(pars.begin(), pit),
>>   ^~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>  note: 
>> candidate function [with _ForwardIter = 
>> std::__1::__list_iterator<lyx::Paragraph, void *>]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>> std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>> inline It next(It i, Diff n = 1)
>> ^
>> CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
>>   pars.insert(next(pars.begin(), pit + 1),
>>   ^~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>  note: 
>> candidate function [with _ForwardIter = 
>> std::__1::__list_iterator<lyx::Paragraph, void *>]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>> std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>> inline It next(It i, Diff n = 1)
>> ^
>> CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
>>   ParagraphList copy_pars(next(pars.begin(), startpit),
>>   ^~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>  note: 
>> candidate function [with _ForwardIter = 
>> std::__1::__list_const_iterator<lyx::Paragraph, void
>> *>]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>> std::__1::__list_const_iterator<lyx::Paragraph, void *>, Diff = long]
>> inline It next(It i, Diff n = 1)
>> ^
>> 3 errors generated.
>> make[4]: *** [CutAndPaste.o] Error 1
>> make[3]: *** [install-recursive] Error 1
>> make[2]: *** [install] Error 2
>> make[1]: *** [install-recursive] Error 1
>> make: *** [install-strip] Error 2
>> 
>> 
>> 
>> 
>> These notwithstanding, it looks like there could be Qt problems later. I 
>> spotted the following lines:
>> 
>> checking whether Qt5 is requested... no
>> 
>> and
>> 
>> Configuration
>> ...
>> Qt Frontend:
>> Qt version: 4.8.7
>> ...
>> 
>> Qt 4.8.7 is my MacPorts installation.
>> 
>> FWIW, I see that in config.log, this appears:
>> 
>> --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
>> Creator.app/Contents/Frameworks/
>> ^ note space
>> 
>> Notice that the quotes from my script have been removed.
> 
> Yes, that's the difference between the ideal and the real world.
> Unix is able to handle spaces in path names as long as nobody makes a mistake.
> One has to quote every path name variable in scripts - it is not automatic.
> Since the configure script is generated by auto tools I think it would be
> easier to solve it pragmatically instead of getting it right.
> 
> The practical solution is to rename your Qt Creator application name and
> remove the space from path name. I think it doesn't break the app -
> at least it should not.
> 
> Regards, Stephan

Build questions for OS X

[Jerry]

I am attempting to build LyX on OS X for testing purposes, not distribution.

I have all of the prerequisites installed via MacPorts except possibly Qt, as 
described below.

I have done the git checkout and am looking at INSTALL.MacOSX.

The download link(s) in INSTALL.MacOSX for Qt are out of date, listing a 
trolltech web site and a Nokia FTP site. I found and downloaded a OS X 
installer from https://www.qt.io/download-open-source/ which promises to 
download binaries and source. Will this work? Can I download only binaries? I 
have not proceeded with this step because...

...INSTALL.MacOSX says to install Qt 4 but the qt.io site provides an installer 
only for Qt 5 with a pre-built option for only 64-bit. Will Qt 5 work? If not, 
where can I get Qt 4?...

...I already have Qt installed on my machine via MacPorts which reports that I 
have qt4-mac 4.8.7_0 as the active installation. qt5-mac 5.4.2 is available but 
not installed. Will a MacPorts version of Qt work? How?

If anything I have said above makes it look like I have a clue what I am doing 
it is wrong--I'm at least 50% clueless here.

Jerry

Build questions for OS X

[Jerry]

I am attempting to build LyX on OS X for testing purposes, not distribution.

I have all of the prerequisites installed via MacPorts except possibly Qt, as 
described below.

I have done the git checkout and am looking at INSTALL.MacOSX.

The download link(s) in INSTALL.MacOSX for Qt are out of date, listing a 
trolltech web site and a Nokia FTP site. I found and downloaded a OS X 
installer from https://www.qt.io/download-open-source/ which promises to 
download binaries and source. Will this work? Can I download only binaries? I 
have not proceeded with this step because...

...INSTALL.MacOSX says to install Qt 4 but the qt.io site provides an installer 
only for Qt 5 with a pre-built option for only 64-bit. Will Qt 5 work? If not, 
where can I get Qt 4?...

...I already have Qt installed on my machine via MacPorts which reports that I 
have qt4-mac 4.8.7_0 as the active installation. qt5-mac 5.4.2 is available but 
not installed. Will a MacPorts version of Qt work? How?

If anything I have said above makes it look like I have a clue what I am doing 
it is wrong--I'm at least 50% clueless here.

Jerry

Re: Will LyX 2.2 fix the OS X slow scrolling problem?

[Jerry]

On Jun 3, 2015, at 3:25 PM, Jerry lancebo...@qwest.net wrote:

 I see that MacPorts currently builds LyX 2.13.

Oops. 2.1.3.
Jerry

Re: Will LyX 2.2 fix the OS X slow scrolling problem?

[Jerry]

On Jun 3, 2015, at 8:24 AM, Scott Kostyshak skost...@lyx.org wrote:

 On Wed, Jun 3, 2015 at 10:46 AM, Jean-Marc Lasgouttes
 lasgout...@lyx.org wrote:
 Le 03/06/2015 02:26, Jerry a écrit :
 
 Will LyX 2.2 fix the OS X slow scrolling problem?
 
 Someone mentioned some time back that there is an experimental fix
 for the slow scrolling problem on OS X LyX but that it needs testing.
 I am willing to test. However, even further back while testing for
 another problem, I experienced difficulty building from source and
 the problems were not resolved (for me) so I abandoned those earlier
 efforts.
 
 
 Hi Jerry,
 
 Current master code (that will become 2.2) should indeed improve greatly the
 MacOS experience: faster, with proper kerning and retina support.
 
 If someone can either provide a binary or provide some dumb-guy-level
 instructions for checkout and building, I would be happy to take it
 from there. I already have git installed and can do a basic
 checkout.
 
 
 I'll let Stephan answer on what is the easiest way to build from scratch on
 Mac OS.
 
 I know almost nothing about Homebrew, but would it make sense to have
 a homebrew script?
 
 Scott

Yikes. I won't be installing Homebrew at this point because it will clobber my 
/usr/local. (If your question about Homebrew is about someone else installing 
Homebrew then please disregard the previous sentence.)

However, MacPorts doesn't clobber anything and I already have it installed. I 
see that MacPorts currently builds LyX 2.13.
https://trac.macports.org/browser/trunk/dports/aqua/LyX/Portfile

I have never built LyX from MacPorts, instead downloading the official 
binaries, but I would consider MacPorts a nice option--assuming someone else 
set up the portfile for 2.2. :-\

Jerry

Re: Will LyX 2.2 fix the OS X slow scrolling problem?

[Jerry]

On Jun 3, 2015, at 8:24 AM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Wed, Jun 3, 2015 at 10:46 AM, Jean-Marc Lasgouttes
> <lasgout...@lyx.org> wrote:
>> Le 03/06/2015 02:26, Jerry a écrit :
>>> 
>>> Will LyX 2.2 fix the OS X slow scrolling problem?
>>> 
>>> Someone mentioned some time back that there is an experimental fix
>>> for the slow scrolling problem on OS X LyX but that it needs testing.
>>> I am willing to test. However, even further back while testing for
>>> another problem, I experienced difficulty building from source and
>>> the problems were not resolved (for me) so I abandoned those earlier
>>> efforts.
>> 
>> 
>> Hi Jerry,
>> 
>> Current master code (that will become 2.2) should indeed improve greatly the
>> MacOS experience: faster, with proper kerning and retina support.
>> 
>>> If someone can either provide a binary or provide some dumb-guy-level
>>> instructions for checkout and building, I would be happy to take it
>>> from there. I already have git installed and can do a basic
>>> checkout.
>> 
>> 
>> I'll let Stephan answer on what is the easiest way to build from scratch on
>> Mac OS.
> 
> I know almost nothing about Homebrew, but would it make sense to have
> a homebrew script?
> 
> Scott

Yikes. I won't be installing Homebrew at this point because it will clobber my 
/usr/local. (If your question about Homebrew is about someone else installing 
Homebrew then please disregard the previous sentence.)

However, MacPorts doesn't clobber anything and I already have it installed. I 
see that MacPorts currently builds LyX 2.13.
https://trac.macports.org/browser/trunk/dports/aqua/LyX/Portfile

I have never built LyX from MacPorts, instead downloading the official 
binaries, but I would consider MacPorts a nice option--assuming someone else 
set up the portfile for 2.2. :-\

Jerry

Re: Will LyX 2.2 fix the OS X slow scrolling problem?

[Jerry]

On Jun 3, 2015, at 3:25 PM, Jerry <lancebo...@qwest.net> wrote:

> I see that MacPorts currently builds LyX 2.13.

Oops. 2.1.3.
Jerry

Will LyX 2.2 fix the OS X slow scrolling problem?

[Jerry]

Will LyX 2.2 fix the OS X slow scrolling problem?

Someone mentioned some time back that there is an experimental fix for the slow 
scrolling problem on OS X LyX but that it needs testing. I am willing to test. 
However, even further back while testing for another problem, I experienced 
difficulty building from source and the problems were not resolved (for me) so 
I abandoned those earlier efforts.

If someone can either provide a binary or provide some dumb-guy-level 
instructions for checkout and building, I would be happy to take it from there. 
I already have git installed and can do a basic checkout.

Jerry

Will LyX 2.2 fix the OS X slow scrolling problem?

[Jerry]

Will LyX 2.2 fix the OS X slow scrolling problem?

Someone mentioned some time back that there is an experimental fix for the slow 
scrolling problem on OS X LyX but that it needs testing. I am willing to test. 
However, even further back while testing for another problem, I experienced 
difficulty building from source and the problems were not resolved (for me) so 
I abandoned those earlier efforts.

If someone can either provide a binary or provide some dumb-guy-level 
instructions for checkout and building, I would be happy to take it from there. 
I already have git installed and can do a basic checkout.

Jerry

latex misbehavior on first launch of LyX 2.1.3 and earlier

[Jerry]

OS X 10.9.4 (Mavericks)
LyX 2.1.3 (today's release)
Late 2008 MacBook Pro

Recently (2.1.x ?), every time I initially launch a new version of LyX, I get 
high CPU usage (90+ % of one CPU) and high RAM (~200 MB) use by luatex while 
the system marks LyX as not responding. In the past, as I recall, I have 
force-quit LyX after a couple of minutes and re-launched. Today, however, I 
waited longer and started writing this note and just now got a crash report 
which I have pasted below. I did not force-quit LyX on the first launch and it 
now appears to be running OK, after maybe 4-5 minutes of lua-thrashing. The 
luatex process has quit and LyX seems to be running OK. Further quit-launch 
cycles show LyX continuing to work OK.

Jerry


Process: luatex [87588]
Path:/usr/local/texlive/2013/bin/x86_64-darwin/luatex
Identifier:  luatex
Version: ???
Code Type:   X86-64 (Native)
Parent Process:  Python [87585]
Responsible: lyx [87568]
User ID: 501

Date/Time:   2015-02-11 15:17:40.421 -0700
OS Version:  Mac OS X 10.9.4 (13E28)
Report Version:  11
Anonymous UUID:  deleted

Sleep/Wake UUID: deleted

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000c

VM Regions Near 0x000c:
-- shared memory  7ffdd000-7ffde000 [4K] r-x/r-x 
SM=SHM  


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   lualatex0x0001001301c8 0x1 + 1245640
1   lualatex0x000100133623 0x1 + 1259043
2   lualatex0x000100158868 0x1 + 1411176
3   lualatex0x000100199b3c 0x1 + 1678140
4   lualatex0x0001001bc3ea 0x1 + 1819626
5   lualatex0x0001001cd807 0x1 + 1890311
6   lualatex0x0001001bc658 0x1 + 1820248
7   lualatex0x0001001bb81c 0x1 + 1816604
8   lualatex0x0001001bb883 0x1 + 1816707
9   lualatex0x0001001b27cc 0x1 + 1779660
10  lualatex0x000129ff 0x1 + 10751
11  lualatex0x000133c4 0x1 + 13252
12  lualatex0x000100035db2 0x1 + 220594
13  lualatex0x00010003605b 0x1 + 221275
14  lualatex0x0001000d7d94 0x1 + 884116
15  lualatex0x0001000ae887 0x1 + 714887
16  lualatex0x0001000b1128 0x1 + 725288
17  lualatex0x0001000a8100 0x1 + 688384
18  lualatex0x00011b0e 0x1 + 6926
19  lualatex0x00011544 0x1 + 5444

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x  rbx: 0x025f  rcx: 0x024f  
rdx: 0x1278
  rdi: 0x000107aca390  rsi: 0x000107aca8b0  rbp: 0x7fff5fbfdf80  
rsp: 0x7fff5fbfdee0
   r8: 0x07ac0001   r9: 0x00010780  r10: 0x94b93107  
r11: 0x0001078424b0
  r12: 0x000107acdc30  r13: 0x000a  r14: 0x0002  
r15: 0x00010e21dec0
  rip: 0x0001001301c8  rfl: 0x00010202  cr2: 0x000c
  
Logical CPU: 1
Error Code:  0x0006
Trap Number: 14


Binary Images:
   0x1 -0x10072afef +lualatex (???) 
6CF1C250-DA48-34FC-931B-F2CE566F7DE0 /usr/texbin/lualatex
0x7fff6d6e8000 - 0x7fff6d71b817  dyld (239.4) 
042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A /usr/lib/dyld
0x7fff8be7c000 - 0x7fff8bebeff7  libauto.dylib (185.5) 
F45C36E8-B606-3886-B5B1-B6745E757CA8 /usr/lib/libauto.dylib
0x7fff8c128000 - 0x7fff8c139ff7  libsystem_asl.dylib (217.1.4) 
655FB343-52CF-3E2F-B14D-BEBF5AAEF94D /usr/lib/system/libsystem_asl.dylib
0x7fff8c19d000 - 0x7fff8c1c6ff7  libc++abi.dylib (49.1) 
21A807D3-6732-3455-B77F-743E9F916DF0 /usr/lib/libc++abi.dylib
0x7fff8c7cd000 - 0x7fff8c7e9ff7  libsystem_kernel.dylib (2422.110.17) 
873931CE-D1AF-3596-AADB-D2E63C9AB29F /usr/lib/system/libsystem_kernel.dylib
0x7fff8cb8f000 - 0x7fff8cb91ff3  libsystem_configuration.dylib (596.15) 
4998CB6A-9D54-390A-9F57-5D1AC53C135C 
/usr/lib/system/libsystem_configuration.dylib
0x7fff8e698000 - 0x7fff8e6e6ff9  libstdc++.6.dylib (60) 
0241E6A4-1368-33BE-950B-D0A175C41F54 /usr/lib/libstdc++.6.dylib
0x7fff8e7a2000 - 0x7fff8e7a3fff  libsystem_sandbox.dylib (278.11.1) 
0D0B13EA-6B7A-3AC8-BE60-B548543BEB77 /usr/lib/system/libsystem_sandbox.dylib
0x7fff8e7af000 - 0x7fff8e7b3ff7

latex misbehavior on first launch of LyX 2.1.3 and earlier

[Jerry]

OS X 10.9.4 (Mavericks)
LyX 2.1.3 (today's release)
Late 2008 MacBook Pro

Recently (2.1.x ?), every time I initially launch a new version of LyX, I get 
high CPU usage (90+ % of one CPU) and high RAM (~200 MB) use by luatex while 
the system marks LyX as "not responding." In the past, as I recall, I have 
force-quit LyX after a couple of minutes and re-launched. Today, however, I 
waited longer and started writing this note and just now got a crash report 
which I have pasted below. I did not force-quit LyX on the first launch and it 
now appears to be running OK, after maybe 4-5 minutes of lua-thrashing. The 
luatex process has quit and LyX seems to be running OK. Further quit-launch 
cycles show LyX continuing to work OK.

Jerry


Process: luatex [87588]
Path:/usr/local/texlive/2013/bin/x86_64-darwin/luatex
Identifier:  luatex
Version: ???
Code Type:   X86-64 (Native)
Parent Process:  Python [87585]
Responsible: lyx [87568]
User ID: 501

Date/Time:   2015-02-11 15:17:40.421 -0700
OS Version:  Mac OS X 10.9.4 (13E28)
Report Version:  11
Anonymous UUID:  deleted

Sleep/Wake UUID: deleted

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000c

VM Regions Near 0x000c:
--> shared memory  7ffdd000-7ffde000 [4K] r-x/r-x 
SM=SHM  


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   lualatex0x0001001301c8 0x1 + 1245640
1   lualatex0x000100133623 0x1 + 1259043
2   lualatex0x000100158868 0x1 + 1411176
3   lualatex0x000100199b3c 0x1 + 1678140
4   lualatex0x0001001bc3ea 0x1 + 1819626
5   lualatex0x0001001cd807 0x1 + 1890311
6   lualatex0x0001001bc658 0x1 + 1820248
7   lualatex0x0001001bb81c 0x1 + 1816604
8   lualatex0x0001001bb883 0x1 + 1816707
9   lualatex0x0001001b27cc 0x1 + 1779660
10  lualatex0x000129ff 0x1 + 10751
11  lualatex0x000133c4 0x1 + 13252
12  lualatex0x000100035db2 0x1 + 220594
13  lualatex0x00010003605b 0x1 + 221275
14  lualatex0x0001000d7d94 0x1 + 884116
15  lualatex0x0001000ae887 0x1 + 714887
16  lualatex0x0001000b1128 0x1 + 725288
17  lualatex0x0001000a8100 0x1 + 688384
18  lualatex0x00011b0e 0x1 + 6926
19  lualatex0x00011544 0x1 + 5444

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x  rbx: 0x025f  rcx: 0x024f  
rdx: 0x1278
  rdi: 0x000107aca390  rsi: 0x000107aca8b0  rbp: 0x7fff5fbfdf80  
rsp: 0x7fff5fbfdee0
   r8: 0x07ac0001   r9: 0x00010780  r10: 0x94b93107  
r11: 0x0001078424b0
  r12: 0x000107acdc30  r13: 0x000a  r14: 0x0002  
r15: 0x00010e21dec0
  rip: 0x0001001301c8  rfl: 0x00010202  cr2: 0x000c
  
Logical CPU: 1
Error Code:  0x0006
Trap Number: 14


Binary Images:
   0x1 -0x10072afef +lualatex (???) 
<6CF1C250-DA48-34FC-931B-F2CE566F7DE0> /usr/texbin/lualatex
0x7fff6d6e8000 - 0x7fff6d71b817  dyld (239.4) 
<042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld
0x7fff8be7c000 - 0x7fff8bebeff7  libauto.dylib (185.5) 
 /usr/lib/libauto.dylib
0x7fff8c128000 - 0x7fff8c139ff7  libsystem_asl.dylib (217.1.4) 
<655FB343-52CF-3E2F-B14D-BEBF5AAEF94D> /usr/lib/system/libsystem_asl.dylib
0x7fff8c19d000 - 0x7fff8c1c6ff7  libc++abi.dylib (49.1) 
<21A807D3-6732-3455-B77F-743E9F916DF0> /usr/lib/libc++abi.dylib
0x7fff8c7cd000 - 0x7fff8c7e9ff7  libsystem_kernel.dylib (2422.110.17) 
<873931CE-D1AF-3596-AADB-D2E63C9AB29F> /usr/lib/system/libsystem_kernel.dylib
0x7fff8cb8f000 - 0x7fff8cb91ff3  libsystem_configuration.dylib (596.15) 
<4998CB6A-9D54-390A-9F57-5D1AC53C135C> 
/usr/lib/system/libsystem_configuration.dylib
0x7fff8e698000 - 0x7fff8e6e6ff9  libstdc++.6.dylib (60) 
<0241E6A4-1368-33BE-950B-D0A175C41F54> /usr/lib/libstdc++.6.dylib
0x7fff8e7a2000 - 0x7fff8e7a3fff  libsystem_sandbox.dylib (278.11.1) 
<0D0B13EA-6B7A-3AC8-BE60-B548543BEB77> /usr/lib/system/li

[OT] Re: Computer Algebra Systems (octave)

[Jerry]

I'm curious to know what e-mail program you used to send this e-mail. On my 
computer, OS X 10.9.4, the message did not appear in the usual message window, 
but there was an .em. attachment that contained the message. I've seen this a 
few times lately and I'm wondering what the source is, and whether there is 
something wrong with my computer or if this is the result of a non-standard 
e-mail program. In the copy of your message below, you can see that the 
attachment has been removed but that the name remains in brackets  .

Jerry

On Nov 8, 2014, at 12:25 AM, Cyrille Artho c.ar...@aist.go.jp wrote:

 
 -- 
 Regards,
 Cyrille Artho - http://artho.com/
 Those who will not reason, are bigots, those who cannot,
 are fools, and those who dare not, are slaves.
   -- George Gordon Noel Byron
 Re: Computer Algebra Systems (octave).eml

[OT] Re: Computer Algebra Systems (octave)

[Jerry]

I'm curious to know what e-mail program you used to send this e-mail. On my 
computer, OS X 10.9.4, the message did not appear in the usual message window, 
but there was an .em. attachment that contained the message. I've seen this a 
few times lately and I'm wondering what the source is, and whether there is 
something wrong with my computer or if this is the result of a non-standard 
e-mail program. In the copy of your message below, you can see that the 
attachment has been removed but that the name remains in brackets < >.

Jerry

On Nov 8, 2014, at 12:25 AM, Cyrille Artho <c.ar...@aist.go.jp> wrote:

> 
> -- 
> Regards,
> Cyrille Artho - http://artho.com/
> Those who will not reason, are bigots, those who cannot,
> are fools, and those who dare not, are slaves.
>   -- George Gordon Noel Byron
> 

Re: Help with patch for word selection mode on double click

[Jerry]

On Oct 28, 2014, at 11:13 PM, Scott Kostyshak skost...@lyx.org wrote:

 On Tue, Oct 28, 2014 at 11:24 PM, Jerry lancebo...@qwest.net wrote:
 
 On Oct 28, 2014, at 4:03 AM, Scott Kostyshak skost...@lyx.org wrote:
 
 I have a patch that enables word selection mode on double click. It
 seems to work well. The patch is here:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
 
 The only major issue is that when dragging to the left, you cannot
 highlight the first word. Does anyone have an idea for where to fix
 this?
 
 The following patch might give a clue as to where the problem is. When
 applied, you can select the first word. It is not meant to be taken as
 a correct patch:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
 
 Scott
 
 Does this mean that upon a click-and-a-half, dragging extends the selection 
 by whole words?
 
 Yes. See http://www.lyx.org/trac/ticket/7890
 
 Scott

This is awesome.
Jerry

Re: Help with patch for word selection mode on double click

[Jerry]

On Oct 28, 2014, at 11:13 PM, Scott Kostyshak skost...@lyx.org wrote:

 On Tue, Oct 28, 2014 at 11:24 PM, Jerry lancebo...@qwest.net wrote:
 
 On Oct 28, 2014, at 4:03 AM, Scott Kostyshak skost...@lyx.org wrote:
 
 I have a patch that enables word selection mode on double click. It
 seems to work well. The patch is here:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
 
 The only major issue is that when dragging to the left, you cannot
 highlight the first word. Does anyone have an idea for where to fix
 this?
 
 The following patch might give a clue as to where the problem is. When
 applied, you can select the first word. It is not meant to be taken as
 a correct patch:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
 
 Scott
 
 Does this mean that upon a click-and-a-half, dragging extends the selection 
 by whole words?
 
 Yes. See http://www.lyx.org/trac/ticket/7890
 
 Scott

I just looked at the patch, and I not understanding it but recalling how LyX 
currently works, I should add that after a multi-word selection has been made, 
either in character-selection mode (including possibly partial words) or 
word-selection mode, there should be no cursor. Gone. Only the selected text, 
highlighted. Lyx currently shows selected text _and_ a blinking cursor, which 
is wrong by Mac standards and arguably just wrong. The reason, I suppose, is 
that having selected text and a blinking cursor present confusing signals: 
where will text appear if I type now? The answer is, of course, that all of the 
selected text will be replaced with the newly typed text, and the replacement 
will begin as soon as the first new character is typed. Thus, any blinking 
cursor before typing new text is sending the wrong message and is also 
irrelevant.

Jerry

Re: Help with patch for word selection mode on double click

[Jerry]

On Oct 29, 2014, at 1:30 AM, Jerry lancebo...@qwest.net wrote:

 
 On Oct 28, 2014, at 11:13 PM, Scott Kostyshak skost...@lyx.org wrote:
 
 On Tue, Oct 28, 2014 at 11:24 PM, Jerry lancebo...@qwest.net wrote:
 
 On Oct 28, 2014, at 4:03 AM, Scott Kostyshak skost...@lyx.org wrote:
 
 I have a patch that enables word selection mode on double click. It
 seems to work well. The patch is here:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
 
 The only major issue is that when dragging to the left, you cannot
 highlight the first word. Does anyone have an idea for where to fix
 this?
 
 The following patch might give a clue as to where the problem is. When
 applied, you can select the first word. It is not meant to be taken as
 a correct patch:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
 
 Scott
 
 Does this mean that upon a click-and-a-half, dragging extends the selection 
 by whole words?
 
 Yes. See http://www.lyx.org/trac/ticket/7890
 
 Scott
 
 I just looked at the patch, and I not understanding it but recalling how LyX 
 currently works, I should add that after a multi-word selection has been 
 made, either in character-selection mode (including possibly partial words) 
 or word-selection mode, there should be no cursor. Gone. Only the selected 
 text, highlighted. Lyx currently shows selected text _and_ a blinking cursor, 
 which is wrong by Mac standards and arguably just wrong. The reason, I 
 suppose, is that having selected text and a blinking cursor present confusing 
 signals: where will text appear if I type now? The answer is, of course, that 
 all of the selected text will be replaced with the newly typed text, and the 
 replacement will begin as soon as the first new character is typed. Thus, any 
 blinking cursor before typing new text is sending the wrong message and is 
 also irrelevant.
 
 Jerry

And of course the cursor reappears to the right side of the first typed new 
character.

Jerry

Re: Help with patch for word selection mode on double click

[Jerry]

On Oct 29, 2014, at 1:33 AM, Jerry lancebo...@qwest.net wrote:

 
 On Oct 29, 2014, at 1:30 AM, Jerry lancebo...@qwest.net wrote:
 
 
 On Oct 28, 2014, at 11:13 PM, Scott Kostyshak skost...@lyx.org wrote:
 
 On Tue, Oct 28, 2014 at 11:24 PM, Jerry lancebo...@qwest.net wrote:
 
 On Oct 28, 2014, at 4:03 AM, Scott Kostyshak skost...@lyx.org wrote:
 
 I have a patch that enables word selection mode on double click. It
 seems to work well. The patch is here:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
 
 The only major issue is that when dragging to the left, you cannot
 highlight the first word. Does anyone have an idea for where to fix
 this?
 
 The following patch might give a clue as to where the problem is. When
 applied, you can select the first word. It is not meant to be taken as
 a correct patch:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
 
 Scott
 
 Does this mean that upon a click-and-a-half, dragging extends the 
 selection by whole words?
 
 Yes. See http://www.lyx.org/trac/ticket/7890
 
 Scott
 
 I just looked at the patch, and I not understanding it but recalling how LyX 
 currently works, I should add that after a multi-word selection has been 
 made, either in character-selection mode (including possibly partial words) 
 or word-selection mode, there should be no cursor. Gone. Only the selected 
 text, highlighted. Lyx currently shows selected text _and_ a blinking 
 cursor, which is wrong by Mac standards and arguably just wrong. The reason, 
 I suppose, is that having selected text and a blinking cursor present 
 confusing signals: where will text appear if I type now? The answer is, of 
 course, that all of the selected text will be replaced with the newly typed 
 text, and the replacement will begin as soon as the first new character is 
 typed. Thus, any blinking cursor before typing new text is sending the wrong 
 message and is also irrelevant.
 
 Jerry
 
 And of course the cursor reappears to the right side of the first typed new 
 character.
 
 Jerry
 
And finally Why doesn't Qt handle this more or less automatically? I don't 
recall seeing this problem on other Qt-based text editing programs.

Jerry

Re: Help with patch for "word selection mode" on double click

[Jerry]

On Oct 28, 2014, at 11:13 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Tue, Oct 28, 2014 at 11:24 PM, Jerry <lancebo...@qwest.net> wrote:
>> 
>> On Oct 28, 2014, at 4:03 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>> 
>>> I have a patch that enables "word selection mode" on double click. It
>>> seems to work well. The patch is here:
>>> 
>>> http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
>>> 
>>> The only major issue is that when dragging to the left, you cannot
>>> highlight the first word. Does anyone have an idea for where to fix
>>> this?
>>> 
>>> The following patch might give a clue as to where the problem is. When
>>> applied, you can select the first word. It is not meant to be taken as
>>> a correct patch:
>>> 
>>> http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
>>> 
>>> Scott
>> 
>> Does this mean that upon a click-and-a-half, dragging extends the selection 
>> by whole words?
> 
> Yes. See http://www.lyx.org/trac/ticket/7890
> 
> Scott

This is awesome.
Jerry

Re: Help with patch for "word selection mode" on double click

[Jerry]

On Oct 28, 2014, at 11:13 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Tue, Oct 28, 2014 at 11:24 PM, Jerry <lancebo...@qwest.net> wrote:
>> 
>> On Oct 28, 2014, at 4:03 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>> 
>>> I have a patch that enables "word selection mode" on double click. It
>>> seems to work well. The patch is here:
>>> 
>>> http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
>>> 
>>> The only major issue is that when dragging to the left, you cannot
>>> highlight the first word. Does anyone have an idea for where to fix
>>> this?
>>> 
>>> The following patch might give a clue as to where the problem is. When
>>> applied, you can select the first word. It is not meant to be taken as
>>> a correct patch:
>>> 
>>> http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
>>> 
>>> Scott
>> 
>> Does this mean that upon a click-and-a-half, dragging extends the selection 
>> by whole words?
> 
> Yes. See http://www.lyx.org/trac/ticket/7890
> 
> Scott

I just looked at the patch, and I not understanding it but recalling how LyX 
currently works, I should add that after a multi-word selection has been made, 
either in character-selection mode (including possibly partial words) or 
word-selection mode, there should be no cursor. Gone. Only the selected text, 
highlighted. Lyx currently shows selected text _and_ a blinking cursor, which 
is wrong by Mac standards and arguably just wrong. The reason, I suppose, is 
that having selected text and a blinking cursor present confusing signals: 
where will text appear if I type now? The answer is, of course, that all of the 
selected text will be replaced with the newly typed text, and the replacement 
will begin as soon as the first new character is typed. Thus, any blinking 
cursor before typing new text is sending the wrong message and is also 
irrelevant.

Jerry

Re: Help with patch for "word selection mode" on double click

[Jerry]

On Oct 29, 2014, at 1:30 AM, Jerry <lancebo...@qwest.net> wrote:

> 
> On Oct 28, 2014, at 11:13 PM, Scott Kostyshak <skost...@lyx.org> wrote:
> 
>> On Tue, Oct 28, 2014 at 11:24 PM, Jerry <lancebo...@qwest.net> wrote:
>>> 
>>> On Oct 28, 2014, at 4:03 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>>> 
>>>> I have a patch that enables "word selection mode" on double click. It
>>>> seems to work well. The patch is here:
>>>> 
>>>> http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
>>>> 
>>>> The only major issue is that when dragging to the left, you cannot
>>>> highlight the first word. Does anyone have an idea for where to fix
>>>> this?
>>>> 
>>>> The following patch might give a clue as to where the problem is. When
>>>> applied, you can select the first word. It is not meant to be taken as
>>>> a correct patch:
>>>> 
>>>> http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
>>>> 
>>>> Scott
>>> 
>>> Does this mean that upon a click-and-a-half, dragging extends the selection 
>>> by whole words?
>> 
>> Yes. See http://www.lyx.org/trac/ticket/7890
>> 
>> Scott
> 
> I just looked at the patch, and I not understanding it but recalling how LyX 
> currently works, I should add that after a multi-word selection has been 
> made, either in character-selection mode (including possibly partial words) 
> or word-selection mode, there should be no cursor. Gone. Only the selected 
> text, highlighted. Lyx currently shows selected text _and_ a blinking cursor, 
> which is wrong by Mac standards and arguably just wrong. The reason, I 
> suppose, is that having selected text and a blinking cursor present confusing 
> signals: where will text appear if I type now? The answer is, of course, that 
> all of the selected text will be replaced with the newly typed text, and the 
> replacement will begin as soon as the first new character is typed. Thus, any 
> blinking cursor before typing new text is sending the wrong message and is 
> also irrelevant.
> 
> Jerry

And of course the cursor reappears to the right side of the first typed new 
character.

Jerry

Re: Help with patch for "word selection mode" on double click

[Jerry]

On Oct 29, 2014, at 1:33 AM, Jerry <lancebo...@qwest.net> wrote:

> 
> On Oct 29, 2014, at 1:30 AM, Jerry <lancebo...@qwest.net> wrote:
> 
>> 
>> On Oct 28, 2014, at 11:13 PM, Scott Kostyshak <skost...@lyx.org> wrote:
>> 
>>> On Tue, Oct 28, 2014 at 11:24 PM, Jerry <lancebo...@qwest.net> wrote:
>>>> 
>>>> On Oct 28, 2014, at 4:03 AM, Scott Kostyshak <skost...@lyx.org> wrote:
>>>> 
>>>>> I have a patch that enables "word selection mode" on double click. It
>>>>> seems to work well. The patch is here:
>>>>> 
>>>>> http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
>>>>> 
>>>>> The only major issue is that when dragging to the left, you cannot
>>>>> highlight the first word. Does anyone have an idea for where to fix
>>>>> this?
>>>>> 
>>>>> The following patch might give a clue as to where the problem is. When
>>>>> applied, you can select the first word. It is not meant to be taken as
>>>>> a correct patch:
>>>>> 
>>>>> http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
>>>>> 
>>>>> Scott
>>>> 
>>>> Does this mean that upon a click-and-a-half, dragging extends the 
>>>> selection by whole words?
>>> 
>>> Yes. See http://www.lyx.org/trac/ticket/7890
>>> 
>>> Scott
>> 
>> I just looked at the patch, and I not understanding it but recalling how LyX 
>> currently works, I should add that after a multi-word selection has been 
>> made, either in character-selection mode (including possibly partial words) 
>> or word-selection mode, there should be no cursor. Gone. Only the selected 
>> text, highlighted. Lyx currently shows selected text _and_ a blinking 
>> cursor, which is wrong by Mac standards and arguably just wrong. The reason, 
>> I suppose, is that having selected text and a blinking cursor present 
>> confusing signals: where will text appear if I type now? The answer is, of 
>> course, that all of the selected text will be replaced with the newly typed 
>> text, and the replacement will begin as soon as the first new character is 
>> typed. Thus, any blinking cursor before typing new text is sending the wrong 
>> message and is also irrelevant.
>> 
>> Jerry
> 
> And of course the cursor reappears to the right side of the first typed new 
> character.
> 
> Jerry
> 
And finally Why doesn't Qt handle this more or less automatically? I don't 
recall seeing this problem on other Qt-based text editing programs.

Jerry

Re: Help with patch for word selection mode on double click

[Jerry]

On Oct 28, 2014, at 4:03 AM, Scott Kostyshak skost...@lyx.org wrote:

 I have a patch that enables word selection mode on double click. It
 seems to work well. The patch is here:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
 
 The only major issue is that when dragging to the left, you cannot
 highlight the first word. Does anyone have an idea for where to fix
 this?
 
 The following patch might give a clue as to where the problem is. When
 applied, you can select the first word. It is not meant to be taken as
 a correct patch:
 
 http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
 
 Scott

Does this mean that upon a click-and-a-half, dragging extends the selection by 
whole words?

Jerry

Re: Help with patch for "word selection mode" on double click

[Jerry]

On Oct 28, 2014, at 4:03 AM, Scott Kostyshak <skost...@lyx.org> wrote:

> I have a patch that enables "word selection mode" on double click. It
> seems to work well. The patch is here:
> 
> http://www.lyx.org/trac/attachment/ticket/7890/0001-Fix-9160-and-7890.patch
> 
> The only major issue is that when dragging to the left, you cannot
> highlight the first word. Does anyone have an idea for where to fix
> this?
> 
> The following patch might give a clue as to where the problem is. When
> applied, you can select the first word. It is not meant to be taken as
> a correct patch:
> 
> http://www.lyx.org/trac/attachment/ticket/7890/0002-HACK-just-to-show-where-the-problem-is.patch
> 
> Scott

Does this mean that upon a click-and-a-half, dragging extends the selection by 
whole words?

Jerry

Re: #9157: Equation Number Problem

[Jerry]

On Jun 9, 2014, at 8:07 AM, Shawn ODonoghue sodon...@indiana.edu wrote:

 Thank you for the quick response.
 
 Everything worked as you described.
 
 Shawn
 
 
 On Mon, Jun 9, 2014 at 5:50 AM, LyX Ticket Tracker t...@lyx.org wrote:
 #9157: Equation Number Problem
 -+-
  Reporter:  sodonogh |   Owner:  lasgouttes
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone:
 Component:  general  | Version:  2.1.0
  Severity:  normal   |  Resolution:
  Keywords:  equation number  |
 -+-
 
 Comment (by skostysh):
 
  Hi Shawn,
 
  Thanks for the report. I think the problem is that you are using instant
  preview (to check, go to Tools  Preferences  Look  Feel  Display and
  see if Instant Preview is set to On). To turn this off, change it to
  Off or No math. As to why instant preview leads to this behavior, it's
  because each math chunk is rendered independently. So they are all
  equation 1.
 
 --
 Ticket URL: http://www.lyx.org/trac/ticket/9157#comment:1
 The LyX Project http://www.lyx.org/
 LyX -- The Document Processor
 
I don't mean to butt in here but why was this ticket closed? The problem 
remains, that is, equation numbering in instant preview mode does not work.

Jerry

Re: #9157: Equation Number Problem

[Jerry]

On Jun 9, 2014, at 6:50 PM, Scott Kostyshak skost...@lyx.org wrote:

 On Mon, Jun 9, 2014 at 9:09 PM, Jerry lancebo...@qwest.net wrote:
 
 On Jun 9, 2014, at 8:07 AM, Shawn ODonoghue sodon...@indiana.edu wrote:
 
 Thank you for the quick response.
 
 Everything worked as you described.
 
 Shawn
 
 
 On Mon, Jun 9, 2014 at 5:50 AM, LyX Ticket Tracker t...@lyx.org wrote:
 
 #9157: Equation Number Problem
 -+-
 Reporter:  sodonogh |   Owner:  lasgouttes
 Type:  defect   |  Status:  new
 Priority:  normal   |   Milestone:
 Component:  general  | Version:  2.1.0
 Severity:  normal   |  Resolution:
 Keywords:  equation number  |
 -+-
 
 Comment (by skostysh):
 
 Hi Shawn,
 
 Thanks for the report. I think the problem is that you are using instant
 preview (to check, go to Tools  Preferences  Look  Feel  Display and
 see if Instant Preview is set to On). To turn this off, change it to
 Off or No math. As to why instant preview leads to this behavior,
 it's
 because each math chunk is rendered independently. So they are all
 equation 1.
 
 --
 Ticket URL: http://www.lyx.org/trac/ticket/9157#comment:1
 The LyX Project http://www.lyx.org/
 LyX -- The Document Processor
 
 
 Hi Jerry,
 
 I don't mean to butt in here
 
 Feedback is always welcome! Please butt in wherever you think fit :)
 But please if it it's feedback regarding an issue on trac, post any
 relevant information there. Otherwise important information sent
 through emails will be lost when one looks at the issue.

Of course. It was just me being lazy.
 
 but why was this ticket closed? The problem
 remains, that is, equation numbering in instant preview mode does not work.
 
 I'll update the bug report. It's a duplicate of another bug. I didn't
 want to take time to find the bug it's a duplicate of and I got the
 feeling that the OP viewed the problem as solved. In other words, I
 was lazy. Thanks for keeping me in check.

OK. Thanks.
Jerry
 
 Scott

Re: #9157: Equation Number Problem

[Jerry]

On Jun 9, 2014, at 8:07 AM, Shawn ODonoghue <sodon...@indiana.edu> wrote:

> Thank you for the quick response.
> 
> Everything worked as you described.
> 
> Shawn
> 
> 
> On Mon, Jun 9, 2014 at 5:50 AM, LyX Ticket Tracker <t...@lyx.org> wrote:
> #9157: Equation Number Problem
> -+-
>  Reporter:  sodonogh |   Owner:  lasgouttes
>  Type:  defect   |  Status:  new
>  Priority:  normal   |   Milestone:
> Component:  general  | Version:  2.1.0
>  Severity:  normal   |  Resolution:
>  Keywords:  equation number  |
> -+-
> 
> Comment (by skostysh):
> 
>  Hi Shawn,
> 
>  Thanks for the report. I think the problem is that you are using instant
>  preview (to check, go to Tools > Preferences > Look & Feel > Display and
>  see if Instant Preview is set to "On"). To turn this off, change it to
>  "Off" or "No math". As to why instant preview leads to this behavior, it's
>  because each math chunk is rendered independently. So they are all
>  equation 1.
> 
> --
> Ticket URL: <http://www.lyx.org/trac/ticket/9157#comment:1>
> The LyX Project <http://www.lyx.org/>
> LyX -- The Document Processor
> 
I don't mean to butt in here but why was this ticket closed? The problem 
remains, that is, equation numbering in instant preview mode does not work.

Jerry

Re: #9157: Equation Number Problem

[Jerry]

On Jun 9, 2014, at 6:50 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Mon, Jun 9, 2014 at 9:09 PM, Jerry <lancebo...@qwest.net> wrote:
>> 
>> On Jun 9, 2014, at 8:07 AM, Shawn ODonoghue <sodon...@indiana.edu> wrote:
>> 
>> Thank you for the quick response.
>> 
>> Everything worked as you described.
>> 
>> Shawn
>> 
>> 
>> On Mon, Jun 9, 2014 at 5:50 AM, LyX Ticket Tracker <t...@lyx.org> wrote:
>>> 
>>> #9157: Equation Number Problem
>>> -+-
>>> Reporter:  sodonogh |   Owner:  lasgouttes
>>> Type:  defect   |  Status:  new
>>> Priority:  normal   |   Milestone:
>>> Component:  general  | Version:  2.1.0
>>> Severity:  normal   |  Resolution:
>>> Keywords:  equation number  |
>>> -+-
>>> 
>>> Comment (by skostysh):
>>> 
>>> Hi Shawn,
>>> 
>>> Thanks for the report. I think the problem is that you are using instant
>>> preview (to check, go to Tools > Preferences > Look & Feel > Display and
>>> see if Instant Preview is set to "On"). To turn this off, change it to
>>> "Off" or "No math". As to why instant preview leads to this behavior,
>>> it's
>>> because each math chunk is rendered independently. So they are all
>>> equation 1.
>>> 
>>> --
>>> Ticket URL: <http://www.lyx.org/trac/ticket/9157#comment:1>
>>> The LyX Project <http://www.lyx.org/>
>>> LyX -- The Document Processor
>> 
> 
> Hi Jerry,
> 
>> I don't mean to butt in here
> 
> Feedback is always welcome! Please butt in wherever you think fit :)
> But please if it it's feedback regarding an issue on trac, post any
> relevant information there. Otherwise important information sent
> through emails will be lost when one looks at the issue.

Of course. It was just me being lazy.
> 
>> but why was this ticket closed? The problem
>> remains, that is, equation numbering in instant preview mode does not work.
> 
> I'll update the bug report. It's a duplicate of another bug. I didn't
> want to take time to find the bug it's a duplicate of and I got the
> feeling that the OP viewed the problem as solved. In other words, I
> was lazy. Thanks for keeping me in check.

OK. Thanks.
Jerry
> 
> Scott

Re: Tarballs for LyX 2.1.0 are on FTP

[Jerry]

On Apr 16, 2014, at 11:17 PM, Stephan Witt st.w...@gmx.net wrote:

 Am 14.04.2014 um 19:47 schrieb Vincent van Ravesteijn v...@lyx.org:
 
 Hi all,
 
 The tarballs for LyX 2.1.0 can be found at
 
 ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
 
 As usual I'll wait for the packagers to provide the binaries before 
 announcing the release.
 
 The package for mac is here:
 
 https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.0%2Bqt4-cocoa.dmg
 https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.0%2Bqt4-cocoa.dmg.sig
 
 Stephan

Dumb question no doubt, but what is the purpose of the .sig file? Is this 
related to codesigning?
Jerry

Re: Tarballs for LyX 2.1.0 are on FTP

[Jerry]

On Apr 16, 2014, at 11:17 PM, Stephan Witt <st.w...@gmx.net> wrote:

> Am 14.04.2014 um 19:47 schrieb Vincent van Ravesteijn <v...@lyx.org>:
> 
>> Hi all,
>> 
>> The tarballs for LyX 2.1.0 can be found at
>> 
>> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
>> 
>> As usual I'll wait for the packagers to provide the binaries before 
>> announcing the release.
> 
> The package for mac is here:
> 
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.0%2Bqt4-cocoa.dmg
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.0%2Bqt4-cocoa.dmg.sig
> 
> Stephan

Dumb question no doubt, but what is the purpose of the .sig file? Is this 
related to codesigning?
Jerry

Slow scrolling on OS X in 2.1 fixed?

[Jerry]

I see the recent postings about 2.1 in OS X but I still don't see any (further) 
discussion of fixing the slow scrolling problem. I recall that there had been 
some work on this but that it isn't ready for releasing yet. For day-to-day 
use, this, in my opinion, is the single most important thing that makes LyX 
less than a complete joy to use.

I noticed recently that if the pixmap cache is enabled _and_ if 
force_paint_single_char is set to 0, scrolling speed is comparable to that of 
other OS X programs. But of course force_paint_single_char to 0 causes a 
misplaced text cursor, and using the pixmap cache causes text to rendered 
without subpixel antialiasing which to the Mac user's eye results in faint, 
fuzzy text.

Will OS X scrolling be fixed in 2.1?

Jerry

Re: Slow scrolling on OS X in 2.1 fixed?

[Jerry]

On Mar 3, 2014, at 8:15 AM, Richard Heck rgh...@lyx.org wrote:

 On 03/03/2014 05:39 AM, Jean-Marc Lasgouttes wrote:
 03/03/2014 11:16, Jerry:
 I see the recent postings about 2.1 in OS X but I still don't see any
 (further) discussion of fixing the slow scrolling problem. I recall
 that there had been some work on this but that it isn't ready for
 releasing yet. For day-to-day use, this, in my opinion, is the single
 most important thing that makes LyX less than a complete joy to use.
 
 I noticed recently that if the pixmap cache is enabled _and_ if
 force_paint_single_char is set to 0, scrolling speed is comparable to
 that of other OS X programs. But of course force_paint_single_char to
 0 causes a misplaced text cursor, and using the pixmap cache causes
 text to rendered without subpixel antialiasing which to the Mac
 user's eye results in faint, fuzzy text.
 
 Will OS X scrolling be fixed in 2.1?
 
 It will unfortunately not be fixed. I have a branch
 (features/str-metrics) that contains code almost ready to be wildly
 tested, but it has not landed to main git yet. This means that this is
 2.2 material.
 
 Note, Jerry, that you can use and test JMarc's branch, if you are able to
 compile LyX yourself.

I've tried and failed to build from git in the past but when I get time I'll 
give it another go.

I appreciate the work on this and apologize for sounding like a broken record. 
I hope to provide some testing feedback at some point.

Jerry
 
 We plan to make 2.2 happen earlier than usual, but we
 never managed to honor such promises in the past.
 
 This time will be different.
 
 Richard
 

Slow scrolling on OS X in 2.1 fixed?

[Jerry]

I see the recent postings about 2.1 in OS X but I still don't see any (further) 
discussion of fixing the slow scrolling problem. I recall that there had been 
some work on this but that it isn't ready for releasing yet. For day-to-day 
use, this, in my opinion, is the single most important thing that makes LyX 
less than a complete joy to use.

I noticed recently that if the pixmap cache is enabled _and_ if 
force_paint_single_char is set to 0, scrolling speed is comparable to that of 
other OS X programs. But of course force_paint_single_char to 0 causes a 
misplaced text cursor, and using the pixmap cache causes text to rendered 
without subpixel antialiasing which to the Mac user's eye results in faint, 
fuzzy text.

Will OS X scrolling be fixed in 2.1?

Jerry

Re: Slow scrolling on OS X in 2.1 fixed?

[Jerry]

On Mar 3, 2014, at 8:15 AM, Richard Heck <rgh...@lyx.org> wrote:

> On 03/03/2014 05:39 AM, Jean-Marc Lasgouttes wrote:
>> 03/03/2014 11:16, Jerry:
>>> I see the recent postings about 2.1 in OS X but I still don't see any
>>> (further) discussion of fixing the slow scrolling problem. I recall
>>> that there had been some work on this but that it isn't ready for
>>> releasing yet. For day-to-day use, this, in my opinion, is the single
>>> most important thing that makes LyX less than a complete joy to use.
>>> 
>>> I noticed recently that if the pixmap cache is enabled _and_ if
>>> force_paint_single_char is set to 0, scrolling speed is comparable to
>>> that of other OS X programs. But of course force_paint_single_char to
>>> 0 causes a misplaced text cursor, and using the pixmap cache causes
>>> text to rendered without subpixel antialiasing which to the Mac
>>> user's eye results in faint, fuzzy text.
>>> 
>>> Will OS X scrolling be fixed in 2.1?
>> 
>> It will unfortunately not be fixed. I have a branch
>> (features/str-metrics) that contains code almost ready to be wildly
>> tested, but it has not landed to main git yet. This means that this is
>> 2.2 material.
> 
> Note, Jerry, that you can use and test JMarc's branch, if you are able to
> compile LyX yourself.

I've tried and failed to build from git in the past but when I get time I'll 
give it another go.

I appreciate the work on this and apologize for sounding like a broken record. 
I hope to provide some testing feedback at some point.

Jerry
> 
>> We plan to make 2.2 happen earlier than usual, but we
>> never managed to honor such promises in the past.
> 
> This time will be different.
> 
> Richard
> 

Re: GSOC 2014 project list: on LyX--docx roundtrip conversion

[Jerry]

On Feb 6, 2014, at 10:35 AM, stefano franchi stefano.fran...@gmail.com wrote:

 The first project in our wiki page for GSOC 2014:
 
 http://wiki.lyx.org/GSoC/GSoCProjectIdeasFor2014
 
 is, at the same time, the most ambitious and the least well-defined (possibly 
 because the former implies the latter).
 
 It is not clear to me if this a coding project or if it defines the outline 
 of a preliminary non-coding feasibility study that would, at most, produce a 
 document describing the minimal-lyx and minimal-docx feature sets (plus, 
 possibly, a minimal-lyx-layout and a minimal-doc-template).
 
 Any thought on how to make it more focused?
 
 Perhaps we could define the goals as:
 
 1. Define a minimal-lyx feature set (I.e. the supported LyX/LaTeX features)
 2. Write a corresponding lyx-layout
 3. Define a minimal-doc feature set  (Word/ODF features corresponding to (1)
 4, Write a Word/OO template (the set of styles corresponding to 2)
 5. Provide an automated path from 1 to 4 and back using glue-code and 
 existing internal and external tools (e.g.: LyX export functions to 
 XHTML/EPub, eLyxer, pandoc, writer2latex, etc).
 
 I am not sure points 1-5 above capture the existing description, partly 
 because I am not sure about what is meant by develop a framework. Perhaps 
 my summary caputeres the subgoal only?
 
 Stefano

One can hope (right?) that since a commonality between LyX and docx is math 
that this would be included on the feature set(s). On OS X, the new versions of 
Word have a built-in math typesetting capability (and thus no longer depends on 
MathType). Presumably this is allowed by the docx format and presumably this is 
also an aspect of Windows Word. Autonumbering would also be hoped for.

Jerry

 
 
 -- 
 __
 Stefano Franchi
 Associate Research Professor
 Department of Hispanic Studies Ph:   +1 (979) 845-2125
 Texas AM University  Fax:  +1 (979) 845-6421
 College Station, Texas, USA
 
 stef...@tamu.edu
 http://stefano.cleinias.org

Re: GSOC 2014 project list: on LyX<-->docx roundtrip conversion

[Jerry]

On Feb 6, 2014, at 10:35 AM, stefano franchi <stefano.fran...@gmail.com> wrote:

> The first project in our wiki page for GSOC 2014:
> 
> http://wiki.lyx.org/GSoC/GSoCProjectIdeasFor2014
> 
> is, at the same time, the most ambitious and the least well-defined (possibly 
> because the former implies the latter).
> 
> It is not clear to me if this a coding project or if it defines the outline 
> of a preliminary non-coding feasibility study that would, at most, produce a 
> document describing the minimal-lyx and minimal-docx feature sets (plus, 
> possibly, a minimal-lyx-layout and a minimal-doc-template).
> 
> Any thought on how to make it more focused?
> 
> Perhaps we could define the goals as:
> 
> 1. Define a minimal-lyx feature set (I.e. the supported LyX/LaTeX features)
> 2. Write a corresponding lyx-layout
> 3. Define a minimal-doc feature set  (Word/ODF features corresponding to (1)
> 4, Write a Word/OO template (the set of styles corresponding to 2)
> 5. Provide an automated path from 1 to 4 and back using glue-code and 
> existing internal and external tools (e.g.: LyX export functions to 
> XHTML/EPub, eLyxer, pandoc, writer2latex, etc).
> 
> I am not sure points 1-5 above capture the existing description, partly 
> because I am not sure about what is meant by "develop a framework". Perhaps 
> my summary caputeres the subgoal only?
> 
> Stefano

One can hope (right?) that since a commonality between LyX and docx is math 
that this would be included on the feature set(s). On OS X, the new versions of 
Word have a built-in math typesetting capability (and thus no longer depends on 
MathType). Presumably this is allowed by the docx format and presumably this is 
also an aspect of Windows Word. Autonumbering would also be hoped for.

Jerry

> 
> 
> -- 
> __
> Stefano Franchi
> Associate Research Professor
> Department of Hispanic Studies Ph:   +1 (979) 845-2125
> Texas A University  Fax:  +1 (979) 845-6421
> College Station, Texas, USA
> 
> stef...@tamu.edu
> http://stefano.cleinias.org

Re: annual survery of LyX users

[Jerry]

On Jun 19, 2013, at 11:36 AM, Scott Kostyshak skost...@lyx.org wrote:

 LyX users influence development by posting tickets on trac. A few
 brave users participate in discussions on lyx-devel. I think there is
 a clear way for LyX users who would like to get in touch with LyX
 developers. I think the other way is less obvious.
 
 I often find myself thinking I wonder what most users think about
 this. I could send an email to the lyx-users list, but most of the
 time I don't because i would only expect a couple to respond and that
 wouldn't really give me an idea of what most users think.
 
 I propose the following: an annual survey of LyX users.

I think this is a great idea.

Having thought about it for all of five seconds now, would it make sense to 
solicit the users' list before each survey to get ideas for the survey, then 
follow up with some benevolent editing to create the actual survey?

Jerry

 What I am most
 interested in asking users is do they prefer X or Y?. For example, I
 proposed a recent patch that really comes down to a preference. A
 couple of developers confirmed this, and I just planned on forgetting
 about it. But then I realized that just because a patch includes a
 personal preference doesn't necessarily mean it should be rejected.
 Developers could vote on it, but it would also be nice to get input
 from users.
 
 This could be qualitative, such as here are a list of enhancements
 that are being debated for inclusion in LyX 2.2. What are your
 thoughts? or we could make it quantitative if you have sent more
 than N emails to lyx-users or lyx-devel in the past year, you can
 vote. And perhaps 2/3 majority would be required for an enhancement
 to go through. A couple of examples where I would be interested in
 knowing the answer are
 
 (A1) continuous spell-check by default.
 (A2) behavior of LFUN_DOWN_SELECT on last line.
 
 The survey could include other types of questions, but it would be
 nice to keep the survey as brief as possible. Another question that
 would be useful (e.g. for deciding what the minimum version of
 packages our layouts and templates should support) is:
 
 (B1) what TeX distribution do you use (please provide the year, e.g.
 TeX Live 2009) and how often do you update to the newest packages?
 
 Any thoughts?
 
 Scott

Re: annual survery of LyX users

[Jerry]

On Jun 19, 2013, at 11:36 AM, Scott Kostyshak <skost...@lyx.org> wrote:

> LyX users influence development by posting tickets on trac. A few
> brave users participate in discussions on lyx-devel. I think there is
> a clear way for LyX users who would like to get in touch with LyX
> developers. I think the other way is less obvious.
> 
> I often find myself thinking "I wonder what most users think about
> this". I could send an email to the lyx-users list, but most of the
> time I don't because i would only expect a couple to respond and that
> wouldn't really give me an idea of what most users think.
> 
> I propose the following: an annual survey of LyX users.

I think this is a great idea.

Having thought about it for all of five seconds now, would it make sense to 
solicit the users' list before each survey to get ideas for the survey, then 
follow up with some benevolent editing to create the actual survey?

Jerry

> What I am most
> interested in asking users is "do they prefer X or Y?". For example, I
> proposed a recent patch that really comes down to a preference. A
> couple of developers confirmed this, and I just planned on forgetting
> about it. But then I realized that just because a patch includes a
> personal preference doesn't necessarily mean it should be rejected.
> Developers could vote on it, but it would also be nice to get input
> from users.
> 
> This could be qualitative, such as "here are a list of enhancements
> that are being debated for inclusion in LyX 2.2. What are your
> thoughts?" or we could make it quantitative "if you have sent more
> than N emails to lyx-users or lyx-devel in the past year, you can
> vote". And perhaps 2/3 majority would be required for an enhancement
> to go through. A couple of examples where I would be interested in
> knowing the answer are
> 
> (A1) continuous spell-check by default.
> (A2) behavior of LFUN_DOWN_SELECT on last line.
> 
> The survey could include other types of questions, but it would be
> nice to keep the survey as brief as possible. Another question that
> would be useful (e.g. for deciding what the minimum version of
> packages our layouts and templates should support) is:
> 
> (B1) what TeX distribution do you use (please provide the year, e.g.
> TeX Live 2009) and how often do you update to the newest packages?
> 
> Any thoughts?
> 
> Scott

Re: LyX 2.1 beta 1: due in two weeks

[Jerry]

On May 21, 2013, at 1:32 AM, Vincent van Ravesteijn wrote:

 Dear all,
 
 It seems that the current master has survived the Lyx Developer's Meeting and 
 is still in good shape. Therefore, I intend to release the first beta of LyX 
 2.1 during the first weekend of June. In the meantime, the last topics can be 
 finished, the documentation can be updated, the translations can be updated, 
 and the release can be prepared.
 
 From now on, I would like to freeze the current master and to only allow:
 - important bugfixes, and
 - a few remaining topics that are 'in flight'
 (I will send a separate mail about which topics I know that are being 
 prepared for LyX2.1)
 
 Development of new features and/or fixes that can wait for LyX 2.1.x, or 
 2.2.0, can take place in the new features repository.
 
 Please have a look at http://wiki.lyx.org/LyX/NewInLyX21; and help to 
 complete the list of new features as much as possible. Maybe Uwe would also 
 appreciate some help to document the new features.

The recent work to correct slow scrolling is not included?
Jerry

 
 Depending on the feedback we get about this beta release, I will decide on 
 whether there will be more betas, or we will jump to the final LyX 2.1 
 release.
 
 Please let me know if you have any remarks.
 
 Vincent
 
 

Re: LyX 2.1 beta 1: due in two weeks

[Jerry]

On May 22, 2013, at 2:06 AM, Jean-Marc Lasgouttes wrote:

 22/05/2013 10:15, Vincent van Ravesteijn:
 Op 22-5-2013 9:29, Jerry schreef:
 
 The recent work to correct slow scrolling is not included?
 Jerry
 
 I'm not sure I know which work you mean. Besides, is this really a new
 feature or just a bugfix ?
 
 I guess this is the patch from pdv we discussed in Milano.
 
 Jerry, unfortunately this patch cannot go in in its present form and we did 
 not find the time to do the cleanup in Milano. Too much time was spent at the 
 meeting debating the virtues of C++11, cmake or Qt instead of coding :-|
 
 This is difficult stuff and has to be done carefully.
 
 JMarc

I appreciate that. Thanks for the update.
Jerry

Re: LyX 2.1 beta 1: due in two weeks

[Jerry]

On May 21, 2013, at 1:32 AM, Vincent van Ravesteijn wrote:

> Dear all,
> 
> It seems that the current master has survived the Lyx Developer's Meeting and 
> is still in good shape. Therefore, I intend to release the first beta of LyX 
> 2.1 during the first weekend of June. In the meantime, the last topics can be 
> finished, the documentation can be updated, the translations can be updated, 
> and the release can be prepared.
> 
> From now on, I would like to freeze the current master and to only allow:
> - important bugfixes, and
> - a few remaining topics that are 'in flight'
> (I will send a separate mail about which topics I know that are being 
> prepared for LyX2.1)
> 
> Development of new features and/or fixes that can wait for LyX 2.1.x, or 
> 2.2.0, can take place in the new features repository.
> 
> Please have a look at "http://wiki.lyx.org/LyX/NewInLyX21; and help to 
> complete the list of new features as much as possible. Maybe Uwe would also 
> appreciate some help to document the new features.

The recent work to correct slow scrolling is not included?
Jerry

> 
> Depending on the feedback we get about this beta release, I will decide on 
> whether there will be more betas, or we will jump to the final LyX 2.1 
> release.
> 
> Please let me know if you have any remarks.
> 
> Vincent
> 
> 

Re: LyX 2.1 beta 1: due in two weeks

[Jerry]

On May 22, 2013, at 2:06 AM, Jean-Marc Lasgouttes wrote:

> 22/05/2013 10:15, Vincent van Ravesteijn:
>> Op 22-5-2013 9:29, Jerry schreef:
>>> 
>>> The recent work to correct slow scrolling is not included?
>>> Jerry
>> 
>> I'm not sure I know which work you mean. Besides, is this really a new
>> feature or just a bugfix ?
> 
> I guess this is the patch from pdv we discussed in Milano.
> 
> Jerry, unfortunately this patch cannot go in in its present form and we did 
> not find the time to do the cleanup in Milano. Too much time was spent at the 
> meeting debating the virtues of C++11, cmake or Qt instead of coding :-|
> 
> This is difficult stuff and has to be done carefully.
> 
> JMarc

I appreciate that. Thanks for the update.
Jerry

Re: 2.0.6 on OS X: Window resizing from the edges is no longer possible

[Jerry]

On May 12, 2013, at 1:02 AM, Stephan Witt wrote:

 Am 11.05.2013 um 05:25 schrieb Jerry lancebo...@qwest.net:
 
 Hi,
 
 I just downloaded the OS X binary of LyX 2.0.6 and immediately saw a new 
 problem concerning the way windows work. 2.0.5 did not have this problem.
 
 In OS X beginning I believe with 10.7 it is possible to resize windows from 
 any edge, not just the lower left corner. (Windows users are stunned.) When 
 the cursor is moved over any edge (left, right, top, bottom) of the front 
 window, it turns into a tiny two-ended arrow, unless the edge is already at 
 the screen's boundary in which case it is a one-ended arrow. Clicking and 
 dragging then resizes the window from that edge.
 
 LyX 2.0.5, thanks probably to the underlying Qt stuff, handled this 
 correctly.
 
 LyX 2.0.6 does not--the little arrow cursor does not appear, and clicking 
 does not allow resizing in this manner--the click is handled as if window 
 resizing is not active. Resizing by the lower right corner however does 
 still work.
 
 I use a utility called Flexiglass which extends window-sizing, dragging, 
 etc. and it is hobbled now in 2.0.6. For example, dragging a window using a 
 Flexiglass feature which does not require using the normal drag region of a 
 window now allows the window to be dragged beyond the e.g. top of the 
 screen, where normally (and in 2.0.5) the drag was limited to the top of the 
 screen. I have disabled this utility and 2.0.6 still behaves as described 
 above.
 
 Possibly the Qt framework is defective or was configured wrong.
 
 Yes, it's the Qt framework. More precisely it is the Mac OS X API the Qt 
 framework is made for.
 
 With LyX 2.0.5.1 we got so many crash reports related to the Qt for Cocoa 
 framework I decided
 to switch back to the Carbon based Qt until LyX with Qt for Cocoa is stable 
 enough.
 
 Stephan

Thanks for that information, Stephan.

Jerry

Re: 2.0.6 on OS X: Window resizing from the edges is no longer possible

[Jerry]

On May 12, 2013, at 1:02 AM, Stephan Witt wrote:

> Am 11.05.2013 um 05:25 schrieb Jerry <lancebo...@qwest.net>:
> 
>> Hi,
>> 
>> I just downloaded the OS X binary of LyX 2.0.6 and immediately saw a new 
>> problem concerning the way windows work. 2.0.5 did not have this problem.
>> 
>> In OS X beginning I believe with 10.7 it is possible to resize windows from 
>> any edge, not just the lower left corner. (Windows users are stunned.) When 
>> the cursor is moved over any edge (left, right, top, bottom) of the front 
>> window, it turns into a tiny two-ended arrow, unless the edge is already at 
>> the screen's boundary in which case it is a one-ended arrow. Clicking and 
>> dragging then resizes the window from that edge.
>> 
>> LyX 2.0.5, thanks probably to the underlying Qt stuff, handled this 
>> correctly.
>> 
>> LyX 2.0.6 does not--the little arrow cursor does not appear, and clicking 
>> does not allow resizing in this manner--the click is handled as if window 
>> resizing is not active. Resizing by the lower right corner however does 
>> still work.
>> 
>> I use a utility called Flexiglass which extends window-sizing, dragging, 
>> etc. and it is hobbled now in 2.0.6. For example, dragging a window using a 
>> Flexiglass feature which does not require using the normal drag region of a 
>> window now allows the window to be dragged beyond the e.g. top of the 
>> screen, where normally (and in 2.0.5) the drag was limited to the top of the 
>> screen. I have disabled this utility and 2.0.6 still behaves as described 
>> above.
>> 
>> Possibly the Qt framework is defective or was configured wrong.
> 
> Yes, it's the Qt framework. More precisely it is the Mac OS X API the Qt 
> framework is made for.
> 
> With LyX 2.0.5.1 we got so many crash reports related to the Qt for Cocoa 
> framework I decided
> to switch back to the Carbon based Qt until LyX with Qt for Cocoa is stable 
> enough.
> 
> Stephan

Thanks for that information, Stephan.

Jerry

2.0.6 on OS X: Window resizing from the edges is no longer possible

[Jerry]

Hi,

I just downloaded the OS X binary of LyX 2.0.6 and immediately saw a new 
problem concerning the way windows work. 2.0.5 did not have this problem.

In OS X beginning I believe with 10.7 it is possible to resize windows from any 
edge, not just the lower left corner. (Windows users are stunned.) When the 
cursor is moved over any edge (left, right, top, bottom) of the front window, 
it turns into a tiny two-ended arrow, unless the edge is already at the 
screen's boundary in which case it is a one-ended arrow. Clicking and dragging 
then resizes the window from that edge.

LyX 2.0.5, thanks probably to the underlying Qt stuff, handled this correctly.

LyX 2.0.6 does not--the little arrow cursor does not appear, and clicking does 
not allow resizing in this manner--the click is handled as if window resizing 
is not active. Resizing by the lower right corner however does still work.

I use a utility called Flexiglass which extends window-sizing, dragging, etc. 
and it is hobbled now in 2.0.6. For example, dragging a window using a 
Flexiglass feature which does not require using the normal drag region of a 
window now allows the window to be dragged beyond the e.g. top of the screen, 
where normally (and in 2.0.5) the drag was limited to the top of the screen. I 
have disabled this utility and 2.0.6 still behaves as described above.

Possibly the Qt framework is defective or was configured wrong.

Jerry

2.0.6 on OS X: Window resizing from the edges is no longer possible

[Jerry]

Hi,

I just downloaded the OS X binary of LyX 2.0.6 and immediately saw a new 
problem concerning the way windows work. 2.0.5 did not have this problem.

In OS X beginning I believe with 10.7 it is possible to resize windows from any 
edge, not just the lower left corner. (Windows users are stunned.) When the 
cursor is moved over any edge (left, right, top, bottom) of the front window, 
it turns into a tiny two-ended arrow, unless the edge is already at the 
screen's boundary in which case it is a one-ended arrow. Clicking and dragging 
then resizes the window from that edge.

LyX 2.0.5, thanks probably to the underlying Qt stuff, handled this correctly.

LyX 2.0.6 does not--the little arrow cursor does not appear, and clicking does 
not allow resizing in this manner--the click is handled as if window resizing 
is not active. Resizing by the lower right corner however does still work.

I use a utility called Flexiglass which extends window-sizing, dragging, etc. 
and it is hobbled now in 2.0.6. For example, dragging a window using a 
Flexiglass feature which does not require using the normal drag region of a 
window now allows the window to be dragged beyond the e.g. top of the screen, 
where normally (and in 2.0.5) the drag was limited to the top of the screen. I 
have disabled this utility and 2.0.6 still behaves as described above.

Possibly the Qt framework is defective or was configured wrong.

Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 20, 2013, at 3:26 PM, Jerry wrote:

 
 On Jan 19, 2013, at 1:22 AM, Kornel Benko wrote:
 
 Am Freitag, 18. Januar 2013 um 16:37:11, schrieb Jerry lancebo...@qwest.net
 ^
 /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
  error: call to function 'tostr' that is neither visible in the template 
 definition nor found by argument-dependent
  lookup
string const s = tostr(t);
 ^
 
 I don't understand.
 
 1.) You are able to compile master tree
 
 That's correct.
 
 2.) The source src/insets/InsetTabular.cpp respective to tostr() is in 
 both cases
  the same, there should be the same error.
 
 Unfortunately, no. The master version and the 2.0.0 version of 
 InsetTabular.cpp, using my file comparison tool, shows 143 differences 
 between the two files. On the 2.0.0 version, 
 /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19
  points to the third s in the line
   string const s = tostr(t);
 The file sizes are different, with the master version at 166,776 bytes and 
 the 2.0.0 version at 160,383 bytes.
 
 
 Maybe different compile parameters?
 
 No, same compile parameters.
 
 Jerry

I fixed my build script and can now compile, but linking is bombing. Please see 
my next e-mail. BTW, these two versions of this file, InsetTabular.cpp, after 
my fix, are still different in 85 places
Jerry

 
 Apropos, the given line numbers are totally unrelated to the actual 2.0.x 
 version.
 Could you please try to compile this one first?
 
  Kornel
 
 

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 23, 2013, at 8:40 PM, Jerry wrote:

 
 On Jan 20, 2013, at 3:26 PM, Jerry wrote:
 
 
 On Jan 19, 2013, at 1:22 AM, Kornel Benko wrote:
 
 Am Freitag, 18. Januar 2013 um 16:37:11, schrieb Jerry 
 lancebo...@qwest.net
^
 /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
  error: call to function 'tostr' that is neither visible in the template 
 definition nor found by argument-dependent
 lookup
   string const s = tostr(t);
^
 
 I don't understand.
 
 1.) You are able to compile master tree
 
 That's correct.
 
 2.) The source src/insets/InsetTabular.cpp respective to tostr() is in 
 both cases
 the same, there should be the same error.
 
 Unfortunately, no. The master version and the 2.0.0 version of 
 InsetTabular.cpp, using my file comparison tool, shows 143 differences 
 between the two files. On the 2.0.0 version, 
 /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19
  points to the third s in the line
  string const s = tostr(t);
 The file sizes are different, with the master version at 166,776 bytes and 
 the 2.0.0 version at 160,383 bytes.
 
 
 Maybe different compile parameters?
 
 No, same compile parameters.
 
 Jerry
 
 I fixed my build script and can now compile, but linking is bombing. Please 
 see my next e-mail. BTW, these two versions of this file, InsetTabular.cpp, 
 after my fix, are still different in 85 places
 Jerry

Oops--please disregard the above comment. I had accidentally checked out 2.0.x 
instead of 2.0.0 and did not notice the error until now.

The status of my efforts remain the same. Compilation fails at 56% with four 
errors like this:

/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
 error: call to function 'tostr' that is neither visible in the template 
definition nor found by argument-dependent

Here is my script:



# Make a fresh copy of the git repository.
cp -iR /Applications/Words/LyX_outer_folder/lyx-git/lyx_ORIGINAL 
/Applications/Words/LyX_outer_folder/lyx-git/lyx

# Check out a version.
cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
git checkout 2.0.0

# Copy a messed-up file from master to the checked-out version. 
cp -i 
/Applications/Words/LyX_outer_folder/lyx-git/lyx_ORIGINAL/boost/boost/config/compiler/clang.hpp
 \
  
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/boost/config/compiler/clang.hpp

# Clean the build and installation directory.
sudo rm -rf /Applications/Words/LyX_outer_folder/Lyx-dev-app/*
sudo rm -rf /Applications/Words/LyX_outer_folder/Lyx-dev-build/*

# Go to the build directory.
cd /Applications/Words/LyX_outer_folder/lyx-dev-build/

# Run cmake.
cmake \
-DLYX_EXTERNAL_LIBINTL=ON \
-DLIBINTL_INCLUDE_DIR=/opt/local/include \
-DLYX_PROGRAM_SUFFIX=OFF \
-DLYX_PACKAGE_SUFFIX=OFF \
-DLYX_RELEASE=ON \
-DLYX_INSTALL=ON \
-DLYX_COCOA=ON \
-DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/lyx-dev-app/ \
/Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake/

# If building master, the last cmake line should be:
#   /Applications/Words/LyX_outer_folder/lyx-git/lyx/

make
sudo make install



I'm stuck in my efforts at this point with not a clue how to proceed. I can't 
build 2.0.0.

Jerry

 
 
 Apropos, the given line numbers are totally unrelated to the actual 2.0.x 
 version.
 Could you please try to compile this one first?
 
 Kornel
 
 
 

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 20, 2013, at 3:26 PM, Jerry wrote:

> 
> On Jan 19, 2013, at 1:22 AM, Kornel Benko wrote:
> 
>> Am Freitag, 18. Januar 2013 um 16:37:11, schrieb Jerry <lancebo...@qwest.net>
>>> ^
>>> /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
>>>  error: call to function 'tostr' that is neither visible in the template 
>>> definition nor found by argument-dependent
>>>  lookup
>>>string const s = tostr(t);
>>> ^
>> 
>> I don't understand.
>> 
>> 1.) You are able to compile master tree
> 
> That's correct.
> 
>> 2.) The source "src/insets/InsetTabular.cpp" respective to tostr() is in 
>> both cases
>>  the same, there should be the same error.
> 
> Unfortunately, no. The master version and the 2.0.0 version of 
> InsetTabular.cpp, using my file comparison tool, shows 143 differences 
> between the two files. On the 2.0.0 version, 
> /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19
>  points to the third "s" in the line
>   string const s = tostr(t);
> The file sizes are different, with the master version at 166,776 bytes and 
> the 2.0.0 version at 160,383 bytes.
> 
>> 
>> Maybe different compile parameters?
> 
> No, same compile parameters.
> 
> Jerry

I fixed my build script and can now compile, but linking is bombing. Please see 
my next e-mail. BTW, these two versions of this file, InsetTabular.cpp, after 
my fix, are still different in 85 places
Jerry

>> 
>> Apropos, the given line numbers are totally unrelated to the actual 2.0.x 
>> version.
>> Could you please try to compile this one first?
>> 
>>  Kornel
> 
> 

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 23, 2013, at 8:40 PM, Jerry wrote:

> 
> On Jan 20, 2013, at 3:26 PM, Jerry wrote:
> 
>> 
>> On Jan 19, 2013, at 1:22 AM, Kornel Benko wrote:
>> 
>>> Am Freitag, 18. Januar 2013 um 16:37:11, schrieb Jerry 
>>> <lancebo...@qwest.net>
>>>>^
>>>> /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
>>>>  error: call to function 'tostr' that is neither visible in the template 
>>>> definition nor found by argument-dependent
>>>> lookup
>>>>   string const s = tostr(t);
>>>>^
>>> 
>>> I don't understand.
>>> 
>>> 1.) You are able to compile master tree
>> 
>> That's correct.
>> 
>>> 2.) The source "src/insets/InsetTabular.cpp" respective to tostr() is in 
>>> both cases
>>> the same, there should be the same error.
>> 
>> Unfortunately, no. The master version and the 2.0.0 version of 
>> InsetTabular.cpp, using my file comparison tool, shows 143 differences 
>> between the two files. On the 2.0.0 version, 
>> /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19
>>  points to the third "s" in the line
>>  string const s = tostr(t);
>> The file sizes are different, with the master version at 166,776 bytes and 
>> the 2.0.0 version at 160,383 bytes.
>> 
>>> 
>>> Maybe different compile parameters?
>> 
>> No, same compile parameters.
>> 
>> Jerry
> 
> I fixed my build script and can now compile, but linking is bombing. Please 
> see my next e-mail. BTW, these two versions of this file, InsetTabular.cpp, 
> after my fix, are still different in 85 places
> Jerry

Oops--please disregard the above comment. I had accidentally checked out 2.0.x 
instead of 2.0.0 and did not notice the error until now.

The status of my efforts remain the same. Compilation fails at 56% with four 
errors like this:

/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
 error: call to function 'tostr' that is neither visible in the template 
definition nor found by argument-dependent

Here is my script:



# Make a fresh copy of the git repository.
cp -iR /Applications/Words/LyX_outer_folder/lyx-git/lyx_ORIGINAL 
/Applications/Words/LyX_outer_folder/lyx-git/lyx

# Check out a version.
cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
git checkout 2.0.0

# Copy a messed-up file from master to the checked-out version. 
cp -i 
/Applications/Words/LyX_outer_folder/lyx-git/lyx_ORIGINAL/boost/boost/config/compiler/clang.hpp
 \
  
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/boost/config/compiler/clang.hpp

# Clean the build and installation directory.
sudo rm -rf /Applications/Words/LyX_outer_folder/Lyx-dev-app/*
sudo rm -rf /Applications/Words/LyX_outer_folder/Lyx-dev-build/*

# Go to the build directory.
cd /Applications/Words/LyX_outer_folder/lyx-dev-build/

# Run cmake.
cmake \
-DLYX_EXTERNAL_LIBINTL=ON \
-DLIBINTL_INCLUDE_DIR=/opt/local/include \
-DLYX_PROGRAM_SUFFIX=OFF \
-DLYX_PACKAGE_SUFFIX=OFF \
-DLYX_RELEASE=ON \
-DLYX_INSTALL=ON \
-DLYX_COCOA=ON \
-DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/lyx-dev-app/ \
/Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake/

# If building master, the last cmake line should be:
#   /Applications/Words/LyX_outer_folder/lyx-git/lyx/

make
sudo make install



I'm stuck in my efforts at this point with not a clue how to proceed. I can't 
build 2.0.0.

Jerry

> 
>>> 
>>> Apropos, the given line numbers are totally unrelated to the actual 2.0.x 
>>> version.
>>> Could you please try to compile this one first?
>>> 
>>> Kornel
>> 
>> 
> 

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 19, 2013, at 1:22 AM, Kornel Benko wrote:

 Am Freitag, 18. Januar 2013 um 16:37:11, schrieb Jerry lancebo...@qwest.net
   ^
  /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
   error: call to function 'tostr' that is neither visible in the template 
  definition nor found by argument-dependent
lookup
  string const s = tostr(t);
   ^
  
 I don't understand.
  
 1.) You are able to compile master tree

That's correct.

 2.) The source src/insets/InsetTabular.cpp respective to tostr() is in both 
 cases
   the same, there should be the same error.

Unfortunately, no. The master version and the 2.0.0 version of 
InsetTabular.cpp, using my file comparison tool, shows 143 differences between 
the two files. On the 2.0.0 version, 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19
 points to the third s in the line
string const s = tostr(t);
The file sizes are different, with the master version at 166,776 bytes and the 
2.0.0 version at 160,383 bytes.

  
 Maybe different compile parameters?

No, same compile parameters.

Jerry
  
 Apropos, the given line numbers are totally unrelated to the actual 2.0.x 
 version.
 Could you please try to compile this one first?
  
   Kornel

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 19, 2013, at 1:22 AM, Kornel Benko wrote:

> Am Freitag, 18. Januar 2013 um 16:37:11, schrieb Jerry <lancebo...@qwest.net>
> >  ^
> > /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
> >  error: call to function 'tostr' that is neither visible in the template 
> > definition nor found by argument-dependent
> >   lookup
> > string const s = tostr(t);
> >  ^
>  
> I don't understand.
>  
> 1.) You are able to compile master tree

That's correct.

> 2.) The source "src/insets/InsetTabular.cpp" respective to tostr() is in both 
> cases
>   the same, there should be the same error.

Unfortunately, no. The master version and the 2.0.0 version of 
InsetTabular.cpp, using my file comparison tool, shows 143 differences between 
the two files. On the 2.0.0 version, 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19
 points to the third "s" in the line
string const s = tostr(t);
The file sizes are different, with the master version at 166,776 bytes and the 
2.0.0 version at 160,383 bytes.

>  
> Maybe different compile parameters?

No, same compile parameters.

Jerry
>  
> Apropos, the given line numbers are totally unrelated to the actual 2.0.x 
> version.
> Could you please try to compile this one first?
>  
>   Kornel

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 18, 2013, at 12:20 AM, Kornel Benko wrote:

 Am Donnerstag, 17. Januar 2013 um 21:21:10, schrieb Jerry 
 lancebo...@qwest.net
  Thanks for the enlightenment. Same results, of course.
  
  
 Which results do you mean? The compilation error because of missing clang.hpp?

Yes.

 If yes, try to copy ./boost/boost/config/compiler/clang.hpp form the master 
 tree to
 2.0.x tree.
 Please report.

That fixed the problem but now there is this:

[ 56%] Building CXX object 
src/insets/CMakeFiles/insets.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp.o
cd /Applications/Words/LyX_outer_folder/lyx-dev-build/src/insets  
/usr/bin/c++   -DHAVE_GETTEXT -Wall -Wunused-parameter -fno-strict-aliasing  
-Wall -Wunused-parameter -O3 -DNDEBUG 
-I/Applications/Words/LyX_outer_folder/lyx-dev-build 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/src 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/po 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets 
-I/opt/local/include -I/opt/local/include/Qt 
-I/opt/local/share/qt4/mkspecs/default -I/opt/local/include/QtCore 
-I/opt/local/include/QtGui -I/opt/local/include/Qt3Support 
-I/opt/local/include/QtDesigner -I/opt/local/include/QtNetwork 
-I/opt/local/include/QtOpenGL -I/opt/local/include/QtSql 
-I/opt/local/include/QtXml -I/opt/local/include/QtSvg 
-I/opt/local/include/QtUiTools -I/opt/local/include/QtTest
-DBOOST_USER_CONFIG=config.h -o 
CMakeFiles/insets.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp.o
 -c /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:22:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.h:58:10:
 warning: 'lyx::InsetTableCell::clone' hides overloaded virtual function 
[-Woverloaded-virtual]
Inset * clone() { return new InsetTableCell(*this); }
^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetText.h:175:10: 
note: hidden overloaded virtual function 'lyx::InsetText::clone' declared here
Inset * clone() const { return new InsetText(*this); }
^
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:31:
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/CutAndPaste.h:19:
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/frontends/Clipboard.h:19:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/support/FileName.h:260:15: 
warning: 'lyx::support::DocFileName::set' hides overloaded virtual functions 
[-Woverloaded-virtual]
virtual void set(std::string const  filename, std::string const  
buffer_path);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/support/FileName.h:58:15: 
note: hidden overloaded virtual function 'lyx::support::FileName::set' declared 
here
virtual void set(std::string const  filename);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/support/FileName.h:59:15: 
note: hidden overloaded virtual function 'lyx::support::FileName::set' declared 
here
virtual void set(FileName const  fn, std::string const  suffix);
 ^
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:46:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/TextClass.h:364:15: 
warning: 'lyx::DocumentClass::loaded' hides overloaded virtual function 
[-Woverloaded-virtual]
virtual bool loaded() { return false; }
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/TextClass.h:180:15: note: 
hidden overloaded virtual function 'lyx::TextClass::loaded' declared here
virtual bool loaded() const { return loaded_; }
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
 error: call to function 'tostr' that is neither visible in the template 
definition nor found by argument-dependent
  lookup
string const s = tostr(t);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:1398:11:
 note: in instantiation of function template specialization 'lyx::anonymous
  namespace::write_attributelyx::Tabular::VAlignment' requested here
   os  write_attribute(tabularvalignment, tabular_valignment);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:285:14:
 note: 'tostr' should be declared prior to the call site or in namespace 'lyx'
string const tostr(Tabular::VAlignment const  num)
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
 error: call to function 'tostr' that is neither visible in the template 
definition nor found by argument

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 18, 2013, at 12:20 AM, Kornel Benko wrote:

> Am Donnerstag, 17. Januar 2013 um 21:21:10, schrieb Jerry 
> <lancebo...@qwest.net>
> > Thanks for the enlightenment. Same results, of course.
> > 
>  
> Which results do you mean? The compilation error because of missing clang.hpp?

Yes.

> If yes, try to copy "./boost/boost/config/compiler/clang.hpp" form the master 
> tree to
> 2.0.x tree.
> Please report.

That fixed the problem but now there is this:

[ 56%] Building CXX object 
src/insets/CMakeFiles/insets.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp.o
cd /Applications/Words/LyX_outer_folder/lyx-dev-build/src/insets && 
/usr/bin/c++   -DHAVE_GETTEXT -Wall -Wunused-parameter -fno-strict-aliasing  
-Wall -Wunused-parameter -O3 -DNDEBUG 
-I/Applications/Words/LyX_outer_folder/lyx-dev-build 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/src 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/po 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets 
-I/opt/local/include -I/opt/local/include/Qt 
-I/opt/local/share/qt4/mkspecs/default -I/opt/local/include/QtCore 
-I/opt/local/include/QtGui -I/opt/local/include/Qt3Support 
-I/opt/local/include/QtDesigner -I/opt/local/include/QtNetwork 
-I/opt/local/include/QtOpenGL -I/opt/local/include/QtSql 
-I/opt/local/include/QtXml -I/opt/local/include/QtSvg 
-I/opt/local/include/QtUiTools -I/opt/local/include/QtTest
-DBOOST_USER_CONFIG="" -o 
CMakeFiles/insets.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp.o
 -c /Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:22:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.h:58:10:
 warning: 'lyx::InsetTableCell::clone' hides overloaded virtual function 
[-Woverloaded-virtual]
Inset * clone() { return new InsetTableCell(*this); }
^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetText.h:175:10: 
note: hidden overloaded virtual function 'lyx::InsetText::clone' declared here
Inset * clone() const { return new InsetText(*this); }
^
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:31:
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/CutAndPaste.h:19:
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/frontends/Clipboard.h:19:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/support/FileName.h:260:15: 
warning: 'lyx::support::DocFileName::set' hides overloaded virtual functions 
[-Woverloaded-virtual]
virtual void set(std::string const & filename, std::string const & 
buffer_path);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/support/FileName.h:58:15: 
note: hidden overloaded virtual function 'lyx::support::FileName::set' declared 
here
virtual void set(std::string const & filename);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/support/FileName.h:59:15: 
note: hidden overloaded virtual function 'lyx::support::FileName::set' declared 
here
virtual void set(FileName const & fn, std::string const & suffix);
 ^
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:46:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/TextClass.h:364:15: 
warning: 'lyx::DocumentClass::loaded' hides overloaded virtual function 
[-Woverloaded-virtual]
virtual bool loaded() { return false; }
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/TextClass.h:180:15: note: 
hidden overloaded virtual function 'lyx::TextClass::loaded' declared here
virtual bool loaded() const { return loaded_; }
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
 error: call to function 'tostr' that is neither visible in the template 
definition nor found by argument-dependent
  lookup
string const s = tostr(t);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:1398:11:
 note: in instantiation of function template specialization 'lyxwrite_attribute' requested here
   os << write_attribute("tabularvalignment", tabular_valignment);
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:285:14:
 note: 'tostr' should be declared prior to the call site or in namespace 'lyx'
string const tostr(Tabular::VAlignment const & num)
 ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/src/insets/InsetTabular.cpp:194:19:
 error: call to fun

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 16, 2013, at 1:30 AM, Kornel Benko wrote:

 Am Dienstag, 15. Januar 2013 um 18:02:30, schrieb Jerry lancebo...@qwest.net
  
  On Jan 15, 2013, at 1:12 AM, Kornel Benko wrote:
  
   Am Montag, 14. Januar 2013 um 19:51:08, schrieb Jerry 
   lancebo...@qwest.net
   ...
Well, I seem to have lost the ability to build anything but master. 
I've tried a few things to build 2.0.0 such as building inside 
/bla/bla/development/cmake so that CMakeLists.txt is seen, and making a 
symlink of /bla/bla/development/cmake/CMakeLists.txt to /bla/bla/. 

The first attempt (build in /bla/bla/development/cmake) fails like this:

CMake Error: The source directory /bla/bla does not appear to contain 
CMakeLists.txt.
  (where /bla/bla is the source root directory.)

   iff you have branched to 2.0.x
 (
 #cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
 # git checkout 2.0.x
 )

   then
 #cd your 2.0.x build directory
 #cmake 
   /Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake ...

 Kornel
   
  Thanks, Kornel. I followed your instructions above as literally as I could. 
  To be specific, here's what I did. I first made a fresh copy of the 
  repository, the fresh copy having path
  
  /Applications/Words/LyX_outer_folder/lyx-git/lyx/
  
  Then
  
  $ cd /Applications/Words/LyX_outer_folder/lyx-git/lyx 
  $ git checkout 2.0.0
  
  My build directory is set by this cmake line (see below):
  
  -DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \
  
  
 Maybe line too short?
  
  so I 
 
  $ cd /Applications/Words/LyX_outer_folder/Lyx-dev-app/
  
 Why? This is NOT the build directory. Thist is the prefix-path to be used for 
 installation.
 The build directory is _anything_you_choose_, to be used for temporary data 
 created while build.
 The correct sequence:
   #cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
   #git checkout 2.0.0
   #mkdir /tmp/lyx20   
 # or whatever you like
   #cd /tmp/lyx20
   #cmake 
 /Applications/Words/LyX_outer_folder/lyx-git/lyx/Development/cmake 
 -DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ ...
   #make   
 # or whatever is your 
 build-command
   # sudo make install 
 # or appropriate command
 Only now the /Applications/Words/LyX_outer_folder/Lyx-dev-app should be 
 populated ...
  
  which happens to already exist and which is empty, then I run this cmake 
  command:
  
 cd in the build directory first
  
  cmake \
  -DLYX_EXTERNAL_LIBINTL=ON \
  -DLIBINTL_INCLUDE_DIR=/opt/local/include \
  -DLYX_PROGRAM_SUFFIX=OFF \
  -DLYX_PACKAGE_SUFFIX=OFF \
  -DLYX_RELEASE=ON \
  -DLYX_DMG=ON \
  -DLYX_INSTALL=ON \
  -DLYX_COCOA=ON \
  -DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \
  /Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake/
  
  which results in four cmake warnings and this:
  
  -- Build files have been written to: 
  /Applications/Words/LyX_outer_folder/Lyx-dev-app
  
  then (with path still set to 
  /Applications/Words/LyX_outer_folder/Lyx-dev-app)
  
  
   Kornel

Thanks for the enlightenment. Same results, of course.

So I guess you've already figured out that the reason I was seeing source tree 
pollution was because I was building in the source tree. :-/

Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 16, 2013, at 3:02 AM, Kornel Benko wrote:

 Am Mittwoch, 16. Januar 2013 um 10:20:44, schrieb Jean-Marc Lasgouttes 
 lasgout...@lyx.org
  Le 16/01/2013 09:37, Kornel Benko a écrit :
   Here, /usr/include/boost/config/compiler/clang.hpp is part of package
   libboost1.46-dev. I think, we should
  
   provide it too?
  
  I think so.
  
  JMarc
  
 In 2.0.x the last boost version to which we updated is 1.44 or 1.43?
  
 The last commit messages refers to
   1.41.0, 1.42.0, 1.44, 1.43 (Notice the order)
  
 In master branch we are on 1.49.0 ...
 Here we provide already clang.hpp.
 It differs from my installed file, but only in some guards for macro 
 definitions.
 It should work if we simply copy clang.hpp from master to 2.0.x branch.
  
   Kornel

This discussion is outside my skill set. Are we stuck or can this be fixed?
Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 16, 2013, at 1:30 AM, Kornel Benko wrote:

> Am Dienstag, 15. Januar 2013 um 18:02:30, schrieb Jerry <lancebo...@qwest.net>
> > 
> > On Jan 15, 2013, at 1:12 AM, Kornel Benko wrote:
> > 
> > > Am Montag, 14. Januar 2013 um 19:51:08, schrieb Jerry 
> > > <lancebo...@qwest.net>
> > > ...
> > > > Well, I seem to have lost the ability to build anything but master. 
> > > > I've tried a few things to build 2.0.0 such as building inside 
> > > > /bla/bla/development/cmake so that CMakeLists.txt is seen, and making a 
> > > > symlink of /bla/bla/development/cmake/CMakeLists.txt to /bla/bla/. 
> > > > 
> > > > The first attempt (build in /bla/bla/development/cmake) fails like this:
> > > > 
> > > > CMake Error: The source directory "/bla/bla" does not appear to contain 
> > > > CMakeLists.txt.
> > > >   (where /bla/bla is the source root directory.)
> > >  
> > > iff you have branched to 2.0.x
> > >   (
> > >   #cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
> > >   # git checkout 2.0.x
> > >   )
> > >  
> > > then
> > >   #cd 
> > >   #cmake 
> > > /Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake ...
> > >  
> > >   Kornel
> > > 
> > Thanks, Kornel. I followed your instructions above as literally as I could. 
> > To be specific, here's what I did. I first made a fresh copy of the 
> > repository, the fresh copy having path
> > 
> > /Applications/Words/LyX_outer_folder/lyx-git/lyx/
> > 
> > Then
> > 
> > $ cd /Applications/Words/LyX_outer_folder/lyx-git/lyx 
> > $ git checkout 2.0.0
> > 
> > My build directory is set by this cmake line (see below):
> > 
> > -DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \
>  
>  
> Maybe line too short?
>  
> > so I 
> >
> > $ cd /Applications/Words/LyX_outer_folder/Lyx-dev-app/
>  
> Why? This is NOT the build directory. Thist is the prefix-path to be used for 
> installation.
> The build directory is _anything_you_choose_, to be used for temporary data 
> created while build.
> The correct sequence:
>   #cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
>   #git checkout 2.0.0
>   #mkdir /tmp/lyx20   
> # or whatever you like
>   #cd /tmp/lyx20
>   #cmake 
> /Applications/Words/LyX_outer_folder/lyx-git/lyx/Development/cmake 
> -DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ ...
>   #make   
> # or whatever is your 
> build-command
>   # sudo make install 
> # or appropriate command
> Only now the /Applications/Words/LyX_outer_folder/Lyx-dev-app should be 
> populated ...
>  
> > which happens to already exist and which is empty, then I run this cmake 
> > command:
>  
> cd in the build directory first
>  
> > cmake \
> > -DLYX_EXTERNAL_LIBINTL=ON \
> > -DLIBINTL_INCLUDE_DIR=/opt/local/include \
> > -DLYX_PROGRAM_SUFFIX=OFF \
> > -DLYX_PACKAGE_SUFFIX=OFF \
> > -DLYX_RELEASE=ON \
> > -DLYX_DMG=ON \
> > -DLYX_INSTALL=ON \
> > -DLYX_COCOA=ON \
> > -DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \
> > /Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake/
> > 
> > which results in four cmake warnings and this:
> > 
> > -- Build files have been written to: 
> > /Applications/Words/LyX_outer_folder/Lyx-dev-app
> > 
> > then (with path still set to 
> > /Applications/Words/LyX_outer_folder/Lyx-dev-app)
> > 
>  
>   Kornel

Thanks for the enlightenment. Same results, of course.

So I guess you've already figured out that the reason I was seeing source tree 
pollution was because I was building in the source tree. :-/

Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 16, 2013, at 3:02 AM, Kornel Benko wrote:

> Am Mittwoch, 16. Januar 2013 um 10:20:44, schrieb Jean-Marc Lasgouttes 
> <lasgout...@lyx.org>
> > Le 16/01/2013 09:37, Kornel Benko a écrit :
> > > Here, /usr/include/boost/config/compiler/clang.hpp is part of package
> > > libboost1.46-dev. I think, we should
> > >
> > > provide it too?
> > 
> > I think so.
> > 
> > JMarc
>  
> In 2.0.x the last boost version to which we updated is 1.44 or 1.43?
>  
> The last commit messages refers to
>   1.41.0, 1.42.0, 1.44, 1.43 (Notice the order)
>  
> In master branch we are on 1.49.0 ...
> Here we provide already clang.hpp.
> It differs from my installed file, but only in some guards for macro 
> definitions.
> It should work if we simply copy clang.hpp from master to 2.0.x branch.
>  
>   Kornel

This discussion is outside my skill set. Are we stuck or can this be fixed?
Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 15, 2013, at 1:12 AM, Kornel Benko wrote:

 Am Montag, 14. Januar 2013 um 19:51:08, schrieb Jerry lancebo...@qwest.net
 ...
  Well, I seem to have lost the ability to build anything but master. I've 
  tried a few things to build 2.0.0 such as building inside 
  /bla/bla/development/cmake so that CMakeLists.txt is seen, and making a 
  symlink of /bla/bla/development/cmake/CMakeLists.txt to /bla/bla/. 
  
  The first attempt (build in /bla/bla/development/cmake) fails like this:
  
  CMake Error: The source directory /bla/bla does not appear to contain 
  CMakeLists.txt.
(where /bla/bla is the source root directory.)
  
 iff you have branched to 2.0.x
   (
   #cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
   # git checkout 2.0.x
   )
  
 then
   #cd your 2.0.x build directory
   #cmake 
 /Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake ...
  
   Kornel
 
Thanks, Kornel. I followed your instructions above as literally as I could. To 
be specific, here's what I did. I first made a fresh copy of the repository, 
the fresh copy having path

/Applications/Words/LyX_outer_folder/lyx-git/lyx/

Then

$ cd /Applications/Words/LyX_outer_folder/lyx-git/lyx 
$ git checkout 2.0.0

My build directory is set by this cmake line (see below):

-DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \

so I 

$ cd /Applications/Words/LyX_outer_folder/Lyx-dev-app/

which happens to already exist and which is empty, then I run this cmake 
command:

cmake \
-DLYX_EXTERNAL_LIBINTL=ON \
-DLIBINTL_INCLUDE_DIR=/opt/local/include \
-DLYX_PROGRAM_SUFFIX=OFF \
-DLYX_PACKAGE_SUFFIX=OFF \
-DLYX_RELEASE=ON \
-DLYX_DMG=ON \
-DLYX_INSTALL=ON \
-DLYX_COCOA=ON \
-DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \
/Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake/

which results in four cmake warnings and this:

-- Build files have been written to: 
/Applications/Words/LyX_outer_folder/Lyx-dev-app

then (with path still set to /Applications/Words/LyX_outer_folder/Lyx-dev-app)

make

which results in 

[ 10%] Building CXX object 
boost/libs/regex/CMakeFiles/boost_regex.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp.o
cd /Applications/Words/LyX_outer_folder/Lyx-dev-app/boost/libs/regex  
/usr/bin/c++   -DHAVE_GETTEXT -Wall -Wunused-parameter -fno-strict-aliasing  
-Wall -Wunused-parameter -O3 -DNDEBUG 
-I/Applications/Words/LyX_outer_folder/Lyx-dev-app 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/src 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/po 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost
-DBOOST_USER_CONFIG=config.h -o 
CMakeFiles/boost_regex.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp.o
 -c 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp:20:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/boost/config.hpp:35:12: 
fatal error: 
  'boost/config/compiler/clang.hpp' file not found
#  include BOOST_COMPILER_CONFIG
   ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/boost/config/select_compiler_config.hpp:55:34:
 note: 
  expanded from macro 'BOOST_COMPILER_CONFIG'
#   define BOOST_COMPILER_CONFIG boost/config/compiler/clang.hpp
 ^
1 error generated.
make[2]: *** 
[boost/libs/regex/CMakeFiles/boost_regex.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp.o]
 Error 1
make[1]: *** [boost/libs/regex/CMakeFiles/boost_regex.dir/all] Error 2
make: *** [all] Error 2


Jerry

P.S. Why do some people put the path to source as the first argument to cmake 
when the manpage for cmake says it should go last? It seems to work either way, 
right?

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 15, 2013, at 1:12 AM, Kornel Benko wrote:

> Am Montag, 14. Januar 2013 um 19:51:08, schrieb Jerry <lancebo...@qwest.net>
> ...
> > Well, I seem to have lost the ability to build anything but master. I've 
> > tried a few things to build 2.0.0 such as building inside 
> > /bla/bla/development/cmake so that CMakeLists.txt is seen, and making a 
> > symlink of /bla/bla/development/cmake/CMakeLists.txt to /bla/bla/. 
> > 
> > The first attempt (build in /bla/bla/development/cmake) fails like this:
> > 
> > CMake Error: The source directory "/bla/bla" does not appear to contain 
> > CMakeLists.txt.
> >   (where /bla/bla is the source root directory.)
>  
> iff you have branched to 2.0.x
>   (
>   #cd /Applications/Words/LyX_outer_folder/lyx-git/lyx
>   # git checkout 2.0.x
>   )
>  
> then
>   #cd 
>   #cmake 
> /Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake ...
>  
>   Kornel
> 
Thanks, Kornel. I followed your instructions above as literally as I could. To 
be specific, here's what I did. I first made a fresh copy of the repository, 
the fresh copy having path

/Applications/Words/LyX_outer_folder/lyx-git/lyx/

Then

$ cd /Applications/Words/LyX_outer_folder/lyx-git/lyx 
$ git checkout 2.0.0

My build directory is set by this cmake line (see below):

-DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \

so I 

$ cd /Applications/Words/LyX_outer_folder/Lyx-dev-app/

which happens to already exist and which is empty, then I run this cmake 
command:

cmake \
-DLYX_EXTERNAL_LIBINTL=ON \
-DLIBINTL_INCLUDE_DIR=/opt/local/include \
-DLYX_PROGRAM_SUFFIX=OFF \
-DLYX_PACKAGE_SUFFIX=OFF \
-DLYX_RELEASE=ON \
-DLYX_DMG=ON \
-DLYX_INSTALL=ON \
-DLYX_COCOA=ON \
-DLYX_INSTALL_PREFIX=/Applications/Words/LyX_outer_folder/Lyx-dev-app/ \
/Applications/Words/LyX_outer_folder/lyx-git/lyx/development/cmake/

which results in four cmake warnings and this:

-- Build files have been written to: 
/Applications/Words/LyX_outer_folder/Lyx-dev-app

then (with path still set to /Applications/Words/LyX_outer_folder/Lyx-dev-app)

make

which results in 

[ 10%] Building CXX object 
boost/libs/regex/CMakeFiles/boost_regex.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp.o
cd /Applications/Words/LyX_outer_folder/Lyx-dev-app/boost/libs/regex && 
/usr/bin/c++   -DHAVE_GETTEXT -Wall -Wunused-parameter -fno-strict-aliasing  
-Wall -Wunused-parameter -O3 -DNDEBUG 
-I/Applications/Words/LyX_outer_folder/Lyx-dev-app 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/src 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/po 
-I/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost
-DBOOST_USER_CONFIG="" -o 
CMakeFiles/boost_regex.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp.o
 -c 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp
In file included from 
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp:20:
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/boost/config.hpp:35:12: 
fatal error: 
  'boost/config/compiler/clang.hpp' file not found
#  include BOOST_COMPILER_CONFIG
   ^
/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/boost/config/select_compiler_config.hpp:55:34:
 note: 
  expanded from macro 'BOOST_COMPILER_CONFIG'
#   define BOOST_COMPILER_CONFIG "boost/config/compiler/clang.hpp"
 ^
1 error generated.
make[2]: *** 
[boost/libs/regex/CMakeFiles/boost_regex.dir/Applications/Words/LyX_outer_folder/lyx-git/lyx/boost/libs/regex/src/cpp_regex_traits.cpp.o]
 Error 1
make[1]: *** [boost/libs/regex/CMakeFiles/boost_regex.dir/all] Error 2
make: *** [all] Error 2


Jerry

P.S. Why do some people put the path to source as the first argument to cmake 
when the manpage for cmake says it should go last? It seems to work either way, 
right?

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 14, 2013, at 8:45 AM, Nico Williams wrote:

 On Sun, Jan 13, 2013 at 7:18 AM, Kornel Benko kor...@lyx.org wrote:
 Also, does this cmake command pollute my source tree? How can I define a
 build tree?
 
 I tried to pollute as little as possible, but in general, you are not
 encouraged to call
 
 cmake from the source tree.
 
 You can always git clean.
 
 You should write a script to pass to git bisect that builds LyX and
 runs it so you can check the scrolling behavior.

If you are implying complete automation, I have no idea how to make a script 
that scrolls through the User's Guide (my objective test) and measures how long 
it takes.

git clean -x looks like my friend--thanks for that, Nico.

Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 13, 2013, at 8:25 PM, Jerry wrote:

 
 On Jan 13, 2013, at 6:49 AM, Stephan Witt wrote:
 
 Am 13.01.2013 um 14:18 schrieb Kornel Benko kor...@lyx.org:
 
 Am Samstag, 12. Januar 2013 um 19:24:32, schrieb Jerry 
 lancebo...@qwest.net
 Back on the bisection trail
 
 I'm having more trouble building from source for this bisection.
 
 That explains what I've been seeing. (BTW, I can now build master using 
 cmake--the QT_QT_INCLUDE_DIR problem is fixed.) When I try to build branch 
 2.0.0 after cd-ing to the build directory, I get this:
 
 CMake Error: The source directory 
 /Applications/Words/LyX_outer_folder/lyx-git/lyx ( that's my git 
 repository) does not appear to contain CMakeLists.txt.
 
 So I was cd-ing to the /bla/development/cmake directory so that I could see 
 CMakeLists.txt and I think that's what was causing the tree pollution. I just 
 now tried building again from 2.0.0 and got the same result. I see that you 
 (Stephan) and Kornel are woking on this
 
 Jerry 

Well, I seem to have lost the ability to build anything but master. I've tried 
a few things to build 2.0.0 such as building inside /bla/bla/development/cmake 
so that CMakeLists.txt is seen, and making a symlink of 
/bla/bla/development/cmake/CMakeLists.txt to /bla/bla/. 

The first attempt (build in /bla/bla/development/cmake) fails like this:

CMake Error: The source directory /bla/bla does not appear to contain 
CMakeLists.txt.
  (where /bla/bla is the source root directory.)

The second attempt (symlink) fails thusly:

CMake Error at CMakeLists.txt:27 (include):
  include could not find load file:

LyXMacros

CMake Error at CMakeLists.txt:37 (LYX_OPTION_INIT):
  Unknown CMake command LYX_OPTION_INIT.


Jerry

 
 Jerry is on a Mac and want's to make a time travel from 1.6.10 over 2.0.x to 
 2.1.x.
 
 So, he has a problem to do so, probably.
 
 Stephan
 

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 14, 2013, at 8:45 AM, Nico Williams wrote:

> On Sun, Jan 13, 2013 at 7:18 AM, Kornel Benko <kor...@lyx.org> wrote:
>>> Also, does this cmake command pollute my source tree? How can I define a
>>> build tree?
>> 
>> I tried to pollute as little as possible, but in general, you are not
>> encouraged to call
>> 
>> cmake from the source tree.
> 
> You can always git clean.
> 
> You should write a script to pass to git bisect that builds LyX and
> runs it so you can check the scrolling behavior.

If you are implying complete automation, I have no idea how to make a script 
that scrolls through the User's Guide (my objective test) and measures how long 
it takes.

git clean -x looks like my friend--thanks for that, Nico.

Jerry

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 13, 2013, at 8:25 PM, Jerry wrote:

> 
> On Jan 13, 2013, at 6:49 AM, Stephan Witt wrote:
> 
>> Am 13.01.2013 um 14:18 schrieb Kornel Benko <kor...@lyx.org>:
>> 
>>> Am Samstag, 12. Januar 2013 um 19:24:32, schrieb Jerry 
>>> <lancebo...@qwest.net>
>>>> Back on the bisection trail
>>>> 
>>>> I'm having more trouble building from source for this bisection.
> 
> That explains what I've been seeing. (BTW, I can now build master using 
> cmake--the "QT_QT_INCLUDE_DIR problem" is fixed.) When I try to build branch 
> 2.0.0 after cd-ing to the build directory, I get this:
> 
> CMake Error: The source directory 
> "/Applications/Words/LyX_outer_folder/lyx-git/lyx" (<< that's my git 
> repository) does not appear to contain CMakeLists.txt.
> 
> So I was cd-ing to the /bla/development/cmake directory so that I could see 
> CMakeLists.txt and I think that's what was causing the tree pollution. I just 
> now tried building again from 2.0.0 and got the same result. I see that you 
> (Stephan) and Kornel are woking on this
> 
> Jerry 

Well, I seem to have lost the ability to build anything but master. I've tried 
a few things to build 2.0.0 such as building inside /bla/bla/development/cmake 
so that CMakeLists.txt is seen, and making a symlink of 
/bla/bla/development/cmake/CMakeLists.txt to /bla/bla/. 

The first attempt (build in /bla/bla/development/cmake) fails like this:

CMake Error: The source directory "/bla/bla" does not appear to contain 
CMakeLists.txt.
  (where /bla/bla is the source root directory.)

The second attempt (symlink) fails thusly:

CMake Error at CMakeLists.txt:27 (include):
  include could not find load file:

LyXMacros

CMake Error at CMakeLists.txt:37 (LYX_OPTION_INIT):
  Unknown CMake command "LYX_OPTION_INIT".


Jerry

>> 
>> Jerry is on a Mac and want's to make a time travel from 1.6.10 over 2.0.x to 
>> 2.1.x.
>> 
>> So, he has a problem to do so, probably.
>> 
>> Stephan
> 

Re: Need help doing bisection for scrolling problem on OS X

[Jerry]

On Jan 13, 2013, at 6:18 AM, Kornel Benko wrote:

 Am Samstag, 12. Januar 2013 um 19:24:32, schrieb Jerry lancebo...@qwest.net
  Back on the bisection trail

  CMake Error: The following variables are used in this project, but they are 
  set to NOTFOUND.
  Please set them or make sure they are set and tested correctly in the CMake 
  files:
  QT_QT_INCLUDE_DIR (ADVANCED)
 used as include directory in directory 
  /Applications/Words/LyX_outer_folder/lyx-git/lyx/src
  etc. -- more similar lines 

  did not help. How do I define QT_QT_INCLUDE_DIR?
  
 If you are on ubuntu/debian, you have to install the package libqt4-dev. 
 There should be
 a appropriate package on your platform.

Ah--thanks Kornel. I fixed in on my OS X using Macports. I'm now able to build 
from master using cmake.
Jerry