Re: fix math toolbars

[Enrico Forestieri]

On Fri, Sep 09, 2016 at 12:04:47PM +0200, Enrico Forestieri wrote:
> On Fri, Sep 09, 2016 at 07:05:52AM +, Guenter Milde wrote:
> 
> > I would appreciate if you could fix it.
> > See http://www.lyx.org/trac/ticket/9616
> 
> This is your hitch. I am not motivated in scratching it.

I did it at cb709469, anyway.

-- 
Enrico

Re: [LyX/master] Fix data loss with [ in first cell of aligned

[Georg Baum]

Richard, OK for branch?

Georg


Georg Baum wrote:

> commit a6be519a815893765a257bec5a456d7f6eecf8f6
> Author: Georg Baum 
> Date:   Thu Sep 8 22:38:33 2016 +0200
> 
> Fix data loss with [ in first cell of aligned
> 
> If the first character in the first cell of an aligned math
> environment is '[', and the environment does not use top or bottom
> vertical alignment, then LyX did write the '[' unprotected so that it
> got misinterpreted as optional argument, both when reading the .lyx
> file in LyX and when reading the .tex file in LaTeX => data loss!
> The fix is to output an empty optional argument in this case, which is
> interpreted as default alignment both by LyX and LaTeX. It would also
> be possible to output \[ in the first cell instead, but this would be
> more difficult to implement.
> ---
>  src/mathed/InsetMathSplit.cpp |   18 ++
>  1 files changed, 14 insertions(+), 4 deletions(-)
> 
> diff --git a/src/mathed/InsetMathSplit.cpp b/src/mathed/InsetMathSplit.cpp
> index 515dcb0..e385e0a 100644
> --- a/src/mathed/InsetMathSplit.cpp
> +++ b/src/mathed/InsetMathSplit.cpp
> @@ -14,7 +14,7 @@
>  
>  #include "MathData.h"
>  #include "MathStream.h"
> -#include "MathStream.h"
> +#include "MathSupport.h"
>  
>  #include "FuncRequest.h"
>  #include "FuncStatus.h"
> @@ -141,9 +141,19 @@ void InsetMathSplit::write(WriteStream & ws) const
>  suffix = from_ascii("*");
>  ws << "\\begin{" << name_ << suffix << '}';
>  bool open = ws.startOuterRow();
> - if (name_ != "split" && name_ != "align" && verticalAlignment() != 
'c')
> - ws << '[' << verticalAlignment() << ']';
> - if (name_ == "alignedat")
> + bool const hasArg(name_ == "alignedat");
> + if (name_ != "split" && name_ != "align") {
> + if (verticalAlignment() != 'c')
> + ws << '[' << verticalAlignment() << ']';
> + else if (!hasArg) {
> + docstring const first(asString(cell(0)));
> + // prevent misinterpretation of the first 
character of
> + // the first cell as optional argument (bug 
10361)
> + if (!first.empty() && first[0] == '[')
> + ws << "[]";
> + }
> + }
> + if (hasArg)
>  ws << '{' << static_cast((ncols() + 1)/2) << '}';
>  InsetMathGrid::write(ws);
>  if (ws.fragile())

Re: cannot compile master

[Kornel Benko]

Am Freitag, 9. September 2016 um 22:29:23, schrieb Guenter Milde 

> On 2016-09-09, Scott Kostyshak wrote:
> > On Fri, Sep 09, 2016 at 12:04:23PM +, Guenter Milde wrote:
> >> Dear LyX Developers,
>
> >> as of today, I cannot compile master, "make" fails with
> ...
> >> GuiView.cpp:(.text+0x1fa85): undefined reference to 
> >> `QSvgRenderer::~QSvgRenderer()'
> ...
>
> >> This is building with cmake from a repo updated today 2016-09-09.
>
> > I can reproduce with current master (b9a47dff) and Qt 4, but not Qt 5.
>
> I believe the reason is in 82808fea04315fd323ec074e8a
> "Set window title according to platform UI"
>
> #include 
>  #include 
> -#if QT_VERSION >= 0x05
>  #include 
> -#endif
>  #include 
>  #include 
>
> and later use of the SVG renderer...
>
> Reverting that commit locally helped.
>
> Günter

Adding ${QT_QTSVG_LIBRARY} to target_link_libraries for lyx works here.

Kornel



signature.asc
Description: This is a digitally signed message part.
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index 0c56ce6..b7d1b06 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -132,6 +132,9 @@ target_link_libraries(${_lyx}
 	${LYX_QTMAIN_LIBRARY}
 	${vld_dll})
 
+if(LYX_USE_QT MATCHES "QT4")
+  target_link_libraries(${_lyx} ${QT_QTSVG_LIBRARY})
+endif()
 qt_use_modules(${_lyx} Core Gui)
 
 if(QT_USES_X11)

Re: Intro with PDF(luatex)

[Kornel Benko]

Am Samstag, 10. September 2016 um 08:03:37, schrieb Guenter Milde 

> On 2016-09-09, Kornel Benko wrote:
> > Am Donnerstag, 8. September 2016 um 16:35:10, schrieb Guenter Milde 
> > 
> 
> Dear Kornel,
> 
> 
> >> ... actually the labeling mechanism is constructed so that inversion
> >> takes precedence and prevents tagging with "unreliable".
> 
> >> Maybe this can be changed in an overhoul of the test setup...
> 
> > Yes, there is some discussion needed.
> 
> Maybe we can start with some simplification...
> 
> * Can we rename "suspiciousTests" to "invertedTests", please?

Sure. Almost alike the original name has been (revertedTests)

>   The "docstring" at the top of the file says:
> 
>  # Regular expressions for tests that are known to fail
>  #
>  # Patterns will be automatically enclosed with '^' and '$'.
>  # Matching tests get the label "inverted"
>  # or (if also matching a pattern in "suspendedTests") "suspended".
>  # They get also the test-feature 'inverted', i.e.
>  # they are reported as failing if the export works without error.
> 
> 
> * Do you still need the "suspendeTests"? What for?

Yes, we need them. This tests will not be executed with the call 'ctest -L 
export'.

>   I know that it was me who suggested this label. 
>   
>   However, the sublabel mechanism supersedes this by giving more
>   detailled info about problems and reasons for failure.

See above.
Nobody prevents us for using sublabels on suspendedTests.

> Thanks
> 
> Günter

Kornel

signature.asc
Description: This is a digitally signed message part.

Ticket 10356 - "Regular expressions do not work on Mac OS X"

[Tadeus Ras]

Dear LyXonauts,

Sorry for the somewhat redundant report. I posted a ticket "Regular expressions 
do not work on Mac OS X" about 10 days ago. Mostly, I would like to know if 
other Mac users encounter the same problem (and if someone possibly found a 
workaround).

I will be offline till the 21st of September but happy to provide further 
details on my return (and even happier about suggestions how to use regular 
expressions with LyX on my Mac ;)

Cheers!
Tadeus

Ticket  "Regular expressions do not work on Mac OS X"
http://www.lyx.org/trac/ticket/10356

Re: Intro with PDF(luatex)

[Guenter Milde]

On 2016-09-09, Kornel Benko wrote:
> Am Donnerstag, 8. September 2016 um 16:35:10, schrieb Guenter Milde 
> 

Dear Kornel,


>> ... actually the labeling mechanism is constructed so that inversion
>> takes precedence and prevents tagging with "unreliable".

>> Maybe this can be changed in an overhoul of the test setup...

> Yes, there is some discussion needed.

Maybe we can start with some simplification...

* Can we rename "suspiciousTests" to "invertedTests", please?
  
  The "docstring" at the top of the file says:

 # Regular expressions for tests that are known to fail
 #
 # Patterns will be automatically enclosed with '^' and '$'.
 # Matching tests get the label "inverted"
 # or (if also matching a pattern in "suspendedTests") "suspended".
 # They get also the test-feature 'inverted', i.e.
 # they are reported as failing if the export works without error.


* Do you still need the "suspendeTests"? What for?

  I know that it was me who suggested this label. 
  
  However, the sublabel mechanism supersedes this by giving more
  detailled info about problems and reasons for failure.


Thanks

Günter

Re: fix math toolbars

[Enrico Forestieri]

On Fri, Sep 09, 2016 at 12:43:27AM +0200, Enrico Forestieri wrote:
> On Thu, Sep 08, 2016 at 10:13:27PM +, Guenter Milde wrote:
> > 
> > * if I insert a literal degree-sign from the keyboard into mathed, LyX
> >   wraps it in \text while inserting, 
> 
> Yes, this was my doing after you insisted so much that at the end
> I surrendered and changed this from the previous behavior of "silently"
> wrapping it in \lyxmathsym. I will never do again the same error.

Well, I did it again. Now when a command is inserted in the wrong mode,
it is explicitly wrapped in the right mode-changing command. I don't
like it but is easy dissolving an unwanted inset.

> > > If you copy and paste an equation outside of lyx, the
> > > "silent additions" are also provided, so they are not so silent.
> > 
> > Really? With an integral in "mathed text" I got:
> > 
> > * in the source pane: $A=\text{\ensuremath{\int}d}x$
> > 
> > * copying the complete mathbox: A=\text{\ensuremath{\int}d}x
> >  
> > * copying from inside the math-box: \text{\int d}x
> 
> This is really strange. I did the same, progressively reducing the
> selection from outside to inside I obtain:
> 
> 1) A=\text{\ensuremath{\int}d}x
> 2) =\text{\ensuremath{\int}d}x
> 3) =\text{\ensuremath{\int}d}
> 4) \text{\ensuremath{\int}d}
> 5) \ensuremath{\int}d
> 
> So, it seems that I cannot reproduce.

I was wrong and I apologize for this. The problem is that I copy-pasted
the above equation in lyx and then hit Ctrl-M, without realizing that
the ensuremath inset was actually entered in this case.

-- 
Enrico

Re: [LyX/master] ctests: Move tests failing only with newest luatex to unreliableTests.

[Kornel Benko]

Am Samstag, 10. September 2016 um 12:37:47, schrieb Günter Milde 

> commit a6c6bbabe938427165eddc668568b793087d15d6
> Author: Günter Milde 
> Date:   Sat Sep 10 10:10:28 2016 +0200
> 
> ctests: Move tests failing only with newest luatex to unreliableTests.

I have the newest luatex from TL16 (not from svn though)
# ctest -R 'export/doc/(nb|el)/Intro_pdf5_'
1071 - INVERTED.TODO_export/doc/el/Intro_pdf5_texF (Failed)
1072 - INVERTED.TODO_export/doc/el/Intro_pdf5_systemF (Failed)
1738 - INVERTED.TODO_export/doc/nb/Intro_pdf5_texF (Failed)

The only one which passes is INVERTED.TODO_export/doc/nb/Intro_pdf5_system
There must be something else which makes it fail on your side.
Nonetheless, I too think the move is OK.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Intro with PDF(luatex)

[Guenter Milde]

On 2016-09-10, Scott Kostyshak wrote:
> On Fri, Sep 09, 2016 at 06:24:02PM +, Guenter Milde wrote:
>> On 2016-09-09, Scott Kostyshak wrote:

>> ...

>> > INVERTED.TODO_export/doc/nb/Intro_pdf5_texF

>> > I should also say that I have not checked whether the output is correct,
>> > or if e.g. the export is without error but the PDF contains gibberish.

>> The error here is

>> ! LaTeX Error: Cannot determine size of graphic in 
>> 0_usr_local_src_lyx_lib_doc_
>> clipart_footnote.png (no BoundingBox).

... and the PDF contains empty spaces instead of the png images.


> Is this with an updated TL 2016? 

Yes, this happened after updating TL 2016 to the version in Debian/testing
about a week ago.

> I can't reproduce with LyX compiled with Qt 5 or Qt 4. 

I use QT 4 but I don't think this is important. The error is only manifest
with PDF(luatex) (i.e. not with DVI(luatex) nor with any other engine.

> Can you send the full LaTeX log for e.g. the first test referenced
> above (the Greek Intro with LuaTeX (PDF) and TeX fonts)?

I append the "Norsk" log (less other sources for problems as Greek is always
tricky).


Günter



This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian)  (format=lualatex 
2016.9.6)  10 SEP 2016 09:10
 restricted system commands enabled.
**Intro.tex
(./Intro.tex
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 1 language(s) loaded.

(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo
File: size12.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/share/texlive/texmf-dist/tex/latex/psnfss/mathpazo.sty
Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS) 
\symupright=\mathgroup4
) (/usr/share/texlive/texmf-dist/tex/latex/psnfss/helvet.sty
Package: helvet 2005/04/12 PSNFSS-v9.2a (WaS) 
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks14
)) (/usr/share/texlive/texmf-dist/tex/latex/psnfss/courier.sty
Package: courier 2005/04/12 PSNFSS-v9.2a (WaS) 
) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2016/06/19 v1.99m Standard LaTeX package
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2016/06/19 v1.99m Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 48.
)) (/usr/share/texlive/texmf-dist/tex/lualatex/luainputenc/luainputenc.sty
Package: luainputenc 2010/11/19 v0.973 inputenc package for LuaTeX
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
Package: ifluatex 2016/05/16 v1.4 Provides the ifluatex switch (HO)
Package ifluatex Info: LuaTeX detected.
) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
Package: ifxetex 2010/09/12 v0.6 Provides ifxetex conditional
) (/usr/share/texlive/texmf-dist/tex/luatex/luatexbase/luatexbase.sty
Package: luatexbase 2015/10/04 v1.3 luatexbase interface to LuaTeX 
(/usr/share/texlive/texmf-dist/tex/luatex/ctablestack/ctablestack.sty
Package: ctablestack 2015/10/01 v1.0 Catcode table stable support
\@catcodetablestackcnt=\count87
)
\CatcodeTableOther=\catcodetable5
\CatcodeTableExpl=\catcodetable6
)
Lua module: luainputenc 2010/05/10 0.97 Lua simple inputenc package.
\inpenc@prehook=\toks15
\inpenc@posthook=\toks16
Inserting `luainputenc.fake_utf_write' at position 1 in `process_output_buffer'.
Inserting `luainputenc.fake_utf_read' at position 1 in `process_input_buffer'. 
(/usr/share/texlive/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2015/03/17 v1.2c Input encoding file
)) (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
Package: color 2016/07/10 v1.1e Standard LaTeX Color (DPC)
(/usr/local/share/texmf/tex/latex/graphics/color.cfg
File: color.cfg 2007/01/18 v1.5 color configuration of teTeX/TeXLive
)
Package color Info: Driver file: dvips.def on input line 147.
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def
File: dvips.def 2016/07/10 v3.1a Driver-dependent file (DPC,SPQR)
) (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def
File: dvipsnam.def 2016/06/17 v3.0m Driver-dependent file (DPC,SPQR)
)) (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
Package: babel 2016/04/23 3.9r The Babel package
(/usr/share/texlive/texmf-dist/tex/generic/babel/luababel.def
\l@dumylang=\language1
\l@nohyphenation=\language2
\l@spanish=\language3
\l@romansh=\language4
\l@czech=\language5
\l@friulan=\language6
\l@finnish=\language7
\l@basque=\language8
\l@galician=\language9
\l@nynorsk=\language10
\l@swedish=\language11
\l@welsh=\language12
\l@polish=\language13
\l@usenglishmax=\language14

Re: [LyX/master] Fix data loss with [ in first cell of aligned

[Richard Heck]

On 09/10/2016 04:22 AM, Georg Baum wrote:
> Richard, OK for branch?

Yes, thank you.

rh

>
> Georg
>
>
> Georg Baum wrote:
>
>> commit a6be519a815893765a257bec5a456d7f6eecf8f6
>> Author: Georg Baum 
>> Date:   Thu Sep 8 22:38:33 2016 +0200
>>
>> Fix data loss with [ in first cell of aligned
>> 
>> If the first character in the first cell of an aligned math
>> environment is '[', and the environment does not use top or bottom
>> vertical alignment, then LyX did write the '[' unprotected so that it
>> got misinterpreted as optional argument, both when reading the .lyx
>> file in LyX and when reading the .tex file in LaTeX => data loss!
>> The fix is to output an empty optional argument in this case, which is
>> interpreted as default alignment both by LyX and LaTeX. It would also
>> be possible to output \[ in the first cell instead, but this would be
>> more difficult to implement.
>> ---
>>  src/mathed/InsetMathSplit.cpp |   18 ++
>>  1 files changed, 14 insertions(+), 4 deletions(-)
>>
>> diff --git a/src/mathed/InsetMathSplit.cpp b/src/mathed/InsetMathSplit.cpp
>> index 515dcb0..e385e0a 100644
>> --- a/src/mathed/InsetMathSplit.cpp
>> +++ b/src/mathed/InsetMathSplit.cpp
>> @@ -14,7 +14,7 @@
>>  
>>  #include "MathData.h"
>>  #include "MathStream.h"
>> -#include "MathStream.h"
>> +#include "MathSupport.h"
>>  
>>  #include "FuncRequest.h"
>>  #include "FuncStatus.h"
>> @@ -141,9 +141,19 @@ void InsetMathSplit::write(WriteStream & ws) const
>>  suffix = from_ascii("*");
>>  ws << "\\begin{" << name_ << suffix << '}';
>>  bool open = ws.startOuterRow();
>> -if (name_ != "split" && name_ != "align" && verticalAlignment() != 
> 'c')
>> -ws << '[' << verticalAlignment() << ']';
>> -if (name_ == "alignedat")
>> +bool const hasArg(name_ == "alignedat");
>> +if (name_ != "split" && name_ != "align") {
>> +if (verticalAlignment() != 'c')
>> +ws << '[' << verticalAlignment() << ']';
>> +else if (!hasArg) {
>> +docstring const first(asString(cell(0)));
>> +// prevent misinterpretation of the first 
> character of
>> +// the first cell as optional argument (bug 
> 10361)
>> +if (!first.empty() && first[0] == '[')
>> +ws << "[]";
>> +}
>> +}
>> +if (hasArg)
>>  ws << '{' << static_cast((ncols() + 1)/2) << '}';
>>  InsetMathGrid::write(ws);
>>  if (ws.fragile())
>

Re: GUI changes for inserting citations in 2.2x

[Charles de Miramon]

Maria Gouskova wrote:

> Hi developers,
> 
> I just upgraded to 2.2.1 today. I can see that there have been a lot of
> changes in the appearance of the interface, so obviously quite a lot of
> work went into the redesign. I confess I was stumped, though, when I went
> to insert a citation. The "Search" and "Formatting" options are hidden,
> and it's done in such a way that if I didn't know that they were there, it
> would not occur to me that those areas of the window were clickable. So I
> was wondering what the motivation was for the change--I can see that it's
> a "cleaner" look, but I think it really hampers the usability of the GUI,
> especially for new users.
> 

I agree with Maria that the new dialog is a usability regression.

If there is a redesign of the dialog, could it be posible to put the search 
field on the top ?

My workflow to insert a citation is :

1) type the name of the author or some word of the title. My main 
bibliography file has around 1900 entries and grows slowly. 
2) select the exact reference in the list
3) add a page number
4) insert

Having the search field on top and the results below is what is intuitive 
today after years of Google use.

I think kbibtex has a rather nice search field that take little vertical 
space and hides seldom used search options behind a button.


If you have search-as-you-type, I'm wondering who needs search with regular 
expressions. I'm certainly not a real geek !

Cheers,
Charles

Re: [RFC][PATCH] Set window title according to platform UI

[Guillaume Munch]

Le 08/09/2016 à 22:27, Enrico Forestieri a écrit :

On Thu, Sep 08, 2016 at 03:04:17PM +0200, Jean-Marc Lasgouttes wrote:


Le 08/09/2016 à 03:31, Enrico Forestieri a écrit :

On Wed, Sep 07, 2016 at 03:13:38PM +0200, Jean-Marc Lasgouttes wrote:


And of course, a screenshot (no you are not entitled to complain about the
huge readonly icon, only to help me fix it).


Fixed in the attached.


Thanks a lot, but let me say: Ouch!


The following is needed for having a resonable size.

>
> …


It is complicated because we want the best quality, otherwise the code
in the else branch above would work equally... bad, because the image
would be rendered at an higher size and then the bitmap scaled down
(with awful results).



Getting the perfect result is a good reason for having such a
long code. Maybe the "ouch!" effect is because it is added as is.
It looks like it could be made a function in qt_helpers or some other
appropriate place, doesn't it? For better maintainability and
re-use.

Re: fix math toolbars

[Guillaume Munch]

Le 10/09/2016 à 17:29, Enrico Forestieri a écrit :

On Fri, Sep 09, 2016 at 12:04:47PM +0200, Enrico Forestieri wrote:


Tell me how much time you think it will take you. One month?
Two months? Three months? I'll wait for that time.


No response and no other nay. So, I am going ahead.



Hi Enrico,

I think I like the idea of the patch, but also I have the feeling that
this is the sort of change that will require time for appreciating all
its consequences.

But, when you call for the opinions of other people on the list, I think
one day is too short a delay. Maybe waiting one week would have been better.

Also, I tried the patch in current master, and it crashed. Bisect points
to 2aa930bbe. See below for a trace.

Guillaume



Thread 1 "lyx" received signal SIGSEGV, Segmentation fault.
0x00cdc174 in lyx::operator== (l=..., r=r@entry=0xd96a12 "textmode")
at ../../../src/support/docstring.cpp:181
181 if (*it != static_cast(*r))
(gdb) bt
#0  0x00cdc174 in lyx::operator== (l=..., r=r@entry=0xd96a12 
"textmode")

at ../../../src/support/docstring.cpp:181
#1  0x0085ae5b in lyx::MathMacro::write (this=0x2c31580, os=...)
at ../../src/mathed/MathMacro.cpp:933
#2  0x00846820 in lyx::write (dat=..., wi=...)
at ../../src/mathed/MathExtern.cpp:1407
#3  0x00885775 in lyx::operator<< (ws=..., ar=...)
at ../../src/mathed/MathStream.cpp:206
#4  0x0082db9f in lyx::InsetMathScript::write (this=0x2c313f0, 
os=...)

at ../../src/mathed/InsetMathScript.cpp:508
#5  0x00846820 in lyx::write (dat=..., wi=...)
at ../../src/mathed/MathExtern.cpp:1407
#6  0x00885775 in lyx::operator<< (ws=..., ar=...)
at ../../src/mathed/MathStream.cpp:206
#7  0x008aa7fa in lyx::InsetMathGrid::write 
(this=this@entry=0x2c358f0,

os=..., beg_row=beg_row@entry=0, beg_col=beg_col@entry=0,
end_row=, end_col=end_col@entry=4)
at ../../src/mathed/InsetMathGrid.cpp:1310
#8  0x008aacb1 in lyx::InsetMathGrid::write 
(this=this@entry=0x2c358f0,

os=...) at ../../src/mathed/InsetMathGrid.cpp:1263
#9  0x008d020b in lyx::InsetMathXYMatrix::write (this=0x2c358f0, 
os=...)

at ../../src/mathed/InsetMathXYMatrix.cpp:88
#10 0x00846820 in lyx::write (dat=..., wi=...)
at ../../src/mathed/MathExtern.cpp:1407
#11 0x00885775 in lyx::operator<< (ws=..., ar=...)
at ../../src/mathed/MathStream.cpp:206
#12 0x00807012 in lyx::InsetMathHull::plaintext (this=0x2c2d960,
os=..., op=..., max_length=)
at ../../src/mathed/InsetMathHull.cpp:2236
#13 0x00805670 in lyx::InsetMathHull::forOutliner (this=0x2c2d960,
os=L"") at ../../src/mathed/InsetMathHull.cpp:2570
#14 0x006a88de in lyx::Paragraph::forOutliner (this=0x2c2c630, 
os=L"",

maxlen=maxlen@entry=121, shorten=shorten@entry=false)
at ../../src/Paragraph.cpp:3295
#15 0x006f0f7a in lyx::Text::forOutliner 
(this=this@entry=0x2c32af8,

os=L"", maxlen=maxlen@entry=120, shorten=shorten@entry=true)
at ../../src/Text.cpp:2054
#16 0x009a9758 in lyx::InsetNote::addToToc (this=0x2c32ae0, 
cpit=...,

output_active=, utype=lyx::InternalUpdate)
at ../../src/insets/InsetNote.cpp:219
#17 0x009ff880 in lyx::InsetText::iterateForToc (
this=this@entry=0x27228e0, cdit=...,
output_active=output_active@entry=true,
utype=utype@entry=lyx::InternalUpdate) at 
../../src/insets/InsetText.cpp:869
#18 0x009ffe69 in lyx::InsetText::addToToc (this=0x27228e0, 
cdit=...,

output_active=, utype=lyx::InternalUpdate)
at ../../src/insets/InsetText.cpp:837
#19 0x0074ba8d in lyx::TocBackend::update (this=0x2554640,
output_active=output_active@entry=true,
utype=utype@entry=lyx::InternalUpdate) at ../../src/TocBackend.cpp:303
#20 0x004f085b in lyx::Buffer::updateBuffer (this=0x231fce0,
scope=scope@entry=lyx::Buffer::UpdateMaster,
utype=utype@entry=lyx::InternalUpdate) at ../../src/Buffer.cpp:4609

Re: [LyX/master] Set window title according to platform UI

[Guillaume Munch]

Le 08/09/2016 à 14:59, Jean-Marc Lasgouttes a écrit :

commit 82808fea04315fd323ec074e8ad7865d190987d4
Author: Jean-Marc Lasgouttes 
Date:   Tue Sep 6 11:17:10 2016 +0200

Set window title according to platform UI

+   // Tell Qt whether the current document is changed
+   setWindowModified(!buf.isClean());



LyX produces the following message on the console in current master:

QWidget::setWindowModified: The window title does not contain a '[*]'
placeholder

Re: GUI changes for inserting citations in 2.2x

[Jürgen Spitzmüller]

Am Samstag, den 10.09.2016, 14:47 +0200 schrieb Charles de Miramon:
> I agree with Maria that the new dialog is a usability regression.
> 
> If there is a redesign of the dialog, could it be posible to put the
> search 
> field on the top ?
> 
> My workflow to insert a citation is :
> 
> 1) type the name of the author or some word of the title. My main 
> bibliography file has around 1900 entries and grows slowly. 
> 2) select the exact reference in the list
> 3) add a page number
> 4) insert
> 
> Having the search field on top and the results below is what is
> intuitive 
> today after years of Google use.
> 
> I think kbibtex has a rather nice search field that take little
> vertical 
> space and hides seldom used search options behind a button.

Note that the screen shot does not show the current version. KBibTeX
0.6 uses two combo boxes, mainly because a menu is unusable with the
many biblatex fields (see attached screenshot). Also note that we have
more widgets, so we cannot put everything into one row. 

Moving it to the top would be trivial, but still we need to show/hide
the search options.

> If you have search-as-you-type, I'm wondering who needs search with
> regular 
> expressions. 

These two are orthogonal.

Jürgen

> I'm certainly not a real geek !
> 
> Cheers,
> Charles

signature.asc
Description: This is a digitally signed message part

Re: fix math toolbars

[Enrico Forestieri]

On Fri, Sep 09, 2016 at 12:04:47PM +0200, Enrico Forestieri wrote:
> 
> Tell me how much time you think it will take you. One month?
> Two months? Three months? I'll wait for that time.

No response and no other nay. So, I am going ahead.

-- 
Enrico