Re: lyx2lyx roundtrip fails for Embedded Objects manual

[Jürgen Spitzmüller]

2014-05-15 21:56 GMT+02:00 Georg Baum:

 IMHO we should
 never try to interpret ERT.


In the beamer case, it was necessary, since old ERT arguments cease to work
due to the redefinitions.

Jürgen

Segfault in comparing documents

[stefano franchi]

[repost as I sent it to the wrong lyx list by mistake]

I never use the compare documents feature and while trying it out today I
got a segfault. I enclosed what I got in the terminal below.
The culprit seems to be the lack of a Title* environment in one of the
two  layouts. The two papers I compared used two different Springer
classes/layout (LNCS and svn-mono), and only one of them has indeed Title*.
Changing the environment to a regular Title allowed LyX to fix the issue.

I did not find any related bug on the tracker, btw, but I may have missed
it.

Any more info I should add to the bug report?


Cheers,

Stefano


terminal output:

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send
us a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!
--
--
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send
us a bug report, if necessary. Thanks!
Bye.
We failed to find the layout 'Title*' in the layout list. You MUST
investigate!
 Plain Layout
 Standard
 Section
 Subsection
 Subsubsection
 Paragraph
 Subparagraph
 Chapter*
 Section*
 Subsection*
 Subsubsection*
 Paragraph*
 Subparagraph*
 Quotation
 Quote
 Verse
 --Separator--
 Labeling
 Itemize
 Enumerate
 Description
 List
 Title
 Subtitle
 Running LaTeX Title
 TOC Title
 Author
 Author Running
 TOC Author
 Institute
 Email
 Abstract
 Bibliography
 Case
 Claim
 Conjecture
 Corollary
 Definition
 Example
 Exercise
 Lemma
 Note
 Problem
 Proof
 Property
 Proposition
 Question
 Remark
 Solution
 Theorem
lassert.cpp (35): ASSERTION false VIOLATED IN TextClass.cpp:1131
Segmentation fault (core dumped)


-- 
__
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: Segfault in comparing documents

[Jean-Marc Lasgouttes]

16/05/2014 15:33, stefano franchi:

[repost as I sent it to the wrong lyx list by mistake]

I never use the compare documents feature and while trying it out
today I got a segfault. I enclosed what I got in the terminal below.
The culprit seems to be the lack of a Title* environment in one of the
two  layouts. The two papers I compared used two different Springer
classes/layout (LNCS and svn-mono), and only one of them has indeed Title*.
Changing the environment to a regular Title allowed LyX to fix the issue.

I did not find any related bug on the tracker, btw, but I may have
missed it.

Any more info I should add to the bug report?


This looks like a new bug indeed. Please add two simple example files to 
the bug report. I am surprised actually that it is possible to compare 
two files with different textclesses.


JMarc

Re: [LyX/master] Do not forget last word of paragraph in completion

[Jean-Marc Lasgouttes]

16/05/2014 15:22, Jean-Marc Lasgouttes:

commit ee7c4db72a9dd392d7e1e34463c3ae11fce670ee
Author: Jean-Marc Lasgouttes lasgout...@lyx.org
Date:   Fri May 16 15:17:10 2014 +0200

 Do not forget last word of paragraph in completion

 With the old code, the last word of a paragraph would not be added in
 the completion list. The key difference is to pass `from' instead of `pos'
 to FontList::fontiterator.

 Slight cleanup of the code.


Richard, this is candidate for branch. There is no hurry since nobody 
ever noticed it :)


JMarc

Re: [LyX/master] Do not forget last word of paragraph in completion

[Richard Heck]

On 05/16/2014 09:42 AM, Jean-Marc Lasgouttes wrote:

16/05/2014 15:22, Jean-Marc Lasgouttes:

commit ee7c4db72a9dd392d7e1e34463c3ae11fce670ee
Author: Jean-Marc Lasgouttes lasgout...@lyx.org
Date:   Fri May 16 15:17:10 2014 +0200

 Do not forget last word of paragraph in completion

 With the old code, the last word of a paragraph would not be 
added in
 the completion list. The key difference is to pass `from' 
instead of `pos'

 to FontList::fontiterator.

 Slight cleanup of the code.


Richard, this is candidate for branch. There is no hurry since nobody 
ever noticed it :)


As you think best.

rh

Re: [LyX/master] Do not forget last word of paragraph in completion

[Jean-Marc Lasgouttes]

16/05/2014 16:12, Richard Heck:

Richard, this is candidate for branch. There is no hurry since nobody
ever noticed it :)


As you think best.


I'll wait for 2.1.2 for this kind of mundane stuff.

JMarc

Re: Segfault in comparing documents

[stefano franchi]

On Fri, May 16, 2014 at 8:40 AM, Jean-Marc Lasgouttes lasgout...@lyx.orgwrote:

 16/05/2014 15:33, stefano franchi:

  [repost as I sent it to the wrong lyx list by mistake]

 I never use the compare documents feature and while trying it out
 today I got a segfault. I enclosed what I got in the terminal below.
 The culprit seems to be the lack of a Title* environment in one of the
 two  layouts. The two papers I compared used two different Springer
 classes/layout (LNCS and svn-mono), and only one of them has indeed
 Title*.
 Changing the environment to a regular Title allowed LyX to fix the issue.

 I did not find any related bug on the tracker, btw, but I may have
 missed it.

 Any more info I should add to the bug report?


 This looks like a new bug indeed. Please add two simple example files to
 the bug report. I am surprised actually that it is possible to compare two
 files with different textclesses.


Done: http://www.lyx.org/trac/attachment/ticket/9125/



S.



-- 
__
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: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 03:31:51PM +0200, Enrico Forestieri wrote:
 commit 95787a0a4c3f6c037b22cb4ba8c98f2e8fa988de
 Author: Enrico Forestieri for...@lyx.org
 Date:   Fri May 16 15:11:08 2014 +0200
 
 Fix an on-screen representation glitch.
 
 If a layout has NextNoIndent set to true, the following paragraph
 is not indented on screen. LyX checks the previous layout for that
 style parameter to decide whether to indent or not. Of course,
 what matters is the latex output and the on-screen representation
 should match this output. Now, when a layout has NextNoIndent==true,
 the latex output is correctly not indented, while the on-screen
 representation may fail to match this output. This can occur when,
 for example, a standard paragraph is nested in the previous layout,
 because LyX would check the property of the nested layout instead
 of the container layout. Thus, LyX should check the property of a
 previous layout at the same depth for correctly deciding whether
 a paragraph has to be indented or not.
 See also http://www.lyx.org/trac/ticket/9055#comment:12 for an
 example document where the previous scenario actually occurs.

Richard, this could go to branch. It's only cosmetic, though.

 diff --git a/src/TextMetrics.cpp b/src/TextMetrics.cpp
 index 790d706..0be9058 100644
 --- a/src/TextMetrics.cpp
 +++ b/src/TextMetrics.cpp
 @@ -1907,12 +1907,13 @@ int TextMetrics::leftMargin(int max_width,
   }
   }
  
 - // This happens after sections in standard classes. The 1.3.x
 - // code compared depths too, but it does not seem necessary
 - // (JMarc)
 - if (tclass.isDefaultLayout(par.layout())
 -  pit  0  pars[pit - 1].layout().nextnoindent)
 - parindent.erase();
 + // This happens after sections or environments in standard classes.
 + // We have to check the previous layout at same depth.
 + if (tclass.isDefaultLayout(par.layout())  pit  0) {
 + pit_type prev = text_-depthHook(pit, par.getDepth());
 + if (pars[prev  pit ? prev : pit - 1].layout().nextnoindent)
 + parindent.erase();
 + }
  
   FontInfo const labelfont = text_-labelFont(par);
   FontMetrics const  labelfont_metrics = theFontMetrics(labelfont);

-- 
Enrico

Re: Re: Re: Re: Plans for python support on lyx-2.2

[José Matos]

On Thursday 15 May 2014 21:07:28 Georg Baum wrote:
 This plan looks sensible. As far as OS X 10.7 is concerned: 
 https://www.python.org/download/mac claims that you can install their binary 
 packages in parallel to the system python, so if anybody really wants to use 
 a current version of LyX on a 5 year old OS, the he could as well do the 
 extra work and install an additional python package.
 
 Georg

Would anyone oppose to change the requirements for devel as stated above?

python 2.7 or 3.3+

-- 
José Abílio

Re: Plans for python support on lyx-2.2

[Richard Heck]

On 05/16/2014 11:10 AM, José Matos wrote:

On Thursday 15 May 2014 21:07:28 Georg Baum wrote:

This plan looks sensible. As far as OS X 10.7 is concerned:
https://www.python.org/download/mac claims that you can install their binary
packages in parallel to the system python, so if anybody really wants to use
a current version of LyX on a 5 year old OS, the he could as well do the
extra work and install an additional python package.

Georg

Would anyone oppose to change the requirements for devel as stated above?

python 2.7 or 3.3+


I don't, but I'd suggest you reissue this question with a new subject 
line, so everyone will see it.


Richard

Re: [LyX/master] Fix an on-screen representation glitch.

[Richard Heck]

On 05/16/2014 11:07 AM, Enrico Forestieri wrote:

On Fri, May 16, 2014 at 03:31:51PM +0200, Enrico Forestieri wrote:

commit 95787a0a4c3f6c037b22cb4ba8c98f2e8fa988de
Author: Enrico Forestieri for...@lyx.org
Date:   Fri May 16 15:11:08 2014 +0200

 Fix an on-screen representation glitch.
 
 If a layout has NextNoIndent set to true, the following paragraph

 is not indented on screen. LyX checks the previous layout for that
 style parameter to decide whether to indent or not. Of course,
 what matters is the latex output and the on-screen representation
 should match this output. Now, when a layout has NextNoIndent==true,
 the latex output is correctly not indented, while the on-screen
 representation may fail to match this output. This can occur when,
 for example, a standard paragraph is nested in the previous layout,
 because LyX would check the property of the nested layout instead
 of the container layout. Thus, LyX should check the property of a
 previous layout at the same depth for correctly deciding whether
 a paragraph has to be indented or not.
 See also http://www.lyx.org/trac/ticket/9055#comment:12 for an
 example document where the previous scenario actually occurs.

Richard, this could go to branch. It's only cosmetic, though.


As you think best.

Richard

Re: Call for testers: the features/str-metrics branch

[Jean-Marc Lasgouttes]

11/05/2014 23:37, Guy Rutenberg:

Hi,


On 12 May 2014 00:31, Guy Rutenberg guyrutenb...@gmail.com
mailto:guyrutenb...@gmail.com wrote:

I did some initial testing and came up with the following wrong
behavior:


I actually found a more serious bug. When in RTL mode (`language
hebrew`) if one types a single continuous line without any spaces, LyX
simply hangs when it reaches the end-of-line. If there are spaces it
breaks the line correctly. I've checked it on Linux, can others
reproduce the bug as well?


I am not sure how to reproduce. Could I have an example file for this 
bug please?


JMarc

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 11:50:44AM -0400, Richard Heck wrote:
 On 05/16/2014 11:07 AM, Enrico Forestieri wrote:
 Richard, this could go to branch. It's only cosmetic, though.
 
 As you think best.

I pushed it. However, git told me bad things:

$ git push
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.07 KiB, done.
Total 5 (delta 4), reused 0 (delta 0)
To g...@git.lyx.org:lyx
   b17802b..f5a246b  2.1.x - 2.1.x
 ! [rejected]2.0.x - 2.0.x (non-fast-forward)
error: failed to push some refs to 'g...@git.lyx.org:lyx'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes (e.g. 'git pull') before pushing again.  See the
'Note about fast-forwards' section of 'git push --help' for details.


I think it is still trying to do something with the 2.0.x branch behind
my back. What are the magic words I have to use to stop it from doing that?

-- 
Enrico

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 10:37:31PM +0200, Enrico Forestieri wrote:

 On Fri, May 16, 2014 at 11:50:44AM -0400, Richard Heck wrote:
  On 05/16/2014 11:07 AM, Enrico Forestieri wrote:
  Richard, this could go to branch. It's only cosmetic, though.
  
  As you think best.
 
 I pushed it. However, git told me bad things:
 
 $ git push
 Counting objects: 9, done.
 Delta compression using up to 2 threads.
 Compressing objects: 100% (5/5), done.
 Writing objects: 100% (5/5), 1.07 KiB, done.
 Total 5 (delta 4), reused 0 (delta 0)
 To g...@git.lyx.org:lyx
b17802b..f5a246b  2.1.x - 2.1.x
  ! [rejected]2.0.x - 2.0.x (non-fast-forward)
 error: failed to push some refs to 'g...@git.lyx.org:lyx'
 To prevent you from losing history, non-fast-forward updates were rejected
 Merge the remote changes (e.g. 'git pull') before pushing again.  See the
 'Note about fast-forwards' section of 'git push --help' for details.
 
 
 I think it is still trying to do something with the 2.0.x branch behind
 my back. What are the magic words I have to use to stop it from doing that?

After some googling I think I need to issue the following commands:

$ git branch -d -r origin/2.0.x
$ git config --unset branch.2.0.x.remote
$ git config --unset branch.2.0.x.merge

Is that correct?

-- 
Enrico

Re: Where is my menubar?

[Scott Kostyshak]

On Tue, May 13, 2014 at 2:40 PM, Scott Kostyshak skost...@lyx.org wrote:
 On Tue, May 13, 2014 at 9:34 AM, Richard Heck rgh...@lyx.org wrote:

 Does one have to do this every time?

 Yes (or use an alias). I guess that's good in the sense that it's 100%
 reproducible.

There appears to be a bug in the appmenu-qt5 package. The menu bar
comes back after
sudo apt-get remove appmenu-qt5

See: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1307619
If anyone is experiencing the bug, please add yourself to the me too
list (there are only 5 of us so far).

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Scott Kostyshak]

On Fri, May 16, 2014 at 5:02 PM, Enrico Forestieri for...@lyx.org wrote:

 Merge the remote changes (e.g. 'git pull') before pushing again.  See the

When I get this error, doing a
git pull --rebase
is usually what I want. Git will not let you push if you do not have
the latest version. Even if you edited a file that does not conflict
with the updates you don't have. The --rebase just tells git to put
your patch on top of the commits that you're going to pull in.

Scott

Re: Call for testers: the features/str-metrics branch

[Scott Kostyshak]

On Fri, May 16, 2014 at 11:53 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
 11/05/2014 23:37, Guy Rutenberg:

 Hi,



 On 12 May 2014 00:31, Guy Rutenberg guyrutenb...@gmail.com
 mailto:guyrutenb...@gmail.com wrote:

 I did some initial testing and came up with the following wrong
 behavior:


 I actually found a more serious bug. When in RTL mode (`language
 hebrew`) if one types a single continuous line without any spaces, LyX
 simply hangs when it reaches the end-of-line. If there are spaces it
 breaks the line correctly. I've checked it on Linux, can others
 reproduce the bug as well?


 I am not sure how to reproduce. Could I have an example file for this bug
 please?

I can reproduce on 37494dfb and 13551a9f. What I did was:

1. open examples/he/splash.lyx
2. click on the bottom right corner (under the 6th point).
3. press return twice (this will give a .6 above the .7)
4. hold f for a while. On 37494dfb I think it froze right when it
got to the end of the string, but 13551a9f survives a little longer:
hold f until it gets to the end of the first line, wraps around to
the end of the next line, and hold it 10 seconds after that. Then hold
a. I only have to hold a for a couple of seconds until it freezes
(infinite loop?).

If you cannot reproduce, might a screen cast help?

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 05:45:27PM -0400, Scott Kostyshak wrote:

 On Fri, May 16, 2014 at 5:02 PM, Enrico Forestieri for...@lyx.org wrote:
 
  Merge the remote changes (e.g. 'git pull') before pushing again.  See the
 
 When I get this error, doing a
 git pull --rebase
 is usually what I want. Git will not let you push if you do not have
 the latest version. Even if you edited a file that does not conflict
 with the updates you don't have. The --rebase just tells git to put
 your patch on top of the commits that you're going to pull in.

No, this cannot be the reason. My procedure for pushing is the following:

$ git commit -a
$ git pull --rebase
$ git push

so, I had just issued that command. It has something to do with the fact
that previously I had 2.0.x as a checked out branch and then I switched
to 2.1.x. Now git is still someway trying to also push 2.0.x and I would
like to tell it not to do that, but I don't know neither why it still
insists on 2.0.x nor what I can do. Maybe it is simpler to start afresh
and clone again the repository. I like very much git branches.

-- 
Enrico

Re: [LyX/master] Fix an on-screen representation glitch.

[Scott Kostyshak]

On Fri, May 16, 2014 at 6:01 PM, Enrico Forestieri for...@lyx.org wrote:

 Now git is still someway trying to also push 2.0.x and I would
 like to tell it not to do that, but I don't know neither why it still
 insists on 2.0.x nor what I can do.

From what I understand, when you do a git push you only want to push
the branch that you have checked out. If that's right, then putting
the following should do that:

git config --global push.default current

Note the global. I assume you want this for all Git-related projects.

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 06:09:17PM -0400, Scott Kostyshak wrote:

 On Fri, May 16, 2014 at 6:01 PM, Enrico Forestieri for...@lyx.org wrote:
 
  Now git is still someway trying to also push 2.0.x and I would
  like to tell it not to do that, but I don't know neither why it still
  insists on 2.0.x nor what I can do.
 
 From what I understand, when you do a git push you only want to push
 the branch that you have checked out.

Exactly.

 If that's right, then putting
 the following should do that:
 
 git config --global push.default current
 
 Note the global. I assume you want this for all Git-related projects.

Maybe you are right. But I have now found .git/config whose content is:

$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
[remote origin]
fetch = +refs/heads/*:refs/remotes/origin/*
url = g...@git.lyx.org:lyx
[branch 2.0.x]
remote = origin
merge = refs/heads/2.0.x
[merge]
defaultToUpstream = true
[gui]
wmstate = normal
geometry = 1031x427+46+46 282 192
[branch 2.1.x]
remote = origin
merge = refs/heads/2.1.x


and I simply plan removing the [branch 2.0.x] stanza.

-- 
Enrico

Re: [LyX/master] Fix an on-screen representation glitch.

[Scott Kostyshak]

On Fri, May 16, 2014 at 6:21 PM, Enrico Forestieri for...@lyx.org wrote:

 and I simply plan removing the [branch 2.0.x] stanza.

Ah, now I see what you meant above. I am still not used to 2.0.x as
being old. I was reading it as I should read 2.1.x. I still put the
date as 2013 also :)

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 06:26:00PM -0400, Scott Kostyshak wrote:

 On Fri, May 16, 2014 at 6:21 PM, Enrico Forestieri for...@lyx.org wrote:
 
  and I simply plan removing the [branch 2.0.x] stanza.
 
 Ah, now I see what you meant above. I am still not used to 2.0.x as
 being old. I was reading it as I should read 2.1.x. I still put the
 date as 2013 also :)

I now tried my luck and issued the commands I found googling:
$ git branch -d -r origin/2.0.x
$ git config --unset branch.2.0.x.remote
$ git config --unset branch.2.0.x.merge

then I looked again at .git/config
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
[remote origin]
fetch = +refs/heads/*:refs/remotes/origin/*
url = g...@git.lyx.org:lyx
[branch 2.0.x]
[merge]
defaultToUpstream = true
[gui]
wmstate = normal
geometry = 1031x427+46+46 282 192
[branch 2.1.x]
remote = origin
merge = refs/heads/2.1.x

and it actually almost got rid of the [branch 2.0.x] stanza, leaving
only the header. I would like to get rid of that too, but I don't know
what of the git options of the type --reset --hard --really --please
I have to use. Perhaps I will simply use an editor and be done with it.

-- 
Enrico

Re: lyx2lyx roundtrip fails for Embedded Objects manual

[Jürgen Spitzmüller]

2014-05-15 21:56 GMT+02:00 Georg Baum:

> IMHO we should
> never try to interpret ERT.
>

In the beamer case, it was necessary, since old ERT arguments cease to work
due to the redefinitions.

Jürgen

Segfault in comparing documents

[stefano franchi]

[repost as I sent it to the wrong lyx list by mistake]

I never use the "compare documents" feature and while trying it out today I
got a segfault. I enclosed what I got in the terminal below.
The culprit seems to be the lack of a "Title*" environment in one of the
two  layouts. The two papers I compared used two different Springer
classes/layout (LNCS and svn-mono), and only one of them has indeed Title*.
Changing the environment to a regular Title allowed LyX to fix the issue.

I did not find any related bug on the tracker, btw, but I may have missed
it.

Any more info I should add to the bug report?


Cheers,

Stefano


terminal output:

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send
us a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!
--
--
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send
us a bug report, if necessary. Thanks!
Bye.
We failed to find the layout 'Title*' in the layout list. You MUST
investigate!
 Plain Layout
 Standard
 Section
 Subsection
 Subsubsection
 Paragraph
 Subparagraph
 Chapter*
 Section*
 Subsection*
 Subsubsection*
 Paragraph*
 Subparagraph*
 Quotation
 Quote
 Verse
 --Separator--
 Labeling
 Itemize
 Enumerate
 Description
 List
 Title
 Subtitle
 Running LaTeX Title
 TOC Title
 Author
 Author Running
 TOC Author
 Institute
 Email
 Abstract
 Bibliography
 Case
 Claim
 Conjecture
 Corollary
 Definition
 Example
 Exercise
 Lemma
 Note
 Problem
 Proof
 Property
 Proposition
 Question
 Remark
 Solution
 Theorem
lassert.cpp (35): ASSERTION false VIOLATED IN TextClass.cpp:1131
Segmentation fault (core dumped)


-- 
__
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: Segfault in comparing documents

[Jean-Marc Lasgouttes]

16/05/2014 15:33, stefano franchi:

[repost as I sent it to the wrong lyx list by mistake]

I never use the "compare documents" feature and while trying it out
today I got a segfault. I enclosed what I got in the terminal below.
The culprit seems to be the lack of a "Title*" environment in one of the
two  layouts. The two papers I compared used two different Springer
classes/layout (LNCS and svn-mono), and only one of them has indeed Title*.
Changing the environment to a regular Title allowed LyX to fix the issue.

I did not find any related bug on the tracker, btw, but I may have
missed it.

Any more info I should add to the bug report?


This looks like a new bug indeed. Please add two simple example files to 
the bug report. I am surprised actually that it is possible to compare 
two files with different textclesses.


JMarc

Re: [LyX/master] Do not forget last word of paragraph in completion

[Jean-Marc Lasgouttes]

16/05/2014 15:22, Jean-Marc Lasgouttes:

commit ee7c4db72a9dd392d7e1e34463c3ae11fce670ee
Author: Jean-Marc Lasgouttes 
Date:   Fri May 16 15:17:10 2014 +0200

 Do not forget last word of paragraph in completion

 With the old code, the last word of a paragraph would not be added in
 the completion list. The key difference is to pass `from' instead of `pos'
 to FontList::fontiterator.

 Slight cleanup of the code.


Richard, this is candidate for branch. There is no hurry since nobody 
ever noticed it :)


JMarc

Re: [LyX/master] Do not forget last word of paragraph in completion

[Richard Heck]

On 05/16/2014 09:42 AM, Jean-Marc Lasgouttes wrote:

16/05/2014 15:22, Jean-Marc Lasgouttes:

commit ee7c4db72a9dd392d7e1e34463c3ae11fce670ee
Author: Jean-Marc Lasgouttes 
Date:   Fri May 16 15:17:10 2014 +0200

 Do not forget last word of paragraph in completion

 With the old code, the last word of a paragraph would not be 
added in
 the completion list. The key difference is to pass `from' 
instead of `pos'

 to FontList::fontiterator.

 Slight cleanup of the code.


Richard, this is candidate for branch. There is no hurry since nobody 
ever noticed it :)


As you think best.

rh

Re: [LyX/master] Do not forget last word of paragraph in completion

[Jean-Marc Lasgouttes]

16/05/2014 16:12, Richard Heck:

Richard, this is candidate for branch. There is no hurry since nobody
ever noticed it :)


As you think best.


I'll wait for 2.1.2 for this kind of mundane stuff.

JMarc

Re: Segfault in comparing documents

[stefano franchi]

On Fri, May 16, 2014 at 8:40 AM, Jean-Marc Lasgouttes wrote:

> 16/05/2014 15:33, stefano franchi:
>
>  [repost as I sent it to the wrong lyx list by mistake]
>>
>> I never use the "compare documents" feature and while trying it out
>> today I got a segfault. I enclosed what I got in the terminal below.
>> The culprit seems to be the lack of a "Title*" environment in one of the
>> two  layouts. The two papers I compared used two different Springer
>> classes/layout (LNCS and svn-mono), and only one of them has indeed
>> Title*.
>> Changing the environment to a regular Title allowed LyX to fix the issue.
>>
>> I did not find any related bug on the tracker, btw, but I may have
>> missed it.
>>
>> Any more info I should add to the bug report?
>>
>
> This looks like a new bug indeed. Please add two simple example files to
> the bug report. I am surprised actually that it is possible to compare two
> files with different textclesses.
>
>
Done: http://www.lyx.org/trac/attachment/ticket/9125/



S.



-- 
__
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: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 03:31:51PM +0200, Enrico Forestieri wrote:
> commit 95787a0a4c3f6c037b22cb4ba8c98f2e8fa988de
> Author: Enrico Forestieri 
> Date:   Fri May 16 15:11:08 2014 +0200
> 
> Fix an on-screen representation glitch.
> 
> If a layout has NextNoIndent set to true, the following paragraph
> is not indented on screen. LyX checks the previous layout for that
> style parameter to decide whether to indent or not. Of course,
> what matters is the latex output and the on-screen representation
> should match this output. Now, when a layout has NextNoIndent==true,
> the latex output is correctly not indented, while the on-screen
> representation may fail to match this output. This can occur when,
> for example, a standard paragraph is nested in the previous layout,
> because LyX would check the property of the nested layout instead
> of the container layout. Thus, LyX should check the property of a
> previous layout at the same depth for correctly deciding whether
> a paragraph has to be indented or not.
> See also http://www.lyx.org/trac/ticket/9055#comment:12 for an
> example document where the previous scenario actually occurs.

Richard, this could go to branch. It's only cosmetic, though.

> diff --git a/src/TextMetrics.cpp b/src/TextMetrics.cpp
> index 790d706..0be9058 100644
> --- a/src/TextMetrics.cpp
> +++ b/src/TextMetrics.cpp
> @@ -1907,12 +1907,13 @@ int TextMetrics::leftMargin(int max_width,
>   }
>   }
>  
> - // This happens after sections in standard classes. The 1.3.x
> - // code compared depths too, but it does not seem necessary
> - // (JMarc)
> - if (tclass.isDefaultLayout(par.layout())
> - && pit > 0 && pars[pit - 1].layout().nextnoindent)
> - parindent.erase();
> + // This happens after sections or environments in standard classes.
> + // We have to check the previous layout at same depth.
> + if (tclass.isDefaultLayout(par.layout()) && pit > 0) {
> + pit_type prev = text_->depthHook(pit, par.getDepth());
> + if (pars[prev < pit ? prev : pit - 1].layout().nextnoindent)
> + parindent.erase();
> + }
>  
>   FontInfo const labelfont = text_->labelFont(par);
>   FontMetrics const & labelfont_metrics = theFontMetrics(labelfont);

-- 
Enrico

Re: Re: Re: Re: Plans for python support on lyx-2.2

[José Matos]

On Thursday 15 May 2014 21:07:28 Georg Baum wrote:
> This plan looks sensible. As far as OS X 10.7 is concerned: 
> https://www.python.org/download/mac claims that you can install their binary 
> packages in parallel to the system python, so if anybody really wants to use 
> a current version of LyX on a 5 year old OS, the he could as well do the 
> extra work and install an additional python package.
> 
> Georg

Would anyone oppose to change the requirements for devel as stated above?

python 2.7 or 3.3+

-- 
José Abílio

Re: Plans for python support on lyx-2.2

[Richard Heck]

On 05/16/2014 11:10 AM, José Matos wrote:

On Thursday 15 May 2014 21:07:28 Georg Baum wrote:

This plan looks sensible. As far as OS X 10.7 is concerned:
https://www.python.org/download/mac claims that you can install their binary
packages in parallel to the system python, so if anybody really wants to use
a current version of LyX on a 5 year old OS, the he could as well do the
extra work and install an additional python package.

Georg

Would anyone oppose to change the requirements for devel as stated above?

python 2.7 or 3.3+


I don't, but I'd suggest you reissue this question with a new subject 
line, so everyone will see it.


Richard

Re: [LyX/master] Fix an on-screen representation glitch.

[Richard Heck]

On 05/16/2014 11:07 AM, Enrico Forestieri wrote:

On Fri, May 16, 2014 at 03:31:51PM +0200, Enrico Forestieri wrote:

commit 95787a0a4c3f6c037b22cb4ba8c98f2e8fa988de
Author: Enrico Forestieri 
Date:   Fri May 16 15:11:08 2014 +0200

 Fix an on-screen representation glitch.
 
 If a layout has NextNoIndent set to true, the following paragraph

 is not indented on screen. LyX checks the previous layout for that
 style parameter to decide whether to indent or not. Of course,
 what matters is the latex output and the on-screen representation
 should match this output. Now, when a layout has NextNoIndent==true,
 the latex output is correctly not indented, while the on-screen
 representation may fail to match this output. This can occur when,
 for example, a standard paragraph is nested in the previous layout,
 because LyX would check the property of the nested layout instead
 of the container layout. Thus, LyX should check the property of a
 previous layout at the same depth for correctly deciding whether
 a paragraph has to be indented or not.
 See also http://www.lyx.org/trac/ticket/9055#comment:12 for an
 example document where the previous scenario actually occurs.

Richard, this could go to branch. It's only cosmetic, though.


As you think best.

Richard

Re: Call for testers: the features/str-metrics branch

[Jean-Marc Lasgouttes]

11/05/2014 23:37, Guy Rutenberg:

Hi,


On 12 May 2014 00:31, Guy Rutenberg > wrote:

I did some initial testing and came up with the following wrong
behavior:


I actually found a more serious bug. When in RTL mode (`language
hebrew`) if one types a single continuous line without any spaces, LyX
simply hangs when it reaches the end-of-line. If there are spaces it
breaks the line correctly. I've checked it on Linux, can others
reproduce the bug as well?


I am not sure how to reproduce. Could I have an example file for this 
bug please?


JMarc

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 11:50:44AM -0400, Richard Heck wrote:
> On 05/16/2014 11:07 AM, Enrico Forestieri wrote:
> >Richard, this could go to branch. It's only cosmetic, though.
> 
> As you think best.

I pushed it. However, git told me bad things:

$ git push
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.07 KiB, done.
Total 5 (delta 4), reused 0 (delta 0)
To g...@git.lyx.org:lyx
   b17802b..f5a246b  2.1.x -> 2.1.x
 ! [rejected]2.0.x -> 2.0.x (non-fast-forward)
error: failed to push some refs to 'g...@git.lyx.org:lyx'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes (e.g. 'git pull') before pushing again.  See the
'Note about fast-forwards' section of 'git push --help' for details.


I think it is still trying to do something with the 2.0.x branch behind
my back. What are the magic words I have to use to stop it from doing that?

-- 
Enrico

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 10:37:31PM +0200, Enrico Forestieri wrote:

> On Fri, May 16, 2014 at 11:50:44AM -0400, Richard Heck wrote:
> > On 05/16/2014 11:07 AM, Enrico Forestieri wrote:
> > >Richard, this could go to branch. It's only cosmetic, though.
> > 
> > As you think best.
> 
> I pushed it. However, git told me bad things:
> 
> $ git push
> Counting objects: 9, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (5/5), done.
> Writing objects: 100% (5/5), 1.07 KiB, done.
> Total 5 (delta 4), reused 0 (delta 0)
> To g...@git.lyx.org:lyx
>b17802b..f5a246b  2.1.x -> 2.1.x
>  ! [rejected]2.0.x -> 2.0.x (non-fast-forward)
> error: failed to push some refs to 'g...@git.lyx.org:lyx'
> To prevent you from losing history, non-fast-forward updates were rejected
> Merge the remote changes (e.g. 'git pull') before pushing again.  See the
> 'Note about fast-forwards' section of 'git push --help' for details.
> 
> 
> I think it is still trying to do something with the 2.0.x branch behind
> my back. What are the magic words I have to use to stop it from doing that?

After some googling I think I need to issue the following commands:

$ git branch -d -r origin/2.0.x
$ git config --unset branch.2.0.x.remote
$ git config --unset branch.2.0.x.merge

Is that correct?

-- 
Enrico

Re: Where is my menubar?

[Scott Kostyshak]

On Tue, May 13, 2014 at 2:40 PM, Scott Kostyshak  wrote:
> On Tue, May 13, 2014 at 9:34 AM, Richard Heck  wrote:

>> Does one have to do this every time?
>
> Yes (or use an alias). I guess that's good in the sense that it's 100%
> reproducible.

There appears to be a bug in the appmenu-qt5 package. The menu bar
comes back after
sudo apt-get remove appmenu-qt5

See: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1307619
If anyone is experiencing the bug, please add yourself to the "me too"
list (there are only 5 of us so far).

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Scott Kostyshak]

On Fri, May 16, 2014 at 5:02 PM, Enrico Forestieri  wrote:

>> Merge the remote changes (e.g. 'git pull') before pushing again.  See the

When I get this error, doing a
git pull --rebase
is usually what I want. Git will not let you push if you do not have
the latest version. Even if you edited a file that does not conflict
with the updates you don't have. The "--rebase" just tells git to put
your patch on top of the commits that you're going to pull in.

Scott

Re: Call for testers: the features/str-metrics branch

[Scott Kostyshak]

On Fri, May 16, 2014 at 11:53 AM, Jean-Marc Lasgouttes
 wrote:
> 11/05/2014 23:37, Guy Rutenberg:
>>
>> Hi,
>>
>>
>>
>> On 12 May 2014 00:31, Guy Rutenberg > > wrote:
>>
>> I did some initial testing and came up with the following wrong
>> behavior:
>>
>>
>> I actually found a more serious bug. When in RTL mode (`language
>> hebrew`) if one types a single continuous line without any spaces, LyX
>> simply hangs when it reaches the end-of-line. If there are spaces it
>> breaks the line correctly. I've checked it on Linux, can others
>> reproduce the bug as well?
>
>
> I am not sure how to reproduce. Could I have an example file for this bug
> please?

I can reproduce on 37494dfb and 13551a9f. What I did was:

1. open examples/he/splash.lyx
2. click on the bottom right corner (under the 6th point).
3. press return twice (this will give a ".6" above the ".7")
4. hold "f" for a while. On 37494dfb I think it froze right when it
got to the end of the string, but 13551a9f survives a little longer:
hold "f" until it gets to the end of the first line, wraps around to
the end of the next line, and hold it 10 seconds after that. Then hold
"a". I only have to hold "a" for a couple of seconds until it freezes
(infinite loop?).

If you cannot reproduce, might a screen cast help?

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 05:45:27PM -0400, Scott Kostyshak wrote:

> On Fri, May 16, 2014 at 5:02 PM, Enrico Forestieri  wrote:
> 
> >> Merge the remote changes (e.g. 'git pull') before pushing again.  See the
> 
> When I get this error, doing a
> git pull --rebase
> is usually what I want. Git will not let you push if you do not have
> the latest version. Even if you edited a file that does not conflict
> with the updates you don't have. The "--rebase" just tells git to put
> your patch on top of the commits that you're going to pull in.

No, this cannot be the reason. My procedure for pushing is the following:

$ git commit -a
$ git pull --rebase
$ git push

so, I had just issued that command. It has something to do with the fact
that previously I had 2.0.x as a checked out branch and then I switched
to 2.1.x. Now git is still someway trying to also push 2.0.x and I would
like to tell it not to do that, but I don't know neither why it still
insists on 2.0.x nor what I can do. Maybe it is simpler to start afresh
and clone again the repository. I like very much git branches.

-- 
Enrico

Re: [LyX/master] Fix an on-screen representation glitch.

[Scott Kostyshak]

On Fri, May 16, 2014 at 6:01 PM, Enrico Forestieri  wrote:

> Now git is still someway trying to also push 2.0.x and I would
> like to tell it not to do that, but I don't know neither why it still
> insists on 2.0.x nor what I can do.

>From what I understand, when you do a "git push" you only want to push
the branch that you have checked out. If that's right, then putting
the following should do that:

git config --global push.default current

Note the "global". I assume you want this for all Git-related projects.

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 06:09:17PM -0400, Scott Kostyshak wrote:

> On Fri, May 16, 2014 at 6:01 PM, Enrico Forestieri  wrote:
> 
> > Now git is still someway trying to also push 2.0.x and I would
> > like to tell it not to do that, but I don't know neither why it still
> > insists on 2.0.x nor what I can do.
> 
> From what I understand, when you do a "git push" you only want to push
> the branch that you have checked out.

Exactly.

> If that's right, then putting
> the following should do that:
> 
> git config --global push.default current
> 
> Note the "global". I assume you want this for all Git-related projects.

Maybe you are right. But I have now found .git/config whose content is:

$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = g...@git.lyx.org:lyx
[branch "2.0.x"]
remote = origin
merge = refs/heads/2.0.x
[merge]
defaultToUpstream = true
[gui]
wmstate = normal
geometry = 1031x427+46+46 282 192
[branch "2.1.x"]
remote = origin
merge = refs/heads/2.1.x


and I simply plan removing the [branch "2.0.x"] stanza.

-- 
Enrico

Re: [LyX/master] Fix an on-screen representation glitch.

[Scott Kostyshak]

On Fri, May 16, 2014 at 6:21 PM, Enrico Forestieri  wrote:

> and I simply plan removing the [branch "2.0.x"] stanza.

Ah, now I see what you meant above. I am still not used to 2.0.x as
being "old". I was reading it as I should read 2.1.x. I still put the
date as 2013 also :)

Scott

Re: [LyX/master] Fix an on-screen representation glitch.

[Enrico Forestieri]

On Fri, May 16, 2014 at 06:26:00PM -0400, Scott Kostyshak wrote:

> On Fri, May 16, 2014 at 6:21 PM, Enrico Forestieri  wrote:
> 
> > and I simply plan removing the [branch "2.0.x"] stanza.
> 
> Ah, now I see what you meant above. I am still not used to 2.0.x as
> being "old". I was reading it as I should read 2.1.x. I still put the
> date as 2013 also :)

I now tried my luck and issued the commands I found googling:
$ git branch -d -r origin/2.0.x
$ git config --unset branch.2.0.x.remote
$ git config --unset branch.2.0.x.merge

then I looked again at .git/config
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = g...@git.lyx.org:lyx
[branch "2.0.x"]
[merge]
defaultToUpstream = true
[gui]
wmstate = normal
geometry = 1031x427+46+46 282 192
[branch "2.1.x"]
remote = origin
merge = refs/heads/2.1.x

and it actually almost got rid of the [branch "2.0.x"] stanza, leaving
only the header. I would like to get rid of that too, but I don't know
what of the git options of the type --reset --hard --really --please
I have to use. Perhaps I will simply use an editor and be done with it.

-- 
Enrico