Re: [LyX/master] Fix thinko in Buffer::preview. It is possible for this routine to be called when we do not have a cloned Buffer, namely, if we do not have EXPORT_in_THREAD defined.

[Richard Heck]

On 07/10/2016 01:33 AM, Scott Kostyshak wrote:
> On Sun, Jul 10, 2016 at 07:16:13AM +0200, Richard Heck wrote:
>> commit d8aab4af9e6e72c835f78ba54a46687b870c25fa
>> Author: Richard Heck 
>> Date:   Sun Jul 10 01:12:42 2016 -0400
>>
>> Fix thinko in Buffer::preview. It is possible for this routine to
>> be called when we do not have a cloned Buffer, namely, if we do not
>> have EXPORT_in_THREAD defined.
> Thanks for fixing this. How does one set EXPORT_in_THREAD? I imagine
> this could be useful for debugging purposes (e.g ruling out that a bug
> is due to exporting in a separate thread).

PS I just stumbled across this when looking at #9680 (Arabic filenames
changing e.g. to _.pdf on preview). I figured out what is happening
there, but it is not obvious what to do about it.

Richard

Re: [LyX/master] Fix thinko in Buffer::preview. It is possible for this routine to be called when we do not have a cloned Buffer, namely, if we do not have EXPORT_in_THREAD defined.

[Richard Heck]

On 07/10/2016 01:33 AM, Scott Kostyshak wrote:
> On Sun, Jul 10, 2016 at 07:16:13AM +0200, Richard Heck wrote:
>> commit d8aab4af9e6e72c835f78ba54a46687b870c25fa
>> Author: Richard Heck 
>> Date:   Sun Jul 10 01:12:42 2016 -0400
>>
>> Fix thinko in Buffer::preview. It is possible for this routine to
>> be called when we do not have a cloned Buffer, namely, if we do not
>> have EXPORT_in_THREAD defined.
> Thanks for fixing this. How does one set EXPORT_in_THREAD? I imagine
> this could be useful for debugging purposes (e.g ruling out that a bug
> is due to exporting in a separate thread).

It's #defined in GuiView.cpp and GuiAlert.cpp. It's set in the code, but
can be manually unset by people who don't want the risks of background
export, threading, etc. And yes, it is useful for the purpose you mentioned.

Probably, it should be exposed via configure, etc, but no one ever did that.

Richard

Re: [LyX/master] Fix thinko in Buffer::preview. It is possible for this routine to be called when we do not have a cloned Buffer, namely, if we do not have EXPORT_in_THREAD defined.

[Scott Kostyshak]

On Sun, Jul 10, 2016 at 07:16:13AM +0200, Richard Heck wrote:
> commit d8aab4af9e6e72c835f78ba54a46687b870c25fa
> Author: Richard Heck 
> Date:   Sun Jul 10 01:12:42 2016 -0400
> 
> Fix thinko in Buffer::preview. It is possible for this routine to
> be called when we do not have a cloned Buffer, namely, if we do not
> have EXPORT_in_THREAD defined.

Thanks for fixing this. How does one set EXPORT_in_THREAD? I imagine
this could be useful for debugging purposes (e.g ruling out that a bug
is due to exporting in a separate thread).

Scott


signature.asc
Description: PGP signature

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Scott Kostyshak]

On Sat, Jul 09, 2016 at 06:36:36PM +0200, Enrico Forestieri wrote:

> I have also extended the fix to Qt4 in much the same manner and it works
> for me. In the attached patch I have also incorporated the changes for
> cmake, except for Qt4, as I don't know what is required.

I tested the new patch and it works well for me.

> The more I think about it, the more I am convinced that this is a Qt issue.

Should we put a fixme/todo somewhere to check if Qt fixes the issue in
e.g. five years so we can remove the workaround? I do not mind if you do
not want to commit the patch at all since your guess is that it's a Qt
issue, and also because the commit is somewhat complicated. It's your
call since I think you're the one who best understands the situation.

In any case, thanks for your work on this. I've learned something about
X events by trying (and failing) to debug this myself and then by
studying your patch.

> Clipboard managers are always troublesome. Cannot help here, sorry.

+1

Scott


signature.asc
Description: PGP signature

Re: lualatex with TL2016

[Scott Kostyshak]

On Sat, Jul 09, 2016 at 05:26:06PM +0200, Kornel Benko wrote:
> Am Samstag, 9. Juli 2016 um 16:46:01, schrieb Jürgen Spitzmüller 
> 
> > Am Samstag, den 09.07.2016, 15:18 +0200 schrieb Kornel Benko:
> > > It meant that they compile without errors. Tested with A4 setting and
> > > portrait.
> > > 
> > > Now retesting with landscape: Works too. Pdf output on screen fits.
> > 
> > OK, thanks again. I committed a slightly modified version.
> > 
> > Should also go to stable I suppose.
> 
> +1

I agree this would be nice for stable. To summarize the situation for
Richard, the following are the pre-requisites for this problem to be
triggered:

1. TeX Live 2016
2. Using an option in Document Settings > Page Layout
3. LuaTeX

If those three are satisfied, then an error will be given. On the one
hand, I don't think we've received any reports about this issue from
users since TeX Live 2016 has been out, so I don't think the above three
pre-requisites are common. On the other hand, the patch is simple and
Kornel and Jürgen have tested it.

Scott


signature.asc
Description: PGP signature

Re: toolbars Lock menu

[Scott Kostyshak]

On Sat, Jul 09, 2016 at 03:19:51PM +0100, José Abílio Matos wrote:
> On Saturday, July 9, 2016 2:42:11 PM WEST racoon wrote:
> > By the way, since I have never worked on a project like LyX, if anyone 
> > has tips on how to work effectively, I am pleased to know. I guess using 
> > git is one.
> 
> The first step is to read:
> http://www.lyx.org/Development
> 
> where there are documents like:
> http://www.lyx.org/DevFAQ
> 
> There are places that can help but those are a good first step.
> 
> Regards,
> -- 
> José Abílio

In addition to José's advice, my advice is the following:

before you spend time doing any work, first check in with lyx-devel and
make a proposal. Because you are proposing a feature (as opposed to a
feature), the most important part is motivation: why do you want to lock
the toolbar? Why would a significant amount of users want to lock the
toolbar? A good way to improve your argument (but by no means
sufficient) for why your feature would be a good idea is to make
parallels to other programs that are similar to LyX. Does Libre Office
have such a feature?

After you have motivated the general idea, describe your feature as
detailed as possible. The most important aspect of this is actually the
interface (not the implementation). How will users use this feature?
e.g. will it be in the context menu (the right-click menu)? Will it be
in the menus at the top (File, Edit, ...)?

Then, and this is more optional, you can ask for comments on a basic
outline of implementation.

Then, eventually post a patch. You will get bonus points if you mention
that if your patch is given a preliminary "thumbs up", you'd be happy to
work on documentation for the feature, and you even have an idea for the
exact place in the manuals where the documentation would go. Note that
in your particular feature proposal, I don't know if we usually document
such features, but this paragraph is meant to be more general.

The above steps are not just for beginners. Even experienced developers
go through them. But I think that newcommers do not realize that often
the first step is not a patch.

And yes, get familiar with git. You should view this as a long-term
investment so spend the time to learn it well. Many software projects
are moving to Git. You will likely use Git for your own individual
programming projects, and even for non-programming projects (I use it to
organize my teaching notes). After a year or so, you will start to
criticize your friends who rely on the old backup mechanism of copying
the folder MyProject to MyProject10234 (but please try to be nice to
them, they don't know any better).

Good luck!

Scott


signature.asc
Description: PGP signature

Re: Aw: Re: #10199: Non-encodable characters with XeTeX

[Scott Kostyshak]

On Fri, Jul 08, 2016 at 10:06:52PM -0400, Scott Kostyshak wrote:
> On Fri, Jul 08, 2016 at 09:23:32PM +0100, Guillaume Munch wrote:
> 
> > In that case, if you already have everything set up and that does not cost
> > you any more effort, thank you for stepping forward.
> 
> I will run them over the night and give the results tomorrow.

Tests indicate that commit b170b6e4 lead to ctex_pdf4_texF going from
failing to passing, and no other changes in the tests. So according to
the tests [1], b170b6e4 is safe.

Scott

[1] it should be said that about 500 (out of 5000) of the tests are
failing, so they do not provide nay information.


signature.asc
Description: PGP signature

Paragraph::id()

[Richard Heck]

If I do:
onePar.id() == otherPar.id()
will that do what I obviously want it to do? I.e., work as a proxy for:
onePar == otherPar
??

Richard

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 21:26:51, schrieb Enrico Forestieri 
> On Sat, Jul 09, 2016 at 09:02:09PM +0200, Enrico Forestieri wrote:
> > 
> > Then, looking at development/cmake/ConfigureChecks.cmake, it seems to
> > me that QT_USES_X11 is correctly set for Qt4, because the QX11Info header
> > is always installed on all platforms and compilation fails if X11 is
> > not the correct backend. This is not true for Qt5, as QtX11Extras/QX11Info
> > is only present if the Qt5X11Extras module is installed, and not otherwise.
> > So, compilation of the code snippet at lines 212-216 may fail even if X11
> > is the backend, so that QT_USES_X11 may not be correctly guessed with Qt5.
> 
> Sorry, I now see that it is guarded by "if (Qt5X11Extras_FOUND)".
> In this case, the last sentence above should read:
> So, compilation of the code snippet at lines 212-216 is not attempted
> even if X11 is the backend, so that QT_USES_X11 may not be guessed with Qt5.
> 
> A more safe approach is based on looking at QtCore/qconfig.h, which
> directly tells you what is the default backend. Indeed it contains
> #define QT_QPA_DEFAULT_PLATFORM_NAME "xcb"
> if X11 is the backend.
> 

At the time I introduced the check, the need for knowing about X11 was testing 
with xvkbd.

I will try to use this define.

Kornel

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

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 21:02:09, schrieb Enrico Forestieri 
> On Sat, Jul 09, 2016 at 07:36:53PM +0200, Kornel Benko wrote:
> > Am Samstag, 9. Juli 2016 um 18:43:50, schrieb Enrico Forestieri 
> > 
> > > 
> > > Please, can you also check what has to be done for Qt4? The problem
> > > is that I have to use a X11 function and thus the X11 library should
> > > be added for the final link step, as already done for autotools.
> > 
> > Have I overseen  HAVE_QT4_X11_EXTRAS in your patch?
> 
> There is no Qt4X11Extras module.
> 
> > We check for  QX11Info in development/cmake/ConfigureChecks.cmake:231
> > The class QX11Info is only available if qt4 uses X11.
> > What more do you need?
> 
> That in the final link step -lX11 is added to the required libraries
> if Qt4 uses X11 as a backend.
> 
> Then, looking at development/cmake/ConfigureChecks.cmake, it seems to
> me that QT_USES_X11 is correctly set for Qt4, because the QX11Info header
> is always installed on all platforms and compilation fails if X11 is
> not the correct backend. This is not true for Qt5, as QtX11Extras/QX11Info
> is only present if the Qt5X11Extras module is installed, and not otherwise.
> So, compilation of the code snippet at lines 212-216 may fail even if X11
> is the backend, so that QT_USES_X11 may not be correctly guessed with Qt5.
> 

So what do you propose? The snipped 212-216 is compiled only if 
Qt5X11Extras_FOUND.

How else can we be sure about X11?

Kornel

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

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Enrico Forestieri]

On Sat, Jul 09, 2016 at 09:02:09PM +0200, Enrico Forestieri wrote:
> 
> Then, looking at development/cmake/ConfigureChecks.cmake, it seems to
> me that QT_USES_X11 is correctly set for Qt4, because the QX11Info header
> is always installed on all platforms and compilation fails if X11 is
> not the correct backend. This is not true for Qt5, as QtX11Extras/QX11Info
> is only present if the Qt5X11Extras module is installed, and not otherwise.
> So, compilation of the code snippet at lines 212-216 may fail even if X11
> is the backend, so that QT_USES_X11 may not be correctly guessed with Qt5.

Sorry, I now see that it is guarded by "if (Qt5X11Extras_FOUND)".
In this case, the last sentence above should read:
So, compilation of the code snippet at lines 212-216 is not attempted
even if X11 is the backend, so that QT_USES_X11 may not be guessed with Qt5.

A more safe approach is based on looking at QtCore/qconfig.h, which
directly tells you what is the default backend. Indeed it contains
#define QT_QPA_DEFAULT_PLATFORM_NAME "xcb"
if X11 is the backend.

-- 
Enrico

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Enrico Forestieri]

On Sat, Jul 09, 2016 at 07:36:53PM +0200, Kornel Benko wrote:
> Am Samstag, 9. Juli 2016 um 18:43:50, schrieb Enrico Forestieri 
> 
> > 
> > Please, can you also check what has to be done for Qt4? The problem
> > is that I have to use a X11 function and thus the X11 library should
> > be added for the final link step, as already done for autotools.
> 
> Have I overseen  HAVE_QT4_X11_EXTRAS in your patch?

There is no Qt4X11Extras module.

> We check for  QX11Info in development/cmake/ConfigureChecks.cmake:231
> The class QX11Info is only available if qt4 uses X11.
> What more do you need?

That in the final link step -lX11 is added to the required libraries
if Qt4 uses X11 as a backend.

Then, looking at development/cmake/ConfigureChecks.cmake, it seems to
me that QT_USES_X11 is correctly set for Qt4, because the QX11Info header
is always installed on all platforms and compilation fails if X11 is
not the correct backend. This is not true for Qt5, as QtX11Extras/QX11Info
is only present if the Qt5X11Extras module is installed, and not otherwise.
So, compilation of the code snippet at lines 212-216 may fail even if X11
is the backend, so that QT_USES_X11 may not be correctly guessed with Qt5.

-- 
Enrico

Re: [LyX/master] Added missing ipa icons to distribution

[Richard Heck]

On 07/09/2016 06:41 AM, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 15.06.2016, 15:04 +0200 schrieb Kornel Benko:
>> commit 43d284e15ad6193da2508a57b5260cb85ff4cdb9
>> Author: Kornel Benko 
>> Date:   Wed Jun 15 15:03:55 2016 +0200
>>
>> Added missing ipa icons to distribution
> This should go to branch as well (also 60a1827b65).

OK.

rh

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 18:43:50, schrieb Enrico Forestieri 
> On Sat, Jul 09, 2016 at 11:45:37AM +0200, Kornel Benko wrote:
> 
> > Am Samstag, 9. Juli 2016 um 04:09:30, schrieb Enrico Forestieri 
> > 
> > > I came up with the attached patch that solves the issue for me.
> > > It requires the Qt5X11Extras module, which is not mandatory, though.
> > > The patch simply tries to refresh the timestamp of the selection request.
> > > I still get the warning from Qt5 (even if only once), but the paste by the
> > > middle mouse button succeeds anyway. Recall that this issue does not occur
> > > with a focus-follows-mouse policy. Given that it also does not occur with
> > > some applications, I don't know who is to blame for this.
> > > 
> > > The patch is for Qt5 and autotools only (I don't know cmake, sorry).
> > > 
> > 
> > Attached.
> 
> Thanks, but...
> 
> > diff --git a/CMakeLists.txt b/CMakeLists.txt
> > index 76cbdde..e39fc59 100644
> > --- a/CMakeLists.txt
> > +++ b/CMakeLists.txt
> > @@ -929,6 +929,7 @@ set(QPA_XCB)
> >  if(Qt5X11Extras_FOUND AND QT_USES_X11)
> ># QPA_XCB is only valid if QT5+X11
> >set(QPA_XCB 1)
> > +  set(HAVE_QT5_X11_EXTRAS 1)
> >  endif()
> 
> This doesn't strike me as correct. QPA_XCB has to be set when Qt5
> uses X11, independently of the presence of the Qt5X11Extras module.
> In the patch I changed this to

I understand that. For me the presence of Qt5X11Extras-module was indication of 
X11.

> -if(Qt5X11Extras_FOUND AND QT_USES_X11)
> +if(LYX_USE_QT MATCHES "QT5" AND QT_USES_X11)
># QPA_XCB is only valid if QT5+X11
>set(QPA_XCB 1)
> +  if(Qt5X11Extras_FOUND)
> +set(HAVE_QT5_X11_EXTRAS 1)
> +  endif()
>  endif()
> 
> Please, can you also check what has to be done for Qt4? The problem
> is that I have to use a X11 function and thus the X11 library should
> be added for the final link step, as already done for autotools.

Have I overseen  HAVE_QT4_X11_EXTRAS in your patch?

We check for  QX11Info in development/cmake/ConfigureChecks.cmake:231
The class QX11Info is only available if qt4 uses X11.
What more do you need?

Kornel


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

Re: Compiling with Microsoft Visual C++

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 17:41:37, schrieb racoon 
> On 09.07.2016 17:33, racoon wrote:
>  > Next, I copy the dependencies. The culprit is, however, that there is no
>  > lyx.exe in
>  > C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I
>  > can't execute it.
> 
> There are LyX.exe files in
> 
> C:\LyX\lyx-23-build\bin\Debug
> 
> and
> 
> C:\LyX\lyx-23-build\LYX_INSTALLED\bin

This is the correct installation place.
1.) You can make a .zip file from the directory  
"C:\LyX\lyx-23-build\LYX_INSTALLED".
2.) You can unzip it wherever you want.
I don't know how to proceed with registering on windows.

> though. But I am not sure what to do with it.
> 
> Daniel (Back on Sunday (GMT) evening the earliest)

Kornel

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

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Enrico Forestieri]

On Sat, Jul 09, 2016 at 11:45:37AM +0200, Kornel Benko wrote:

> Am Samstag, 9. Juli 2016 um 04:09:30, schrieb Enrico Forestieri 
> 
> > I came up with the attached patch that solves the issue for me.
> > It requires the Qt5X11Extras module, which is not mandatory, though.
> > The patch simply tries to refresh the timestamp of the selection request.
> > I still get the warning from Qt5 (even if only once), but the paste by the
> > middle mouse button succeeds anyway. Recall that this issue does not occur
> > with a focus-follows-mouse policy. Given that it also does not occur with
> > some applications, I don't know who is to blame for this.
> > 
> > The patch is for Qt5 and autotools only (I don't know cmake, sorry).
> > 
> 
> Attached.

Thanks, but...

> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index 76cbdde..e39fc59 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -929,6 +929,7 @@ set(QPA_XCB)
>  if(Qt5X11Extras_FOUND AND QT_USES_X11)
># QPA_XCB is only valid if QT5+X11
>set(QPA_XCB 1)
> +  set(HAVE_QT5_X11_EXTRAS 1)
>  endif()

This doesn't strike me as correct. QPA_XCB has to be set when Qt5
uses X11, independently of the presence of the Qt5X11Extras module.
In the patch I changed this to

-if(Qt5X11Extras_FOUND AND QT_USES_X11)
+if(LYX_USE_QT MATCHES "QT5" AND QT_USES_X11)
   # QPA_XCB is only valid if QT5+X11
   set(QPA_XCB 1)
+  if(Qt5X11Extras_FOUND)
+set(HAVE_QT5_X11_EXTRAS 1)
+  endif()
 endif()

Please, can you also check what has to be done for Qt4? The problem
is that I have to use a X11 function and thus the X11 library should
be added for the final link step, as already done for autotools.

-- 
Enrico

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Enrico Forestieri]

On Sat, Jul 09, 2016 at 03:27:40AM -0400, Scott Kostyshak wrote:
> 
> I tried a few random variations on your patch to squash the last
> warning. One that worked for me is to add
> 
>   return true;
> 
> after
> 
>   xcb_flush(con);
> 
> I have no idea if that makes any sense but perhaps it provides a clue.
> Does the warning go away if you add that?

Yes, it does. The documentation is not so much clear about this. It says
"if you want to filter the message out, i.e. stop it being handled further,
return true; otherwise return false."
but it is not clear whether it refers to the *same* message or to the
same message type. Anyway, returning true has no ill effect and gets
rid of the warning (even compiling without Qt5X11Extras), so I added it.
Thanks for the tip.

I have also extended the fix to Qt4 in much the same manner and it works
for me. In the attached patch I have also incorporated the changes for
cmake, except for Qt4, as I don't know what is required.
The more I think about it, the more I am convinced that this is a Qt issue.

> Finally, this doesn't seem to solve the flood of messages I get when
> CopyQ is running, but I don't think this is worth investigating.

Clipboard managers are always troublesome. Cannot help here, sorry.

-- 
Enrico
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 76cbdde..7e13427 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -926,9 +926,12 @@ include(${LYX_CMAKE_DIR}/ConfigureChecks.cmake)
 configure_file(${LYX_CMAKE_DIR}/configCompiler.h.cmake 
${TOP_BINARY_DIR}/configCompiler.h)
 
 set(QPA_XCB)
-if(Qt5X11Extras_FOUND AND QT_USES_X11)
+if(LYX_USE_QT MATCHES "QT5" AND QT_USES_X11)
   # QPA_XCB is only valid if QT5+X11
   set(QPA_XCB 1)
+  if(Qt5X11Extras_FOUND)
+set(HAVE_QT5_X11_EXTRAS 1)
+  endif()
 endif()
 configure_file(${LYX_CMAKE_DIR}/config.h.cmake ${TOP_BINARY_DIR}/config.h)
 
diff --git a/config/qt4.m4 b/config/qt4.m4
index 0e357a4..f39c0ed 100644
--- a/config/qt4.m4
+++ b/config/qt4.m4
@@ -172,18 +172,30 @@ AC_DEFUN([QT_DO_IT_ALL],
[AC_MSG_ERROR([LyX requires at least version $1 of Qt. Only version 
$QTLIB_VERSION has been found.])
])
 
+   save_CPPFLAGS=$CPPFLAGS
+   AC_MSG_CHECKING([whether Qt uses the X Window system])
+   CPPFLAGS="$save_CPPFLAGS $QT_CORE_INCLUDES"
if test x$USE_QT5 = xyes ; then
- save_CPPFLAGS=$CPPFLAGS
- AC_MSG_CHECKING([whether Qt uses the X Window system])
- CPPFLAGS="$save_CPPFLAGS $QT_CORE_INCLUDES"
  AC_EGREP_CPP(xcb,
[#include 
QT_QPA_DEFAULT_PLATFORM_NAME],
[AC_MSG_RESULT(yes)
 AC_DEFINE(QPA_XCB, 1, [Define if Qt uses the X Window System])],
[AC_MSG_RESULT(no)])
- CPPFLAGS=$save_CPPFLAGS
+   else
+ AC_PREPROC_IFELSE([AC_LANG_SOURCE([
+   [#include ],
+   [#ifndef Q_WS_X11],
+   [#error Fail],
+   [#endif]])],
+   qt_use_x11=yes,
+   qt_use_x11=no)
+ AC_MSG_RESULT($qt_use_x11)
+ if test "x$qt_use_x11" = "xyes"; then
+   QT_LIB="$QT_LIB -lX11"
+ fi
fi
+   CPPFLAGS=$save_CPPFLAGS
 
QT_FIND_TOOL([QT_MOC], [moc])
QT_FIND_TOOL([QT_UIC], [uic])
@@ -209,6 +221,13 @@ AC_DEFUN([QT_DO_PKG_CONFIG],
if test "x$USE_QT5" != "xno" ; then
qt_corelibs="Qt5Core"
qt_guilibs="Qt5Core Qt5Concurrent Qt5Gui Qt5Svg Qt5Widgets"
+   lyx_use_x11extras=false
+   PKG_CHECK_EXISTS(Qt5X11Extras, [lyx_use_x11extras=true], [])
+   if $lyx_use_x11extras; then
+   qt_guilibs="$qt_guilibs Qt5X11Extras xcb"
+   AC_DEFINE(HAVE_QT5_X11_EXTRAS, 1,
+   [Define if you have the Qt5X11Extras module])
+   fi
lyx_use_winextras=false
PKG_CHECK_EXISTS(Qt5WinExtras, [lyx_use_winextras=true], [])
if $lyx_use_winextras; then
diff --git a/development/cmake/config.h.cmake b/development/cmake/config.h.cmake
index 253d39f..95148b6 100644
--- a/development/cmake/config.h.cmake
+++ b/development/cmake/config.h.cmake
@@ -73,6 +73,9 @@
 // Defined if QT=QT5 uses X11
 #cmakedefine QPA_XCB 1
 
+// Define if you have the Qt5X11Extras module
+#cmakedefine HAVE_QT5_X11_EXTRAS 1
+
 ${Include_used_spellchecker}
 
 #cmakedefine AIKSAURUSLIB_FOUND 1
diff --git a/src/frontends/qt4/GuiApplication.cpp 
b/src/frontends/qt4/GuiApplication.cpp
index 6586207..6f48ed0 100644
--- a/src/frontends/qt4/GuiApplication.cpp
+++ b/src/frontends/qt4/GuiApplication.cpp
@@ -121,10 +121,14 @@
 #ifdef Q_WS_X11
 #include 
 #include 
+#include 
 #undef CursorShape
 #undef None
 #elif defined(QPA_XCB)
 #include 
+#ifdef HAVE_QT5_X11_EXTRAS
+#include 
+#endif
 #endif
 
 #if (QT_VERSION < 0x05) || (QT_VERSION >= 0x050400)
@@ -3130,8 +3134,21 @@ bool GuiApplication::x11EventFilter(XEvent * xev)
BufferView * bv = 

Re: Compiling with Microsoft Visual C++

[racoon]

On 09.07.2016 17:33, racoon wrote:
> Next, I copy the dependencies. The culprit is, however, that there is no
> lyx.exe in
> C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I
> can't execute it.

There are LyX.exe files in

C:\LyX\lyx-23-build\bin\Debug

and

C:\LyX\lyx-23-build\LYX_INSTALLED\bin

though. But I am not sure what to do with it.

Daniel (Back on Sunday (GMT) evening the earliest)

Re: Compiling with Microsoft Visual C++

[racoon]

Okay, next step taken, I think.

I set a couple of paths in CMAKE. Here is the "Show My Changes" output:

---

Commandline options:
-DLYX_USE_QT:STRING="QT5" 
-DQt5Widgets_DIR:PATH="C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Widgets" 
-DLYX_DEPENDENCIES_DOWNLOAD:BOOL="1" -DLYX_INSTALL:BOOL="1" 
-DQt5Core_DIR:PATH="C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Core" 
-DQT_QMAKE_EXECUTABLE:FILEPATH="C:/Qt/Qt5.6.1/5.6/msvc2015/bin/qmake.exe" 
-DCMAKE_PREFIX_PATH:PATH="C:/Qt/Qt5.6.1/5.6/msvc2015" 
-DLYX_INSTALL_PREFIX:PATH="C:/LyX/lyx-23-install"



Cache file:
LYX_USE_QT:STRING=QT5
Qt5Widgets_DIR:PATH=C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Widgets
LYX_DEPENDENCIES_DOWNLOAD:BOOL=1
LYX_INSTALL:BOOL=1
Qt5Core_DIR:PATH=C:\Qt\Qt5.6.1\5.6\msvc2015\lib\cmake\Qt5Core
QT_QMAKE_EXECUTABLE:FILEPATH=C:/Qt/Qt5.6.1/5.6/msvc2015/bin/qmake.exe
CMAKE_PREFIX_PATH:PATH=C:/Qt/Qt5.6.1/5.6/msvc2015
LYX_INSTALL_PREFIX:PATH=C:/LyX/lyx-23-install

---

Not sure whether some of the settings are redundant.

Compiling in Visual Studio resulted in

== Build: 26 succeeded, 0 failed, 0 up-to-date, 0 skipped ==

Sounds good to me. Unfortunately, MSVC seems not to share my optimism 
and complains about a missing file (screen capture attached).


Nothing else happens.

What I noticed is that the directory C:\LyX\lyx-23-install is empty. 
Aren't there some files supposed to be or what is the directory for?


Next, I copy the dependencies. The culprit is, however, that there is no 
lyx.exe in 
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin... so I 
can't execute it.


Maybe I am compiling it wrongly in MSVC? I just open the INSTALL project 
time in the explorer and hit STRG+F5.


(I think there are some typos in the INSTALL.Win32. I have attached 
corrections in brackets [].)


Daniel
Compiling LyX 2.3 for Win32 and creating Windows installer
==

It's recommended to compile LyX using Microsoft Visual C++ 2015 and CMake.


Compiling with Microsoft Visual C++
===

These instructions assume the LyX source code is in C:\LyX\lyx-23
You can also use another directory if you prefer.

1   Install MSVC 2015

If you don't have Visual C++ 2015 installed, get the free Community 
edition
from https://www.visualstudio.com/

2   Install Qt

Download the latest Qt for Open Source C++ development on Windows 
(VS2015)
from https://qt.io/download-open-source/
Qt 5.6.x is recommended, but 5.7.x or later versions should work as 
well.
Make sure that the bin subfolder of the Qt installation (e.g.
C:\Qt\Qt5.6.1\5.6\msvc2015\bin) is listed in the PATH environment 
variable.

3   Install Python

Install the latest Python 2.x or 3.x version from
https://www.python.org/downloads/

4   Install CMake

Install the latest CMake from http://www.cmake.org

5   Configure

- Open the "Developer Command Prompt for VS2015" from the
  "Visual Studio 2015\Visual Studio Tools" subfolder of the start menu.
  Run the CMake GUI from the command window that was opened.
  Alternatively, you can create a .bat file that first contains the line
  call "C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\vcvarsall.bat" x86
  and then calls the CMake GUI and use this .bat file to start CMake.
  The MSVC 2015 command prompt or vcvarsall.bat set some environment
  variables that are needed for CMake to find the compiler.

- Set the source code path to C:\LyX\lyx-23
  Set the build path to C:\LyX\lyx-23-build
  Click Configure and set the generator to Visual Studio 14.

- Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
  Pre-compiled dependencies will automatically be downloaded.

- Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
  C:\LyX\lyx-23-install and click Configure.

- Check the Advanced checkbox.
  Set GETTEXT_MSGFMT_EXECUTABLE to
  
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\gettext-tools\msgfmt.exe,
  and do the same for the other gettext tools.

- Click Generate.

6   Compile

A Microsoft Visual C++ solution should have been generated at
C:\LyX\lyx-23-build\lyx.sln
Compile the INSTALL project to get a LyX installation in
C:\LyX\lyx-23-install

7   Copy dependencies

Copy
- C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\bin
- 
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\imagemagick
- C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\python 
[Python?]
- 
C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\ghostscript
- C:\LyX\lyx-23-build\msvc2015-deps\lyx-windows-deps-msvc2015\Resources
to C:\LyX\lyx-23-install

And 

Re: lualatex with TL2016

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 16:46:01, schrieb Jürgen Spitzmüller 
> Am Samstag, den 09.07.2016, 15:18 +0200 schrieb Kornel Benko:
> > It meant that they compile without errors. Tested with A4 setting and
> > portrait.
> > 
> > Now retesting with landscape: Works too. Pdf output on screen fits.
> 
> OK, thanks again. I committed a slightly modified version.
> 
> Should also go to stable I suppose.

+1

> Jürgen
> 

Thanks for looking into this.

Kornel

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

Re: lualatex with TL2016

[Jürgen Spitzmüller]

Am Samstag, den 09.07.2016, 15:18 +0200 schrieb Kornel Benko:
> It meant that they compile without errors. Tested with A4 setting and
> portrait.
> 
> Now retesting with landscape: Works too. Pdf output on screen fits.

OK, thanks again. I committed a slightly modified version.

Should also go to stable I suppose.

Jürgen

> 
>   Kornel
> 

Re: toolbars Lock menu

[José Abílio Matos]

On Saturday, July 9, 2016 2:42:11 PM WEST racoon wrote:
> By the way, since I have never worked on a project like LyX, if anyone 
> has tips on how to work effectively, I am pleased to know. I guess using 
> git is one.

The first step is to read:
http://www.lyx.org/Development

where there are documents like:
http://www.lyx.org/DevFAQ

There are places that can help but those are a good first step.

Regards,
-- 
José Abílio

Re: lualatex with TL2016

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 14:47:59, schrieb Jürgen Spitzmüller 
> Am Samstag, den 09.07.2016, 14:40 +0200 schrieb Kornel Benko:
> > Works here with luatex 0.76, 0.80 and also with 0.95.
> 
> Thanks. "Works" means that the paper orientation in the pdf is correct
> in older luatex versions?
> 
> Jürgen

It meant that they compile without errors. Tested with A4 setting and portrait.

Now retesting with landscape: Works too. Pdf output on screen fits.

Kornel



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

Re: writing glosses in any KOMA-Script document class throws Class scrXXXX Error: undefined old font command '\it'

[Michael Berger]

On 07/08/2016 04:44 PM, Jürgen Spitzmüller wrote:

Am Freitag, den 08.07.2016, 15:08 +0200 schrieb Michael Berger:

A short while ago I had posted the user list on the Error: undefined
old font command '\it' (\rm).

As I wrote on lyx-users, the error is fixed in version 1.1 of
covington.sty which has been published yesterday:
http://www.ctan.org/pkg/covington

Please update to this version (with TeXLive, the new version should get
to you automatically when doing an update with the TeXLive manager).

Jürgen

Thanks Jürgen, it is done and works!
Michael

Re: lualatex with TL2016

[Jürgen Spitzmüller]

Am Samstag, den 09.07.2016, 14:40 +0200 schrieb Kornel Benko:
> Works here with luatex 0.76, 0.80 and also with 0.95.

Thanks. "Works" means that the paper orientation in the pdf is correct
in older luatex versions?

Jürgen

Re: toolbars Lock menu

[racoon]

On 09.07.2016 14:36, racoon wrote:

On 09.07.2016 13:48, Guillaume Munch wrote:

Le 08/07/2016 15:10, racoon a écrit :

On 08.07.2016 08:17, racoon wrote:

On 07.07.2016 14:41, racoon wrote:

Can someone give me a hint where LyX stores the individual toolbars'
properties, i.e. position and visibility.


Okay, got it (via QSettings). I was just a bit confused because the
visibility is also (somewhat) stored in the preferences file.


Okay, so here are my first thoughts on a toolbars position lock menu
entry. I know this is not an essential feature but I thought I could use
it to learn something about the LyX code without a deadline :). But
since it is non-essential don't worry if no one has time to help me with
this. Also I am not sure how much time I can invest in this in the
future. That might be another thought whether it is worth your time or
not.

Anyway, I am a beginner (both in C++ and Qt) and maybe someone can point
out my mistakes to me. Furthermore, I can't compile the source, so it's
all just on paper
(http://www.mail-archive.com/lyx-devel%40lists.lyx.org/msg195015.html).



Hi Daniel,

We can help you, but I would advise that you fix your compilation issues
first and that you send code in the patch format (e.g. git diff or git
format-patch). I do not think that any of us can do much with
approximate code that has does not compile.


Hi Guillaume,

Well, I was hoping it does compile. ;)

But I see that normally it will not - especially given my abilities.
Okay, I'll try to take care of the compilation first and then learn how
to use git properly. I guess in the (Windows?) git GUI the latter is just

1. fix the code directly in the directory where it was downloaded from
git, and

2. copy the stuff in the upper right text box (with yellow bar) which is
the "diff".


By the way, since I have never worked on a project like LyX, if anyone 
has tips on how to work effectively, I am pleased to know. I guess using 
git is one.

Re: lualatex with TL2016

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 13:52:16, schrieb Jürgen Spitzmüller 
> Am Samstag, den 09.07.2016, 12:13 +0200 schrieb Kornel Benko:
> > > \\pageheight\\paperheight
> > > \\pagewidth\\paperwidth
> > 
> > Looks good, but I am no expert. Maybe Günter or Jürgen could comment.
> > What about code in ERT or preamble with '\pdfsometing'?
> 
> I would prefer something like the attached (output code only for
> relevant backends). This uses the new luatex commands, but provides
> aliases for older versions.
> 
> Jürgen

Works here with luatex 0.76, 0.80 and also with 0.95.

Kornel

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

Re: toolbars Lock menu

[racoon]

On 09.07.2016 13:48, Guillaume Munch wrote:

Le 08/07/2016 15:10, racoon a écrit :

On 08.07.2016 08:17, racoon wrote:

On 07.07.2016 14:41, racoon wrote:

Can someone give me a hint where LyX stores the individual toolbars'
properties, i.e. position and visibility.


Okay, got it (via QSettings). I was just a bit confused because the
visibility is also (somewhat) stored in the preferences file.


Okay, so here are my first thoughts on a toolbars position lock menu
entry. I know this is not an essential feature but I thought I could use
it to learn something about the LyX code without a deadline :). But
since it is non-essential don't worry if no one has time to help me with
this. Also I am not sure how much time I can invest in this in the
future. That might be another thought whether it is worth your time or
not.

Anyway, I am a beginner (both in C++ and Qt) and maybe someone can point
out my mistakes to me. Furthermore, I can't compile the source, so it's
all just on paper
(http://www.mail-archive.com/lyx-devel%40lists.lyx.org/msg195015.html).



Hi Daniel,

We can help you, but I would advise that you fix your compilation issues
first and that you send code in the patch format (e.g. git diff or git
format-patch). I do not think that any of us can do much with
approximate code that has does not compile.


Hi Guillaume,

Well, I was hoping it does compile. ;)

But I see that normally it will not - especially given my abilities. 
Okay, I'll try to take care of the compilation first and then learn how 
to use git properly. I guess in the (Windows?) git GUI the latter is just


1. fix the code directly in the directory where it was downloaded from 
git, and


2. copy the stuff in the upper right text box (with yellow bar) which is 
the "diff".


Daniel

Re: Anonymous functions: replace bind with lambdas

[Guillaume Munch]

Le 06/07/2016 22:37, Stephan Witt a écrit :

Am 05.07.2016 um 21:39 schrieb Georg Baum :

Thanks. I am currently swamped with work, and this deserves a thorough look
so please be patient for a few days for my answer.


Sure



I’m not familiar with lambda expressions too.

But I can tell you it compiles and runs on Mac with your patch applied
(against c6ce76c2fbe88c7882935d6c1bf44a6247943b97 with one hunk manually
applied).



Thanks for the test.

Re: lualatex with TL2016

[Jürgen Spitzmüller]

Am Samstag, den 09.07.2016, 12:13 +0200 schrieb Kornel Benko:
> > \\pageheight\\paperheight
> > \\pagewidth\\paperwidth
> 
> Looks good, but I am no expert. Maybe Günter or Jürgen could comment.
> What about code in ERT or preamble with '\pdfsometing'?

I would prefer something like the attached (output code only for
relevant backends). This uses the new luatex commands, but provides
aliases for older versions.

Jürgendiff --git a/src/LaTeXFeatures.cpp b/src/LaTeXFeatures.cpp
index 16ec4c1..7a5a8fd 100644
--- a/src/LaTeXFeatures.cpp
+++ b/src/LaTeXFeatures.cpp
@@ -229,6 +229,13 @@ static docstring const papersizepdf_def = from_ascii(
 	"\\pdfpageheight\\paperheight\n"
 	"\\pdfpagewidth\\paperwidth\n");
 
+static docstring const papersizepdflua_def = from_ascii(
+	"% Backwards compatibility for LuaTeX < 0.90\n"
+	"\\providecommand\\pageheight{\\pdfpageheight}\n"
+	"\\providecommand\\pagewidth{\\pdfpagewidth}\n"
+	"\\pageheight\\paperheight\n"
+	"\\pagewidth\\paperwidth\n");
+
 static docstring const cedilla_def = from_ascii(
 	"\\newcommand{\\docedilla}[2]{\\underaccent{#1\\mathchar'30}{#2}}\n"
 	"\\newcommand{\\cedilla}[1]{\\mathpalette\\docedilla{#1}}\n");
@@ -1173,8 +1180,11 @@ docstring const LaTeXFeatures::getMacros() const
 	}
 
 	if (mustProvide("papersize")) {
-		if (runparams_.flavor == OutputParams::LATEX)
+		if (runparams_.flavor == OutputParams::LATEX
+		|| runparams_.flavor == OutputParams::DVILUATEX)
 			macros << papersizedvi_def << '\n';
+		else if  (runparams_.flavor == OutputParams::LUATEX)
+			macros << papersizepdflua_def << '\n';
 		else
 			macros << papersizepdf_def << '\n';
 	}

Re: toolbars Lock menu

[Guillaume Munch]

Le 08/07/2016 15:10, racoon a écrit :

On 08.07.2016 08:17, racoon wrote:

On 07.07.2016 14:41, racoon wrote:

Can someone give me a hint where LyX stores the individual toolbars'
properties, i.e. position and visibility.


Okay, got it (via QSettings). I was just a bit confused because the
visibility is also (somewhat) stored in the preferences file.


Okay, so here are my first thoughts on a toolbars position lock menu
entry. I know this is not an essential feature but I thought I could use
it to learn something about the LyX code without a deadline :). But
since it is non-essential don't worry if no one has time to help me with
this. Also I am not sure how much time I can invest in this in the
future. That might be another thought whether it is worth your time or not.

Anyway, I am a beginner (both in C++ and Qt) and maybe someone can point
out my mistakes to me. Furthermore, I can't compile the source, so it's
all just on paper
(http://www.mail-archive.com/lyx-devel%40lists.lyx.org/msg195015.html).



Hi Daniel,

We can help you, but I would advise that you fix your compilation issues
first and that you send code in the patch format (e.g. git diff or git
format-patch). I do not think that any of us can do much with 
approximate code that has does not compile.



Guillaume

Re: [LyX/master] Added missing ipa icons to distribution

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 12:41:28, schrieb Jürgen Spitzmüller 
> Am Mittwoch, den 15.06.2016, 15:04 +0200 schrieb Kornel Benko:
> > commit 43d284e15ad6193da2508a57b5260cb85ff4cdb9
> > Author: Kornel Benko 
> > Date:   Wed Jun 15 15:03:55 2016 +0200
> > 
> > Added missing ipa icons to distribution
> 
> This should go to branch as well (also 60a1827b65).
> 
> Jürgen

Done at 53425c7 and 35a78ae.

Kornel

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

Re: [LyX/master] Added missing ipa icons to distribution

[Jürgen Spitzmüller]

Am Mittwoch, den 15.06.2016, 15:04 +0200 schrieb Kornel Benko:
> commit 43d284e15ad6193da2508a57b5260cb85ff4cdb9
> Author: Kornel Benko 
> Date:   Wed Jun 15 15:03:55 2016 +0200
> 
> Added missing ipa icons to distribution

This should go to branch as well (also 60a1827b65).

Jürgen

Re: Problems with LaTeX extensions in fresh install on Mac OS El Capitan

[Cyrille Artho]

Cyrille Artho wrote:

Hi all,
I've just installed LyX on a new MacBook Pro. HiRes works well, but LyX
can't find any LaTeX class/style files in texmf-local, no matter what I try.

I've tried both the fink latex installation and Mac ports. On the latter,
custom files go into, for example

/opt/local/share/texmf-local/tex/latex/springer/llncs.cls

latex can find the files, and they're in ls-R generated by texhash, but LyX
can't see them for some reason.

What went wrong here? I've tried fresh installations in the past (up to LyX
2.1), on previous versions of Mac OS, and never had this issue.


I was able to resolve this by logging in again, and by running texhash 
multiple times. At some point LyX was able to compile the files, and show 
the right paths under "Tools/TeX information", but "Help/LaTeX 
configuration" shows the classes in question as missing.


Another restart (or a few) later and it worked. Good to have this resolved 
but this was very erratic.

--
Regards,
Cyrille Artho - http://artho.com/
The human mind treats a new idea the way the body treats
a strange protein -- it rejects it.
-- P. Medawar

Re: lualatex with TL2016

[Kornel Benko]

Am Freitag, 8. Juli 2016 um 22:05:57, schrieb Scott Kostyshak 
> On Sat, Jul 09, 2016 at 12:38:53AM +0200, Kornel Benko wrote:
> > Am Freitag, 8. Juli 2016 um 18:14:29, schrieb Scott Kostyshak 
> > 
>
> > ATM, the patch I have works for me.
>
> It is better than the patch I originally proposed. It is unfortunate to
> add a sizeable chunk of LaTeX, but I don't see see an alternative (from
> what I understand, in LyX we don't even track the LuaTeX version so we
> cannot do the contionals with C++ code. Further, even if we did have
> that information I wonder if we would still choose the LaTeX
> conditionals as you propose because this way exported LaTeX code will be
> valid if compiled on older LuaTeX engines).
>
> I have two comments below.
>
> > diff --git a/src/LaTeXFeatures.cpp b/src/LaTeXFeatures.cpp
> > index 16ec4c1..602dd5f 100644
> > --- a/src/LaTeXFeatures.cpp
> > +++ b/src/LaTeXFeatures.cpp
> > @@ -226,8 +226,18 @@ static docstring const papersizedvi_def = from_ascii(
> > "\\special{papersize=\\the\\paperwidth,\\the\\paperheight}\n");
> >
>
> Should we put a comment here, perhaps to this email thread?
> // https://www.mail-archive.com/search?l=mid75450.Hf17PhF3sW%40amd64

OK, done.

> >  static docstring const papersizepdf_def = from_ascii(
> > -   "\\pdfpageheight\\paperheight\n"
> > -   "\\pdfpagewidth\\paperwidth\n");
> > +   "\\RequirePackage{ifluatex}\n"
> > +   "\\ifluatex\n"
> > +   "  \\ifdim\\luatexversion pt> 94 pt\n"
> > +   "\\usepackage{luatex85}\n"
>
> Instead of relying on the luatex85 package, which is meant to only be a
> temporary fix, I wonder if we can already implement something more
> permanent. So instead of the above line, can we just put the following?
>
> \\pageheight\\paperheight
> \\pagewidth\\paperwidth

Looks good, but I am no expert. Maybe Günter or Jürgen could comment.
What about code in ERT or preamble with '\pdfsometing'?

> as described as the "pure luatex syntax (from 0.85 on is)" [1]. Further,
> I imagine it is more efficient to execute those commands than to load
> another package.
>
> Scott
>
> [1] https://www.mail-archive.com/luatex@tug.org/msg05793.html

Korneldiff --git a/src/LaTeXFeatures.cpp b/src/LaTeXFeatures.cpp
index 16ec4c1..dc1fc00 100644
--- a/src/LaTeXFeatures.cpp
+++ b/src/LaTeXFeatures.cpp
@@ -225,7 +225,15 @@ static docstring const lyxmathsym_def = from_ascii(
 static docstring const papersizedvi_def = from_ascii(
 	"\\special{papersize=\\the\\paperwidth,\\the\\paperheight}\n");

+// See also this email thread
+// https://www.mail-archive.com/search?l=mid75450.Hf17PhF3sW%40amd64
 static docstring const papersizepdf_def = from_ascii(
+	"\\RequirePackage{ifluatex}\n"
+	"\\ifluatex\n"
+	"  \\ifdim\\luatexversion pt> 94 pt\n"
+	"\\usepackage{luatex85}\n"
+	"  \\fi\n"
+	"\\fi\n"
 	"\\pdfpageheight\\paperheight\n"
 	"\\pdfpagewidth\\paperwidth\n");



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

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Kornel Benko]

Am Samstag, 9. Juli 2016 um 04:09:30, schrieb Enrico Forestieri 
> I came up with the attached patch that solves the issue for me.
> It requires the Qt5X11Extras module, which is not mandatory, though.
> The patch simply tries to refresh the timestamp of the selection request.
> I still get the warning from Qt5 (even if only once), but the paste by the
> middle mouse button succeeds anyway. Recall that this issue does not occur
> with a focus-follows-mouse policy. Given that it also does not occur with
> some applications, I don't know who is to blame for this.
>
> The patch is for Qt5 and autotools only (I don't know cmake, sorry).
>

Attached.

Kornel

signature.asc
Description: This is a digitally signed message part.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 76cbdde..e39fc59 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -929,6 +929,7 @@ set(QPA_XCB)
 if(Qt5X11Extras_FOUND AND QT_USES_X11)
   # QPA_XCB is only valid if QT5+X11
   set(QPA_XCB 1)
+  set(HAVE_QT5_X11_EXTRAS 1)
 endif()
 configure_file(${LYX_CMAKE_DIR}/config.h.cmake ${TOP_BINARY_DIR}/config.h)
 
diff --git a/development/cmake/config.h.cmake b/development/cmake/config.h.cmake
index 253d39f..95148b6 100644
--- a/development/cmake/config.h.cmake
+++ b/development/cmake/config.h.cmake
@@ -73,6 +73,9 @@
 // Defined if QT=QT5 uses X11
 #cmakedefine QPA_XCB 1
 
+// Define if you have the Qt5X11Extras module
+#cmakedefine HAVE_QT5_X11_EXTRAS 1
+
 ${Include_used_spellchecker}
 
 #cmakedefine AIKSAURUSLIB_FOUND 1

Re: installing lyx 2.2.0

[Michael Berger]

On 07/08/2016 06:33 PM, Pavel Sanda wrote:

Michael Berger wrote:

Hi,
'make' returns errors as per screenshots.

Could somebody help?
Thanks,
Michael
Just to make sure - you started compiling from _clean_ tree where no 
previous experiments/compilations were done, correct? 
Thanks Pavel, yes I definitely did with the very first installation. But 
after that I lost somehow control.
Meanwhile my problem is solved and lyx 2.2.0 is running (although I 
might have to do some minor adjustments in some of my old files made 
with TL2013 and Lyx 2.1).


Don't ask me how exactly this was accomplished. I reckon there must have 
been other obstacles from previous failed attempts that 
overlapped/interfered with the installation. Furthermore, one or two 
proposals made by users may perhaps have been counterproductive.


When Jürgen informed that he took over maintenance of covington and made 
some necessary fixes I made a fresh attempt last night. I removed 
everything that could have to do with LyX 2.1, Tex Live etc. installed 
by Mageia's software manger and started to install Lyx 2.2.0 as 
administrator. The installation ran through without complaints.
Sorry for the efforts you took and your time invested - but in lack of 
knowledge my strength is just doggedness and motivation.



Michael

Problems with LaTeX extensions in fresh install on Mac OS El Capitan

[Cyrille Artho]

Hi all,
I've just installed LyX on a new MacBook Pro. HiRes works well, but LyX 
can't find any LaTeX class/style files in texmf-local, no matter what I try.


I've tried both the fink latex installation and Mac ports. On the latter, 
custom files go into, for example


/opt/local/share/texmf-local/tex/latex/springer/llncs.cls

latex can find the files, and they're in ls-R generated by texhash, but LyX 
can't see them for some reason.


What went wrong here? I've tried fresh installations in the past (up to LyX 
2.1), on previous versions of Mac OS, and never had this issue.

--
Regards,
Cyrille Artho - http://artho.com/
Solitude is an illusion, for every silence is filled
by a clamorous search for meaning.
-- Steven Erikson, "House of Chains"

Re: Annoying terminal messages: QXcbClipboard: SelectionRequest too old

[Scott Kostyshak]

On Sat, Jul 09, 2016 at 04:09:30AM +0200, Enrico Forestieri wrote:
> 
> I had a closer look at this issue. First of all, it occurs with both
> Qt4 and Qt5, the only difference being that Qt5 prints a warning.
> Then, it does not occur with all applications. I can reproduce with
> gnome-terminal and gedit, but cannot reproduce with gvim, for example.
> It only occurs after selecting something in lyx and trying to paste to
> another application for the first time. Then the paste succeeds on a
> second attempt, even if the window has not the focus anymore. However,
> selecting something else in lyx, it starts over again.

I see similar behavior.

> I came up with the attached patch that solves the issue for me.

Thanks for working on this.

> It requires the Qt5X11Extras module, which is not mandatory, though.
> The patch simply tries to refresh the timestamp of the selection request.
> I still get the warning from Qt5 (even if only once), but the paste by the
> middle mouse button succeeds anyway. Recall that this issue does not occur
> with a focus-follows-mouse policy. Given that it also does not occur with
> some applications, I don't know who is to blame for this.

I tested the patch and can reproduce your findings. The first paste now
works. As you mentioned, I still get the warning, but only one warning
where without the patch I get three warnings.

I tried a few random variations on your patch to squash the last
warning. One that worked for me is to add

  return true;

after

  xcb_flush(con);

I have no idea if that makes any sense but perhaps it provides a clue.
Does the warning go away if you add that?

Finally, this doesn't seem to solve the flood of messages I get when
CopyQ is running, but I don't think this is worth investigating.

Scott


signature.asc
Description: PGP signature