Kornel Benko | 26 May 19:00 2016

Wrong file path in MergedMauals.lyx

Subject says it all.

Attachment (MergedManuals.lyx.patch): text/x-patch, 393 bytes
Scott Kostyshak | 24 May 22:39 2016

cygwin installer for 2.2.0

Do we wait for a cygwin installer before announcing? Is Enrico the one
who takes care of this? I had forgotten that we provided cygwin
installers for the final realize until I looked at

Scott Kostyshak | 24 May 04:32 2016

Tarballs for LyX 2.2.0 are on FTP

Hi all,

The tarballs for LyX 2.2.0 can be found at


As usual I'll wait before announcing the release until after uploading
the binaries and providing some time for the mirrors.

Thanks to everyone for all the help with the final steps in the release

Jean-Pierre Chrétien | 24 May 00:22 2016

Minor last minute edits in fr.po


Jean-Marc pointed out to me a mistake and a shortcut conflict, I have 2 commits 
ready fot these. Should this wait for 2.2.1 or may I push to master ?


commit 9e5198f4f59a1059b116381bb75070cbcf20bc82
Author: jpc <jpc <at> lyx.org>
Date:   Mon May 23 23:15:10 2016 +0100

     * One more shortcut conflict solved
     * fr.gmo updated

diff --git a/po/fr.gmo b/po/fr.gmo
index 84ebb9e..7f59870 100644
Binary files a/po/fr.gmo and b/po/fr.gmo differ
diff --git a/po/fr.po b/po/fr.po
index 3dd65b2..dc434d0 100644
--- a/po/fr.po
+++ b/po/fr.po
 <at>  <at>  -311,14 +311,14  <at>  <at> 
  # 22 avril 2016 : dernière revue avant 2.2.0
  # ------------------------------------------------------------------
  # 23 mai 2016 : correction d'une erreur de traduction (tailles d'icônes)
-#               et d'un conflit de raccourcis
+#               et de conflits de raccourcis
  # ------------------------------------------------------------------
  msgid ""
(Continue reading)

Scott Kostyshak | 22 May 21:24 2016

Using xmllint to test our LyXHTML export

Uwe and Georg have recently found and fixed a bug in our internal XHTML
export. Why not test the export automatically?

These tests would be fast (compared to the LaTeX compilation tests we
have). I think our current XHTML tests just check that the exit code is
zero. We can extend these tests to work as follows:

1. Export to .xhtml and check the exit code.
2. Check the terminal output from LyX (I think we do this for other tests, such
as the lyx2lyx tests).
3. Use xmllint or something similar and check exit code.

I know nothing about XHTML. Does anyone have experience with xmllint or
any other tool? The only other tool I saw mentioned when searching is
XMLStarlet. If someone does have experience, which tool do you
recommend? Also, I'd be curious which options you think should be used.
It seems to me that we would not want a very strict validation, and
basically want to check whether the file is expected to open in a
webbrowser without parser errors.

Scott Kostyshak | 21 May 23:58 2016

Fix for using system icons

There is a patch for

I'm planning to commit the patch before rc2 unless someone objects. The
patch is simple and has been tested.

Scott Kostyshak | 21 May 19:43 2016

Plan to tag and tar 2.2.0rc2 on Monday

Dear all,

Unless something comes up, I'm planning to tag and tar rc2 on Monday. At
that point I'll put the tar balls on the FTP and whenever Mac and Win
binaries are uploaded we will announce the release.

Thank you all for your help,

pdv | 21 May 11:13 2016

Bringing a hidden window to the front on a mac.

If one has 2 documents open in LyX 2.2 in 2 separate windows and one 
wants to bring the one in the back to the front via the menu 
View/Hidden/... then (on a mac, OSX 10.11.4) nothing happens. Although 
the window has been activated, it's not brought to the front. [When 
switching to e.g. the Finder and then back to LyX by clicking on the LyX 
icon in the Dock, the hidden window will now be shown in front.]

The problem is solved by adding a raise() call to the activateWindow() 
call in GuiView.cpp (see included patch).


P. De Visschere
diff --git a/src/frontends/qt4/GuiView.cpp b/src/frontends/qt4/GuiView.cpp
index c2101f3..89bff9a 100644
--- a/src/frontends/qt4/GuiView.cpp
+++ b/src/frontends/qt4/GuiView.cpp
 <at>  <at>  -3615,6 +3615,7  <at>  <at>  void GuiView::dispatch(FuncRequest const & cmd, DispatchResult & dr)
 			for (; i != ids.size(); ++i) {
 				GuiView & gv = guiApp->view(ids[i]);
 				if (gv.workArea(*buffer)) {
+					gv.raise();
Georg Baum | 21 May 11:11 2016

[patch] fix bug 10124 (XHTML export of some symbols)

While testing imagemagick 7 (more on that later) I stumbled upon bug 10124 
as well. It is a simple typo where LyX outputs /<mo> instead of </mo>. OK 
for 2.2.0?

Attachment (x.diff): text/x-patch, 496 bytes
mn | 21 May 10:34 2016

enhancing search: make it find everything; including source

Currently it seems quite difficult to get the search function to really
find everything that might be in a lyx-document.

One example:
Open a new document, language is set to English.
Enter a word enclosed in smart quotes.
Change document language to German with the corresponding smart quotes.
Enter a word enclosed with smart quotes.
Enter a third word, this time enclosing it with direct quotes (Opt-^ /

This results in the following source:
``word'' ,,word`` \quotedblbase word\textquotedblleft{}

When you open the search panel and enter the key-combo used for
smart-quotes you will get the "ascii-quote" sign and will not find anything.
When entering the direct German closing quote, you will only find
\textquotedblleft{}, but not ``.
The ‘smart’-quotes are invisible to search?

So while in the editor, one and the same character representation should
be found when searching for it. (Being aware of the diffreent means to
achieve it.)

(btw: entering `` into the search panel renders it inoperable?
This is on OS X: the input obviously waits for a second compose
character that the acent goes to and doesn’t treat this as a backtick.
Nevertheless, the search button ist dead and when you switch to the
document and back to the search panel one of the `’s is gone.
As a workaround entering space and deleting that right away reactivates
(Continue reading)

Bryan Brown | 20 May 17:56 2016

Re: #10145: Lyx 2.2rc1 Mac not opening

Thanks for the prompt response.

I backed up and deleted the preferences file and Lxy 2.2 came right up.  When i tried to open a document it
reported “cannot load basic module” and a lot of associated problems.

I then deleted the Lyx 2.2 app and Lyx-2.2 directory in ~/Library and then ran my 2.1.4 installation.  I then
renamed the 2.1.4 app to OldLyx and reinstalled by copying Lyx 2.2 to Applications.  It seems to be working. 
I have no idea why it works now but didn’t before.  That is pretty much what I did before.

I will now try to get my laptop installation to work.  It had the same problem.

Bill Brown

> On May 20, 2016, at 2:40 AM, LyX Ticket Tracker <trac <at> lyx.org> wrote:
> #10145: Lyx 2.2rc1 Mac not opening
> -----------------------+-------------------------
> Reporter:  bwbwn      |       Owner:  lasgouttes
>     Type:  defect     |      Status:  new
> Priority:  normal     |   Milestone:
> Component:  general    |     Version:  2.2.0dev
> Severity:  normal     |  Resolution:
> Keywords:  os=macosx  |
> -----------------------+-------------------------
> Changes (by skostysh):
> * cc: stwitt (added)
> * keywords:  Error reading configuration file => os=macosx
(Continue reading)