Re: [LyX/master] Strike out (in the output) deleted display math with track-changes

[Scott Kostyshak]

On Sun, Oct 16, 2016 at 11:27:02PM -0400, Scott Kostyshak wrote:

> A second question is: Is the diagonal line supposed to be so large?
> Screenshot attached.

Oops, now screenshot attached.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Strike out (in the output) deleted display math with track-changes

[Scott Kostyshak]

On Mon, Oct 17, 2016 at 04:00:25AM +0200, Enrico Forestieri wrote:
> commit 261e7ae9ce7e6a1ffc4932ff9c33107588a9a4ac
> Author: Enrico Forestieri 
> Date:   Mon Oct 17 03:25:35 2016 +0200
> 
> Strike out (in the output) deleted display math with track-changes

Nice!

Did this commit fix #9678?

I tested it out and have a couple of questions. Attached is a file. If I
compile I get an error ("there's no line to end here"). If I put the
cursor at the end of "hello" and press (forward) delete to remove the
newline (nothing changes on the screen) and then compile, there is no
error.

A second question is: Is the diagonal line supposed to be so large?
Screenshot attached.

Scott
#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 513
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\use_microtype false
\graphics default
\default_output_format default
\output_sync 1
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes true
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\author 274215730 "scott"
\end_header

\begin_body

\begin_layout Standard
hello
\end_layout

\begin_layout Standard

\change_deleted 274215730 1476673996
\begin_inset Formula 
\[
x+y
\]

\end_inset


\change_unchanged
testing now
\end_layout

\end_body
\end_document


signature.asc
Description: PGP signature

Re: [patch] Increase precision of TexRow in captions

[Pavel Sanda]

Guillaume Munch wrote:
> Dear list,
>
> The attached patches add safe line breaks ("%\n") to the output, to
> crucially increase the precision of forward/reverse-search and error
> reporting of captions. This is especially useful as these captions
> introduce a discontinuity in the TexRow. The change is trivial but since
> this modifies the LaTeX output I prefer to ask for any objection.

How ugly (in terms of chunked text) the LaTeX code becomes now for people who
actually use LaTeX source after the export?

Pavel

Re: #6563: Change tracking and moving labels

[UD]

  
  
To do that I shall have to install 2.2.2, which I cannot do at the
moment. I shall follow up once I manage to install the latest
version.
Yours,
Ehud Kaplan

On 10/15/2016 06:29 PM, LyX Ticket
  Tracker wrote:


  #6563: Change tracking and moving labels
-+
 Reporter:  venik|   Owner:  vfr
 Type:  defect   |  Status:  new
 Priority:  high |   Milestone:  2.2.3
Component:  changes  | Version:  1.6.5
 Severity:  normal   |  Resolution:
 Keywords:  patch|
-+
Changes (by rgheck):

 * milestone:  2.2.2 => 2.2.3


Comment:

 LyX 2.2.2 is released. Please check whether this bug should remain
 targeted to 2.2.3. If not, please retarget.




-- 
Ehud Kaplan, Ph.D.
Jules and Doris Stein Research to Prevent Blindness Professor
Director, Center of Excellence for Computational & System neuroscience,
The Friedman Brain Institute, ISMMS
Director, The laboratory of Visual & Computational Neuroscience
Depts. of Neuroscience, Ophthalmology, Chemical & Structural Biology
The Icahn School of Medicine at Mount Sinai
One Gustave Levy Place
New York, NY, 10029
USA
  

new compiler warnings in today's master

[Uwe Stöhr]

Hi Guillaume,

your recent changes introduced these new compiler warning:

GuiViewSource.cpp
D:\LyXGit\Master\src\TexRow.h(51): warning C4099: 'lyx::TextEntry': type 
name first seen using 'class' now seen using 'struct' (compiling source 
file D:\LyXGit\Master\src\frontends\qt4\GuiView.cpp) 
[D:\LyXGit\Master\compile-2015\src\frontends\qt4\frontend_qt.vcxproj]
  D:\LyXGit\Master\src\TexRow.h(51): note: see declaration of 
'lyx::TextEntry' (compiling source file 
D:\LyXGit\Master\src\frontends\qt4\GuiView.cpp)
D:\LyXGit\Master\src\TexRow.h(51): warning C4099: 'lyx::TextEntry': type 
name first seen using 'class' now seen using 'struct' (compiling source 
file D:\LyXGit\Master\src\frontends\qt4\GuiViewSource.cpp) 
[D:\LyXGit\Master\compile-2015\src\frontends\qt4\frontend_qt.vcxproj]
  D:\LyXGit\Master\src\TexRow.h(51): note: see declaration of 
'lyx::TextEntry' (compiling source file 
D:\LyXGit\Master\src\frontends\qt4\GuiViewSource.cpp)


PreviewLoader.cpp
D:\LyXGit\Master\src\TexRow.h(222): warning C4099: 'lyx::TexString': 
type namefirst seen using 'class' now seen using 'struct' (compiling 
source file D:\LyXGit\Master\src\graphics\PreviewLoader.cpp) 
[D:\LyXGit\Master\compile-2015\src\graphics\graphics.vcxproj]
  D:\LyXGit\Master\src\TexRow.h(222): note: see declaration of 
'lyx::TexString' (compiling source file 
D:\LyXGit\Master\src\graphics\PreviewLoader.cpp)
D:\LyXGit\Master\src\texstream.h(21): warning C4099: 'lyx::TexString': 
type name first seen using 'struct' now seen using 'class' (compiling 
source file D:\LyXGit\Master\src\graphics\PreviewLoader.cpp) 
[D:\LyXGit\Master\compile-2015\src\graphics\graphics.vcxproj]


I get these 2 warnings a dozen times. Could you please have a look?

thanks and regards
Uwe

recent commits

[Guillaume Munch]

I had some comments on the series of commits that I just pushed but this
will have to wait since the messages on lyx-cvs (and lyx-devel) take
ages to arrive. (Is gmane down in celebration of LyX 2.2.2?)

They are various minor improvements to TexRow in general and reverse
search in particular but miss a punchline, because I had to hold back a
few additional commits (until I find a way to fix a long standing bug of
GuiErrorList to enable proper testing).

Some inset offset fine tuning

[racoon]

I just tried to do some fine tuning on the inset offsets (minimalistic 
and classic so far).


1. I have decoupled the outer and inner offset at the beginning and at 
the end of the inset.


2. I have changed the outer offset to 1px.

I like the smaller spaces better. Now they cannot be mistaken for spaces 
anymore even with small font-sizes.


Though I have a non-high resolution display. Maybe it does not look as 
good on a high-res display. If so, maybe there should be an adjustment 
for high-res displays?


Daniel
From 93f644687e9d5fc161b24eb89dc35e1095278633 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ram=C3=B6ller?= 
Date: Mon, 17 Oct 2016 01:21:01 +0200
Subject: [PATCH] Some inset offset fine tuning: - Make outer inset offset
 independent of inner. - Reduced the outer offset.

---
 src/frontends/qt4/GuiFontMetrics.cpp |  4 ++--
 src/frontends/qt4/GuiPainter.cpp |  6 +++---
 src/insets/Inset.h   |  6 +-
 src/insets/InsetText.cpp | 13 -
 4 files changed, 18 insertions(+), 11 deletions(-)

diff --git a/src/frontends/qt4/GuiFontMetrics.cpp 
b/src/frontends/qt4/GuiFontMetrics.cpp
index eade8cc..29f8f3b 100644
--- a/src/frontends/qt4/GuiFontMetrics.cpp
+++ b/src/frontends/qt4/GuiFontMetrics.cpp
@@ -254,7 +254,7 @@ void GuiFontMetrics::rectText(docstring const & str,
 {
static int const d = Inset::TEXT_TO_INSET_OFFSET / 2;
 
-   w = width(str) + Inset::TEXT_TO_INSET_OFFSET;
+   w = width(str) + Inset::TEXT_TO_INSET_OFFSET_INSIDE + 
Inset::TEXT_TO_INSET_OFFSET_INSIDE;
ascent = metrics_.ascent() + d;
descent = metrics_.descent() + d;
 }
@@ -265,7 +265,7 @@ void GuiFontMetrics::buttonText(docstring const & str,
int & w, int & ascent, int & descent) const
 {
rectText(str, w, ascent, descent);
-   w += Inset::TEXT_TO_INSET_OFFSET;
+   w += Inset::TEXT_TO_INSET_OFFSET_INSIDE;
 }
 
 
diff --git a/src/frontends/qt4/GuiPainter.cpp b/src/frontends/qt4/GuiPainter.cpp
index e613f3f..23d4e73 100644
--- a/src/frontends/qt4/GuiPainter.cpp
+++ b/src/frontends/qt4/GuiPainter.cpp
@@ -593,10 +593,10 @@ void GuiPainter::buttonText(int x, int y, docstring const 
& str,
FontMetrics const & fm = theFontMetrics(font);
fm.buttonText(str, width, ascent, descent);
 
-   static int const d = Inset::TEXT_TO_INSET_OFFSET / 2;
+   static int const d = Inset::TEXT_TO_INSET_OFFSET_OUTSIDE;
 
-   button(x + d, y - ascent, width - Inset::TEXT_TO_INSET_OFFSET, descent 
+ ascent, mouseHover);
-   text(x + Inset::TEXT_TO_INSET_OFFSET, y, str, font);
+   button(x + d, y - ascent, width - Inset::TEXT_TO_INSET_OFFSET_OUTSIDE, 
descent + ascent, mouseHover);
+   text(x + Inset::TEXT_TO_INSET_OFFSET_OUTSIDE + 
Inset::TEXT_TO_INSET_OFFSET_INSIDE, y, str, font);
 }
 
 
diff --git a/src/insets/Inset.h b/src/insets/Inset.h
index 48ad7be..34ba4e9 100644
--- a/src/insets/Inset.h
+++ b/src/insets/Inset.h
@@ -574,7 +574,11 @@ public:
///
virtual ColorCode labelColor() const;
//
-   enum { TEXT_TO_INSET_OFFSET = 4 };
+   enum {
+   TEXT_TO_INSET_OFFSET = 4,
+   TEXT_TO_INSET_OFFSET_INSIDE = 2,
+   TEXT_TO_INSET_OFFSET_OUTSIDE = 1
+   };
 
 protected:
/// Constructors
diff --git a/src/insets/InsetText.cpp b/src/insets/InsetText.cpp
index df4f6e2..e30d07a 100644
--- a/src/insets/InsetText.cpp
+++ b/src/insets/InsetText.cpp
@@ -208,7 +208,8 @@ void InsetText::metrics(MetricsInfo & mi, Dimension & dim) 
const
mi.base.textwidth += 2 * TEXT_TO_INSET_OFFSET;
dim.asc += TEXT_TO_INSET_OFFSET;
dim.des += TEXT_TO_INSET_OFFSET;
-   dim.wid += 2 * TEXT_TO_INSET_OFFSET;
+   // cursor position after inset
+   dim.wid += 2 * (TEXT_TO_INSET_OFFSET_INSIDE + 
TEXT_TO_INSET_OFFSET_OUTSIDE);
 }
 
 
@@ -216,10 +217,10 @@ void InsetText::draw(PainterInfo & pi, int x, int y) const
 {
TextMetrics & tm = pi.base.bv->textMetrics(_);
 
-   int const w = tm.width() + TEXT_TO_INSET_OFFSET;
+   int const w = tm.width() + 2 * TEXT_TO_INSET_OFFSET_INSIDE;
int const yframe = y - TEXT_TO_INSET_OFFSET - tm.ascent();
int const h = tm.height() + 2 * TEXT_TO_INSET_OFFSET;
-   int const xframe = x + TEXT_TO_INSET_OFFSET / 2;
+   int const xframe = x + TEXT_TO_INSET_OFFSET_OUTSIDE;
bool change_drawn = false;
if (drawFrame_ || pi.full_repaint) {
if (pi.full_repaint)
@@ -251,7 +252,8 @@ void InsetText::draw(PainterInfo & pi, int x, int y) const
pi.backgroundColor(this, false));
// The change tracking cue must not be inherited
Changer dummy2 = make_change(pi.change_, Change());
-   tm.draw(pi, x + TEXT_TO_INSET_OFFSET, y);
+   // text position within inset
+   tm.draw(pi, x + TEXT_TO_INSET_OFFSET_INSIDE + 
TEXT_TO_INSET_OFFSET_OUTSIDE, y);
  

[patch] Increase precision of TexRow in captions

[Guillaume Munch]

Dear list,

The attached patches add safe line breaks ("%\n") to the output, to
crucially increase the precision of forward/reverse-search and error
reporting of captions. This is especially useful as these captions
introduce a discontinuity in the TexRow. The change is trivial but since
this modifies the LaTeX output I prefer to ask for any objection.

I also tried once again to read section "4.3 ctest automatic tests" of
the developer's manual and I am still at a loss to understand what the
tests do or to know how to run just the ones that are relevant to these
two patches. I am ready to adjust the test afterwards if there are
reports of tests needing such adjustment.

Sincerely,
Guillaume
>From f97a870a2f77229876e12d77bf727505ae42aa84 Mon Sep 17 00:00:00 2001
From: Guillaume Munch 
Date: Mon, 10 Oct 2016 16:52:32 +0200
Subject: [PATCH 1/2] Safe line break to increase precision of error reporting
 in Listings caption

---
 src/insets/InsetListings.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/insets/InsetListings.cpp b/src/insets/InsetListings.cpp
index 8211ba3..62250fe 100644
--- a/src/insets/InsetListings.cpp
+++ b/src/insets/InsetListings.cpp
@@ -227,7 +227,7 @@ void InsetListings::latex(otexstream & os, OutputParams const & runparams) const
 		if (param_string.empty() && caption.str.empty())
 			os << breakln << "\\begin{lstlisting}\n";
 		else {
-			os << breakln << "\\begin{lstlisting}[";
+			os << breakln << "\\begin{lstlisting}" << safebreakln << "[";
 			if (!caption.str.empty()) {
 os << "caption={" << move(caption) << '}';
 if (!param_string.empty())
-- 
2.7.4

>From 4e82c33d8c6bc35e47dfea0bfced9656a1dc9d39 Mon Sep 17 00:00:00 2001
From: Guillaume Munch 
Date: Mon, 10 Oct 2016 17:14:39 +0200
Subject: [PATCH 2/2] Add safe line breaks to improve TexRow precision in
 subfloat & caption

---
 src/insets/InsetFloat.cpp | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/insets/InsetFloat.cpp b/src/insets/InsetFloat.cpp
index 1030b45..e974ff4 100644
--- a/src/insets/InsetFloat.cpp
+++ b/src/insets/InsetFloat.cpp
@@ -324,6 +324,10 @@ docstring InsetFloat::xhtml(XHTMLStream & xs, OutputParams const & rp) const
 void InsetFloat::latex(otexstream & os, OutputParams const & runparams_in) const
 {
 	if (runparams_in.inFloat != OutputParams::NONFLOAT) {
+		if (!paragraphs().empty())
+			// improve TexRow precision
+			os << safebreakln;
+
 		if (runparams_in.moving_arg)
 			os << "\\protect";
 		os << "\\subfloat";
@@ -333,8 +337,6 @@ void InsetFloat::latex(otexstream & os, OutputParams const & runparams_in) const
 		os << getCaption(rp);
 		os << '{';
 		// The main argument is the contents of the float. This is not a moving argument.
-		if (!paragraphs().empty())
-			os.texrow().forceStart(paragraphs()[0].id(), 0);
 		rp.moving_arg = false;
 		rp.inFloat = OutputParams::SUBFLOAT;
 		InsetText::latex(os, rp);
@@ -503,7 +505,7 @@ TexString InsetFloat::getCaption(OutputParams const & runparams) const
 	otexstringstream os;
 	ins->getArgs(os, runparams);
 
-	os << '[';
+	os << safebreakln << '[';
 	otexstringstream os2;
 	ins->getArgument(os2, runparams);
 	TexString ts = os2.release();
@@ -512,7 +514,7 @@ TexString InsetFloat::getCaption(OutputParams const & runparams) const
 	if (arg.find(']') != docstring::npos)
 		arg = '{' + arg + '}';
 	os << move(ts);
-	os << ']';
+	os << ']' << safebreakln;
 	return os.release();
 }
 
-- 
2.7.4

Re: Mysterious crash

[Guillaume Munch]

Le 29/09/2016 à 18:41, Enrico Forestieri a écrit :

On Thu, Sep 29, 2016 at 12:52:02PM +0200, Guillaume Munch wrote:


Thanks for the backtrace. The problem is that the variable BufferView *
bv_ in ViewSourceWidget is a borrowed pointer with unclear lifetime,
i.e. it will dangle. I have decided to get rid of it entirely, but this
requires a few changes to the Dialog architecture and takes some time to
implement (hopefully with bigger benefits). So I pushed a quick fix in
the meantime.


I had arrived to the same conclusion and was pushing the (perhaps simpler)
attached patch, but you beated me ;)



At e0e765f6a98 there is now a proper fix getting rid of the non-sensical
BufferView pointer and simplifying the design a bit. The only reason why
the pointer could not be removed straight away is that it was involved
in a pointer comparison to check whether the bufferview had changed. I
basically moved the control of the widget to the dialog, which knows the
proper pointer.

There is now a virtual function Dialog::on_bufferViewChanged that is
called when the BufferView changes and only then. There were simpler
solutions, but the new signal also helps with some code factoring and
will certainly be useful in the future.

Guillaume

Re: master linking errors

[Kornel Benko]

Am Sonntag, 16. Oktober 2016 um 17:05:03, schrieb Jürgen Spitzmüller 

> Am Sonntag, den 16.10.2016, 16:55 +0200 schrieb Kornel Benko:
> > OK. Have you enabled std:regex? 
> 
> Yes.
> 
> > If yes, you could try to find
> > bold 'foo' from the home position, while setting 'don't ignore
> > format' in adv search settings?
> > 
> > Expected: the first 'foo', but with std:regex the second 'foo' is
> > selected.
> 
> Correct. That's what I get.
> 
> Jürgen
> 

So we have 2 alternatives
1.) use boost:regex
2.) adapt the adv-find  regexes to std:regex

'2' is the correct way, but '1' is easy to realise.

Kornel



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

Re: master linking errors

[Jürgen Spitzmüller]

Am Sonntag, den 16.10.2016, 16:55 +0200 schrieb Kornel Benko:
> OK. Have you enabled std:regex? 

Yes.

> If yes, you could try to find
> bold 'foo' from the home position, while setting 'don't ignore
> format' in adv search settings?
> 
> Expected: the first 'foo', but with std:regex the second 'foo' is
> selected.

Correct. That's what I get.

Jürgen

> 
>   Kornel

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

Re: #9568: Multicolumn, fixed width, and decimal-separator-alignment does not compile

[Jürgen Spitzmüller]

Am Sonntag, den 16.10.2016, 16:41 +0200 schrieb Sven Schreiber:
> OK, you asked for it...
> The attached Latex file uses the "siunitx" package (which I've never 
> used before) to achieve flexibility with respect to the 
> within-cell-alignment of the decimal-aligned multicolumns.
> (If the attachment doesn't make it through this channel please tell
> me.)
> 
> In the attached version you find the line "table-number-alignment = 
> center," -- you can substitute "left" or "right" there, and it
> yields 
> the intended effect for me, namely the whole block of what's in the 
> three multicolumn rows wanders to the left or to the right, while 
> staying aligned at the decimal dot.

Thank you. I am aware of this package, but it has some disadvantages
for our purpose:

1. The whole siunitx machinery has to be started, which results in
unwanted formatting of numbers.

2. For proper results, one has to tell siunitx the maximum number of
numbers before and after the decimal separator, and it is hard to
calculate that from within LyX (this is also the reason why we use our
own approach instead of the dcolumn package). 

BTW, the "{c}" part after the three "\multicolumn{2}" thingies is 
> mysterious to me, changing that to "{l}" or "{r}" didn't seem to
> have 
> any effect.

It does not have any effect here, since sinuitx overrides it.

Jürgen

> 
> HTH,
> Sven
> 

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

Re: master linking errors

[Kornel Benko]

Am Sonntag, 16. Oktober 2016 um 16:13:20, schrieb Jürgen Spitzmüller 

> Am Sonntag, den 16.10.2016, 15:02 +0200 schrieb Kornel Benko:
> > It took ages to compile gcc6.2.0 ...
> > The test with this compiler (+cmake  and again without  '-std=c++14')
> > does compile and link everything.
> > Could you give cmake a chance?
>
> I tried again with a clean build and now succeeded. The problem
> probably was that make distclean is broken (as Richard already
> reported), and I did not notice that on my first attempt.
>
> Sorry for the hassle.
>
> Jürgen
>
> >

OK. Have you enabled std:regex? If yes, you could try to find
bold 'foo' from the home position, while setting 'don't ignore format' in adv 
search settings?

Expected: the first 'foo', but with std:regex the second 'foo' is selected.

Kornel

test.lyx
Description: application/lyx


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

Re: #9568: Multicolumn, fixed width, and decimal-separator-alignment does not compile

[Sven Schreiber]

Am 16.10.2016 um 14:18 schrieb LyX Ticket Tracker:

#9568: Multicolumn, fixed width, and decimal-separator-alignment does not 
compile



 If you show us how to do it in LaTeX, we can implement it in LyX.


OK, you asked for it...
The attached Latex file uses the "siunitx" package (which I've never 
used before) to achieve flexibility with respect to the 
within-cell-alignment of the decimal-aligned multicolumns.

(If the attachment doesn't make it through this channel please tell me.)

In the attached version you find the line "table-number-alignment = 
center," -- you can substitute "left" or "right" there, and it yields 
the intended effect for me, namely the whole block of what's in the 
three multicolumn rows wanders to the left or to the right, while 
staying aligned at the decimal dot.


BTW, the "{c}" part after the three "\multicolumn{2}" thingies is 
mysterious to me, changing that to "{l}" or "{r}" didn't seem to have 
any effect.


HTH,
Sven
\documentclass{article}

\usepackage{siunitx}
\usepackage{booktabs}

\begin{document}

\begin{table}
\caption{Controlling complex alignment with the {tablenum}
macro.}

\label{tab:tablenum}

\sisetup{
table-number-alignment = center,
table-figures-integer = 4,
table-figures-decimal = 4
}

\centering
\begin{tabular}{lr}
\toprule
Heading & Heading \\
\midrule
Info & More info \\
Info & More info \\
\multicolumn{2}{c}{\tablenum{12,34}} \\
\multicolumn{2}{c}{\tablenum{333.5567}} \\
\multicolumn{2}{c}{\tablenum{4563.21}} \\
\bottomrule
\end{tabular}
\hfil
\end{table}

\end{document}

Re: Bug in 2.2.2 for Mac

[Christopher Menzel]

Everything appears to be back to normal! Thanks!

-chris

On 16 Oct 2016, at 8:13 AM, Stephan Witt  wrote:
> Am 16.10.2016 um 00:43 schrieb Christopher Menzel  >:
>> 
>> Sorry, I should have been clearer about that. The submenus are rendered 
>> inaccessible. Also, Open Recent is greyed out. But other stuff, like my user 
>> defined key bindings still work.
>> 
>> -chris
>> 
>> On Oct 15, 2016, at 6:19 PM, Richard Heck  wrote:
>> 
>>> On 10/15/2016 04:38 PM, Christopher Menzel wrote:
>>> 
 
 On 15 Oct 2016, at 4:31 PM, Christopher Menzel  
 wrote:
> 
> Howdy LyX developers,
> 
> There appears to be a bug in 2.2.2 for Mac (LyX-2.2.2+qt5-x86_64-cocoa). 
> The triangles in the top-level dropdown menus that lead to submenus all 
> appear to be missing. See attached screenshot.
>>> 
>>> Are the menus themselves accessible? Or does the lack of triangles cause 
>>> them to be inaccessible?
> 
> I did a new build with Qt 5.6.2 and made a disk image with it and put it here:
> 
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.2%2Bqt5.6.2-x86_64-cocoa.dmg
>  
> 
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.2%2Bqt5.6.2-x86_64-cocoa.dmg.sig
>  
> 
> 
> Sorry, I did my tests with shortcuts only and didn’t notice the broken menu.
> And I’m not sure what caused the problem - I’ll investigate it later.
> 
> Now it works for me. Christopher, please try this build and tell us how it 
> works
> for you, thanks.
> 
> Regards,
> Stephan

Re: master linking errors

[Jürgen Spitzmüller]

Am Sonntag, den 16.10.2016, 15:02 +0200 schrieb Kornel Benko:
> It took ages to compile gcc6.2.0 ...
> The test with this compiler (+cmake  and again without  '-std=c++14') 
> does compile and link everything.
> Could you give cmake a chance?

I tried again with a clean build and now succeeded. The problem
probably was that make distclean is broken (as Richard already
reported), and I did not notice that on my first attempt.

Sorry for the hassle.

Jürgen

> 
>   Kornel

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

Re: [patch] support for Piedmontese

[Uwe Stöhr]

Am 16.10.2016 um 12:16 schrieb Jürgen Spitzmüller:


The patch looks good.


Thanks for having a look. The patch is in.

I could not update the tex2lyx tet files because of bug
http://www.lyx.org/trac/ticket/10440

regards Uwe

Re: master linking errors

[Kornel Benko]

Am Sonntag, 16. Oktober 2016 um 13:13:38, schrieb Jürgen Spitzmüller 

> Am Sonntag, den 16.10.2016, 04:08 -0700 schrieb Kornel Benko:
> > Am Sonntag, 16. Oktober 2016 um 12:46:28, schrieb Jürgen Spitzmüller
> > 
> > > As of today (probably related to a system update),
> > 
> > 
> > This means probably also c++-compiler update.
> 
> Yes.
> 
> > 
> > What about trying with a clean build tree?
> 
> Did that. Error remains.
> 
> Jürgen
> 

It took ages to compile gcc6.2.0 ...
The test with this compiler (+cmake  and again without  '-std=c++14') does 
compile and link everything.
Could you give cmake a chance?

Kornel

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

Re: Bug in 2.2.2 for Mac

[Stephan Witt]

Am 16.10.2016 um 00:43 schrieb Christopher Menzel :
> 
> Sorry, I should have been clearer about that. The submenus are rendered 
> inaccessible. Also, Open Recent is greyed out. But other stuff, like my user 
> defined key bindings still work.
> 
> -chris
> 
> On Oct 15, 2016, at 6:19 PM, Richard Heck  wrote:
> 
>> On 10/15/2016 04:38 PM, Christopher Menzel wrote:
>> 
>>> 
>>> On 15 Oct 2016, at 4:31 PM, Christopher Menzel  
>>> wrote:
 
 Howdy LyX developers,
 
 There appears to be a bug in 2.2.2 for Mac (LyX-2.2.2+qt5-x86_64-cocoa). 
 The triangles in the top-level dropdown menus that lead to submenus all 
 appear to be missing. See attached screenshot.
>> 
>> Are the menus themselves accessible? Or does the lack of triangles cause 
>> them to be inaccessible?

I did a new build with Qt 5.6.2 and made a disk image with it and put it here:

https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.2%2Bqt5.6.2-x86_64-cocoa.dmg
https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.2%2Bqt5.6.2-x86_64-cocoa.dmg.sig

Sorry, I did my tests with shortcuts only and didn’t notice the broken menu.
And I’m not sure what caused the problem - I’ll investigate it later.

Now it works for me. Christopher, please try this build and tell us how it works
for you, thanks.

Regards,
Stephan

Re: master linking errors

[Jean-Marc Lasgouttes]

Le 16/10/2016 à 12:46, Jürgen Spitzmüller a écrit :

As of today (probably related to a system update), master does not link
any longer. I get:

BiblioInfo.o: In function


Less intimidating version (hand made) is:

BiblioInfo.o: In function
`lyx::BibTeXInfo::getValueForKey(string const&, lyx::Buffer const&, 
docstring const&, docstring const&, docstring const&, 
vector, unsigned long) const':

/home/juergen/lyx/lyx-devel/src/BiblioInfo.cpp:765: undefined reference
to `lyx::html::cleanAttr(docstring const&)'

liblyxcore.a(Buffer.o): In function
`lyx::Buffer::writeLaTeXSource(lyx::otexstream&, string const&, 
lyx::OutputParams const&, lyx::Buffer::OutputWhat) const':

/home/juergen/lyx/lyx-devel/src/Buffer.cpp:1910: undefined reference to
`lyx::latexParagraphs(lyx::Buffer const&, lyx::Text const&, 
lyx::otexstream&, lyx::OutputParams const&, string const&)'


liblyxcore.a(Buffer.o): In function
`lyx::Buffer::writeLyXHTMLSource(docstring&, lyx::OutputParams const&,
lyx::Buffer::OutputWhat) const':



Stable links successfully.


It could be something related to C++14, but I do not know what.

JMarc

Re: master linking errors

[Jürgen Spitzmüller]

Am Sonntag, den 16.10.2016, 04:08 -0700 schrieb Kornel Benko:
> Am Sonntag, 16. Oktober 2016 um 12:46:28, schrieb Jürgen Spitzmüller
> 
> > As of today (probably related to a system update),
> 
> 
> This means probably also c++-compiler update.

Yes.

> 
> What about trying with a clean build tree?

Did that. Error remains.

Jürgen

> 
> > 

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

Re: master linking errors

[Kornel Benko]

Am Sonntag, 16. Oktober 2016 um 12:46:28, schrieb Jürgen Spitzmüller 

> As of today (probably related to a system update),

This means probably also c++-compiler update.

What about trying with a clean build tree?

> master does not link
> any longer. I get:
> 
> BiblioInfo.o: In function
> `lyx::BibTeXInfo::getValueForKey(std::__cxx11::basic_string std::char_traits, std::allocator > const&, lyx::Buffer
> const&, std::__cxx11::basic_string std::allocator > const&, std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> std::__cxx11::basic_string std::allocator > const&, std::__debug::vector const*, std::allocator >, unsigned long)
> const':
> /home/juergen/lyx/lyx-devel/src/BiblioInfo.cpp:765: undefined reference
> to `lyx::html::cleanAttr(std::__cxx11::basic_string std::char_traits, std::allocator > const&)'
> liblyxcore.a(Buffer.o): In function
> `lyx::Buffer::writeLaTeXSource(lyx::otexstream&,
> std::__cxx11::basic_string std::allocator > const&, lyx::OutputParams const&,
> lyx::Buffer::OutputWhat) const':
> /home/juergen/lyx/lyx-devel/src/Buffer.cpp:1910: undefined reference to
> `lyx::latexParagraphs(lyx::Buffer const&, lyx::Text const&,
> lyx::otexstream&, lyx::OutputParams const&,
> std::__cxx11::basic_string std::allocator > const&)'
> liblyxcore.a(Buffer.o): In function
> `lyx::Buffer::writeLyXHTMLSource(std::basic_ostream std::char_traits >&, lyx::OutputParams const&,
> lyx::Buffer::OutputWhat) const':
> 
> etc. (a long list)
> 
> Configuration
>   Host type:   x86_64-unknown-linux-gnu
>   Special build flags:  build=development std-regex warnin
> gs assertions stdlib-debug use-aspell use-enchant use-hunspell
>   C++ Compiler:g++ (6)
>   C++ Compiler flags:   -Wall -Wextra -fPIC -g -O -std=c++14 
>   C++ Compiler user flags:   
>   Linker flags:
>   Linker user flags:   
>   Qt Frontend:
>   Qt version:5.7.0
>   Packaging:   posix
>   LyX binary dir:  /usr/local/bin
>   LyX files dir:   /usr/local/share/lyx-dev
> 
> 
> gcc version 6.2.1 20160830 [gcc-6-branch revision 239856] (SUSE Linux)
> autoconf (GNU Autoconf) 2.69
> automake (GNU automake) 1.15

I am using gcc6.1.0, cmake. No problems, but disabled '-std=c++14' because of 
wrong handling of regular expressions
in advanced search.

> Stable links successfully.
> 
> Ideas?
> 
> Jürgen

Kornel

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

master linking errors

[Jürgen Spitzmüller]

As of today (probably related to a system update), master does not link
any longer. I get:

BiblioInfo.o: In function
`lyx::BibTeXInfo::getValueForKey(std::__cxx11::basic_string const&, lyx::Buffer
const&, std::__cxx11::basic_string const&, std::__cxx11::basic_string const&,
std::__cxx11::basic_string const&, std::__debug::vector >, unsigned long)
const':
/home/juergen/lyx/lyx-devel/src/BiblioInfo.cpp:765: undefined reference
to `lyx::html::cleanAttr(std::__cxx11::basic_string const&)'
liblyxcore.a(Buffer.o): In function
`lyx::Buffer::writeLaTeXSource(lyx::otexstream&,
std::__cxx11::basic_string const&, lyx::OutputParams const&,
lyx::Buffer::OutputWhat) const':
/home/juergen/lyx/lyx-devel/src/Buffer.cpp:1910: undefined reference to
`lyx::latexParagraphs(lyx::Buffer const&, lyx::Text const&,
lyx::otexstream&, lyx::OutputParams const&,
std::__cxx11::basic_string const&)'
liblyxcore.a(Buffer.o): In function
`lyx::Buffer::writeLyXHTMLSource(std::basic_ostream&, lyx::OutputParams const&,
lyx::Buffer::OutputWhat) const':

etc. (a long list)

Configuration
  Host type:   x86_64-unknown-linux-gnu
  Special build flags:  build=development std-regex warnin
gs assertions stdlib-debug use-aspell use-enchant use-hunspell
  C++ Compiler:g++ (6)
  C++ Compiler flags:   -Wall -Wextra -fPIC -g -O -std=c++14 
  C++ Compiler user flags:   
  Linker flags:
  Linker user flags:   
  Qt Frontend:
  Qt version:      5.7.0
  Packaging:   posix
  LyX binary dir:  /usr/local/bin
  LyX files dir:   /usr/local/share/lyx-dev


gcc version 6.2.1 20160830 [gcc-6-branch revision 239856] (SUSE Linux)
autoconf (GNU Autoconf) 2.69
automake (GNU automake) 1.15

Stable links successfully.

Ideas?

Jürgen

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

Re: [patch] support for Piedmontese

[Jürgen Spitzmüller]

Am Sonntag, den 16.10.2016, 03:12 +0200 schrieb Uwe Stöhr:
> Am 16.10.2016 um 03:00 schrieb Uwe Stöhr:
> 
> > Attached is the complete patch.
> 
> 
> Attached is a better patch inclusing support for Friulian.

The patch looks good.

Jürgen

> 
> regards Uwe
> 

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

Re: #9568: Multicolumn, fixed width, and decimal-separator-alignment does not compile

[Jürgen Spitzmüller]

> Dear developers,
two comments:
First, I just checked with the new 2.2.2 (thanks for that!) and my 
original example file still doesn't compile. So you guys are
> tolerating 
a situation where normal usage of Lyx without any hacks can produce 
"rubbish". This should be fixed ASAP, IMHO (hey, never used two
> acronyms 
in a row!), whatever the solution is.

That's exactly the problem: there is no consensual solution. We have
two proposals, both not perfect, and two contradictory opinions.

I have made my own position very clear, and it did not change.

> 
Secondly, what do you think about my previous comment in the tracker 
> 
that the left/right/center alignment choice and the decimal separator
>  
alignment choice are independent, so that every combination should be
>  
possible?
Is this doable in Latex (presumably with a package)? Or is it simply
> too 
difficult to implement in Lyx?

If you show us how to do it in LaTeX, we can implement it in LyX.

Jürgen

> 
thanks,
sven

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

Re: [ANNOUNCE] LyX 2.2.2 Released

[racoon]

On 15.10.2016 18:11, Richard Heck wrote:

Public release of LyX version 2.2.2
===

We are proud to announce the release of LyX 2.2.2. This is the second
maintenance release in the 2.2.x series.

You can download LyX 2.2.2 from http://www.lyx.org/Download/.

[...]

We hope you enjoy using LyX 2.2.2.

The LyX team.
http://www.lyx.org


Thanks a lot from me as well! I might be filing quite some bug reports 
but it really is just a measure of how useful I find LyX rather than not.


One thing about the announcement on the website:

http://www.lyx.org/News#item1

There is a link to the *binaries* which takes one to

ftp://ftp.lyx.org/pub/lyx/bin/2.2.2/

And there are for example four different versions of the Windows 
installer. People not involved in the development or otherwise 
unfamiliar with LyX might get confused. Maybe it is better to link 
insetad to


http://www.lyx.org/Download#toc2

Daniel