On 06/01/2016 03:08 PM, Georg Baum wrote:
> Richard Heck wrote:
>
>> commit 4eb3ed96e53ab0eb2af519caa6125cac79c823ad
>> Author: Richard Heck
>> Date: Wed Jun 1 12:31:48 2016 -0400
>>
>> Update lyx2lyx from 2.2.0. This is in preparation for the 2.1.5
>> release.
>>
>> diff --git a/lib/lyx
Richard Heck wrote:
> commit 4eb3ed96e53ab0eb2af519caa6125cac79c823ad
> Author: Richard Heck
> Date: Wed Jun 1 12:31:48 2016 -0400
>
> Update lyx2lyx from 2.2.0. This is in preparation for the 2.1.5
> release.
>
> diff --git a/lib/lyx2lyx/LyX.py b/lib/lyx2lyx/LyX.py
> index 7e52238..1
jpc wrote:
> commit e9cc60a5be1c833731d516ef1be9802241fa161b
> Author: jpc
> Date: Sat Apr 16 09:18:35 2016 +0100
Welcome on board Jean-Pierre!
Pavel
Am 24.02.2016 um 18:20 schrieb Guillaume Munch:
commit bc858ab69d0b3ab4a822b1efee4b32fa2ff720d3
Author: Guillaume Munch
The entry in status.21x is missing.
regards Uwe
Am Donnerstag, 11. Februar 2016 um 18:07:06, schrieb Jean-Marc Lasgouttes
> Le 24/01/2016 15:53, Richard Heck a écrit :
> > On 01/24/2016 07:04 AM, Georg Baum wrote:
> >> Looks like http://www.lyx.org/trac/changeset/21541a07/lyxgit and
> >> http://www.lyx.org/trac/changeset/a25c946b/lyxgit have t
Le 24/01/2016 15:53, Richard Heck a écrit :
On 01/24/2016 07:04 AM, Georg Baum wrote:
Looks like http://www.lyx.org/trac/changeset/21541a07/lyxgit and
http://www.lyx.org/trac/changeset/a25c946b/lyxgit have to be backported as
well.
OK.
The autoconf version (a25c946b) has already been backpor
Le 03/02/2016 15:53, Jean-Marc Lasgouttes a écrit :
commit ef81af703737c6ccdaac8d098b56c2548133363d
Author: Georg Baum
Date: Sat May 16 00:05:23 2015 +0200
Fix compilation with boost 1.60
Oops, I did not indend to commit this right now. Richard, do you want me
to revert? I am pretty c
On 01/24/2016 07:04 AM, Georg Baum wrote:
> Uwe Stöhr wrote:
>
>> After the recent boost update in 2.1.x branch I get now many of these
>> warnings:
>>
>> GraphicsCache.cpp
>> CL : warning : Boost.Signals is no longer being maintained and is now
>> depre
Uwe Stöhr wrote:
> After the recent boost update in 2.1.x branch I get now many of these
> warnings:
>
> GraphicsCache.cpp
> CL : warning : Boost.Signals is no longer being maintained and is now
> deprecated. Please switch to Boost.Signals2. To disable this warning
After the recent boost update in 2.1.x branch I get now many of these
warnings:
GraphicsCache.cpp
CL : warning : Boost.Signals is no longer being maintained and is now
deprecated. Please switch to Boost.Signals2. To disable this warning
message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING
On 09/13/2015 07:58 PM, Guillaume Munch wrote:
commit d186d708ea0bb80f6f62942732d503dda4455dc2
Author: Guillaume Munch
Date: Sat Aug 29 03:38:54 2015 +0100
Fix bug #1996
\overrightarrow and related macros have a standard behaviour with respect to
sub/superscripts.
Very
On Sun, Aug 16, 2015 at 5:19 AM, Kornel Benko wrote:
> commit ac9af80cfb2dea589e4eeb8212616acd33815f92
> Author: Kornel Benko
> Date: Sun Aug 16 11:17:02 2015 +0200
>
> Cmake build: Make use of QT5 available (again).
I can now compile with Qt 5. Thanks, Kornel.
Scott
gt; >> > Hm, the cache is from a QT5-master configuration. I was under the
> >> > impression of failed 2.1.
> >>
> >> Yes it is for Qt5, but Qt5 has been working for me with 2.1.x for a
> >> long time. Strange. But I suppose it is not worth the time t
impression of failed 2.1.
>>
>> Yes it is for Qt5, but Qt5 has been working for me with 2.1.x for a
>> long time. Strange. But I suppose it is not worth the time to figure
>> this out.
>>
>
> 2.1.x is not supposed to work with QT5 IMHO. AT least, I only tried to
Am Samstag, 15. August 2015 um 16:49:58, schrieb Scott Kostyshak
> On Sat, Aug 15, 2015 at 4:35 PM, Kornel Benko wrote:
>
> > Hm, the cache is from a QT5-master configuration. I was under the
> > impression of failed 2.1.
>
> Yes it is for Qt5, but Qt5 has been worki
On Sat, Aug 15, 2015 at 4:35 PM, Kornel Benko wrote:
> Hm, the cache is from a QT5-master configuration. I was under the impression
> of failed 2.1.
Yes it is for Qt5, but Qt5 has been working for me with 2.1.x for a
long time. Strange. But I suppose it is not worth the time to figure
th
I do a fresh build (i.e. remove build dir, then create empty build
> dir) then cache should not be wrong right?
>
> > > I'm guessing this is a problem in configuration on my side. Does
> > > anyone have a suggestion for how I can fix this? Note that 2.1.x
> > &
guessing this is a problem in configuration on my side. Does
> > anyone have a suggestion for how I can fix this? Note that 2.1.x
> > before this commit compiles fine, and master branch compiles fine for
> > me.
>
> You compile master with QT5?
Yes.
Attached is my C
;libqt4-dev'
Maybe your cache is wrong?
> I'm guessing this is a problem in configuration on my side. Does
> anyone have a suggestion for how I can fix this? Note that 2.1.x
> before this commit compiles fine, and master branch compiles fine for
> me.
You compile master with QT5?
> Scott
Kornel
signature.asc
Description: This is a digitally signed message part.
ror
/home/scott/lyxbuilds/master-DELETE/repo/src/graphics/PreviewLoader.h:23:19:
fatal error: QObject: No such file or directory
#include
^
compilation terminated.
I'm guessing this is a problem in configuration on my side. Does
anyone have a suggestion for how I can fix this? No
Le 22/06/2015 15:43, Cor Blom a écrit :
My problem has disappeared with updated packages. So never mind. Sorry
for the noise.
Don't be sorry, don't hesitate to send bug reports our way.
JMarc
My problem has disappeared with updated packages. So never mind. Sorry
for the noise.
Cor
Op 22-06-15 om 09:16 schreef Cor Blom:
Hi,
openSUSE Factory/Tumbleweed now has boost 1.58. We build lyx against
system boost and for 2.1.3 this fails now because of boost. In master
this has been fixed,
Hi,
openSUSE Factory/Tumbleweed now has boost 1.58. We build lyx against
system boost and for 2.1.3 this fails now because of boost. In master
this has been fixed, is it possible to backport this to branch?
If this is too complicated then I'll just build with internal boost
until 2.2.
Than
Am Montag, 15. Juni 2015 um 00:59:06, schrieb Uwe Stöhr
> Am 09.06.2015 um 09:07 schrieb Kornel Benko:
>
> > This is only valid if you use 'make', which you doesn't.
> > For you (since you use visual studio + cmake) it should be
> > # msbuild /t:layouttranslations1
> > from the build director
Am 09.06.2015 um 09:07 schrieb Kornel Benko:
This is only valid if you use 'make', which you doesn't.
For you (since you use visual studio + cmake) it should be
# msbuild /t:layouttranslations1
from the build directory.
Many thanks Kornel,
but this does also not work. What I now did i
On 06/09/2015 02:31 PM, Georg Baum wrote:
Uwe Stöhr wrote:
Why do we have a single pt_BR translation in layouttranslations in the
2.1.x branch if a modification is not allowed.
pt_BR is new in branch for LyX 2.1.4 so there was definitely a change of
the file.
No. The last change was at
Uwe Stöhr wrote:
> Why do we have a single pt_BR translation in layouttranslations in the
> 2.1.x branch if a modification is not allowed.
> pt_BR is new in branch for LyX 2.1.4 so there was definitely a change of
> the file.
No. The last change was at bdc1271c3905, which was befo
+ cmake) it should be
# msbuild /t:layouttranslations1
from the build directory.
> What does it mean? Should i go to the folder "po" and then execute this
> as command line command? This does not work here.
>
> Why do we have a single pt_BR translation in layouttranslati
tes I should run
"make ../lib/layouttranslations' in po"
What does it mean? Should i go to the folder "po" and then execute this
as command line command? This does not work here.
Why do we have a single pt_BR translation in layouttranslations in the
2.1.x branch if
Uwe Stöhr wrote:
> commit 407d5bf228a8fd297aedc933b396a10e976df09b
> Author: Uwe Stöhr
> Date: Thu Jun 4 01:12:12 2015 +0200
>
> layouttranslations: Arabic update by Hatim
It is forbidden to update layouttranslations in a stable release, and if an
update is done in master it must not be
Am 06.04.2015 um 01:07 schrieb Uwe Stöhr:
Second error:...
This problem persists. I can therefore not compile LyX 2.1.x branch.
I can verify the problem on another PC with a fresh checkout and clean
build tree.
I am lost since i not even understand what the error message tries to
tell me
s problem has gone after cleaning the build tree again.
Second error:
> C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5):
error MSB3073: The command "setlocal\r
[D:\LyXGit\2.1.x\compile-result\INSTALL.vcxproj]
C:\Program Files
(x86)\MSBui
> (x86)/LyX/Resources/bind/..
> Maybe need administrative privileges.
>
> I don't compile LyX in this directory but in
> D:\LyXGit\Master\compile-result
> The path
> D:\LyXGit\2.1.x\compile-result
> does simple not exist in my system and I don't know why CMake
ompile LyX in this directory but in
D:\LyXGit\Master\compile-result
The path
D:\LyXGit\2.1.x\compile-result
does simple not exist in my system and I don't know why CMake tries to
access a non-existing directory.
Second error:
> C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Microso
On Sat, Feb 14, 2015 at 7:12 PM, Georg Baum
wrote:
> Liviu Andronic wrote:
>
> > Hi Georg,
> >
> > While we're at it, can we add similar converters (for both pdfcrop and
> > 150dpi) for the ps2pdf path? In some instances, like when using PSTricks,
> > users must pass by this path to obtain the fi
Liviu Andronic wrote:
> Hi Georg,
>
> While we're at it, can we add similar converters (for both pdfcrop and
> 150dpi) for the ps2pdf path? In some instances, like when using PSTricks,
> users must pass by this path to obtain the final PDF. If it's not onerous
> for our menus, it may be worth add
f formats
since any given document either uses TeX fonts or not. For the
same reason
I also added an additional converter to PDF (cropped).
added:
lib/scripts/convert_pdf.py
modified:
lib/Makefile.am
lib/configure.py
status.21x
--
lp:~l
ed:
> lib/Makefile.am
> lib/configure.py
> status.21x
>
>
> --
> lp:~lyx-devel/lyx/stable-2.1.x
> https://code.launchpad.net/~lyx-devel/lyx/stable-2.1.x
>
> You are subscribed to branch lp:~lyx-devel/lyx/stable-2.1.x.
> To unsubscribe from this branch go to
>
Le 08/12/2014 12:56, Jürgen Spitzmüller a écrit :
Jean-Marc Lasgouttes wrote:
commit 53436891f79150cdb053b52dfd38540b9652c9cc
Author: Jean-Marc Lasgouttes
Date: Fri Nov 14 14:53:11 2014 +0100
Let the Foot inset have a different Layout when inside a title
Status entry is missing.
Tha
Jean-Marc Lasgouttes wrote:
> commit 53436891f79150cdb053b52dfd38540b9652c9cc
> Author: Jean-Marc Lasgouttes
> Date: Fri Nov 14 14:53:11 2014 +0100
>
> Let the Foot inset have a different Layout when inside a title
Status entry is missing.
Jürgen
Am Donnerstag, 25. September 2014 um 00:23:29, schrieb Uwe Stöhr
> commit 53fb8f28a5333a5e703eb7564dd9e97eba1844ca
> Author: Uwe Stöhr
> Date: Thu Sep 25 00:23:23 2014 +0200
>
> Install.cmake: add missing subfolder "\templates\springer"
>
> diff --git a/development/cmake/Install.cmake b/d
On 09/02/2014 02:34 PM, Kornel Benko wrote:
Am Dienstag, 2. September 2014 um 20:26:43, schrieb Kornel Benko
Am Dienstag, 2. September 2014 um 19:47:07, schrieb Richard Heck
commit 7008df54386ce0cea0169d60c5abf5dee3b93bc5
Author: Richard Heck
Date: Tue Sep 2 13:46:45 2014 -0400
New
Am Dienstag, 2. September 2014 um 20:26:43, schrieb Kornel Benko
> Am Dienstag, 2. September 2014 um 19:47:07, schrieb Richard Heck
>
> > commit 7008df54386ce0cea0169d60c5abf5dee3b93bc5
> > Author: Richard Heck
> > Date: Tue Sep 2 13:46:45 2014 -0400
> >
> > New Polish translation from
Am Dienstag, 2. September 2014 um 19:47:07, schrieb Richard Heck
> commit 7008df54386ce0cea0169d60c5abf5dee3b93bc5
> Author: Richard Heck
> Date: Tue Sep 2 13:46:45 2014 -0400
>
> New Polish translation from Michal.
>
This is not compilable.
...
msgid ""
"The module %1$s requires a packag
On 06/13/2014 03:36 PM, Georg Baum wrote:
Richard Heck wrote:
On 06/10/2014 11:35 AM, Pavel Sanda wrote:
Richard Heck wrote:
On 06/10/2014 02:50 AM, Pavel Sanda wrote:
Richard Heck wrote:
There are some issues (e.g, with symlinks)
So are the symlinks preserved or not with this patch?
The
Richard Heck wrote:
> On 06/10/2014 11:35 AM, Pavel Sanda wrote:
>> Richard Heck wrote:
>>> On 06/10/2014 02:50 AM, Pavel Sanda wrote:
Richard Heck wrote:
> There are some issues (e.g, with symlinks)
So are the symlinks preserved or not with this patch?
>>> The exact same thing happe
On 06/10/2014 11:35 AM, Pavel Sanda wrote:
Richard Heck wrote:
On 06/10/2014 02:50 AM, Pavel Sanda wrote:
Richard Heck wrote:
There are some issues (e.g, with symlinks)
So are the symlinks preserved or not with this patch?
The exact same thing happens as if backups are enabled and the save f
Richard Heck wrote:
> On 06/10/2014 02:50 AM, Pavel Sanda wrote:
>> Richard Heck wrote:
>>> There are some issues (e.g, with symlinks)
>> So are the symlinks preserved or not with this patch?
>
> The exact same thing happens as if backups are enabled and the save fails:
> If the save works, the ne
On 06/10/2014 02:50 AM, Pavel Sanda wrote:
Richard Heck wrote:
There are some issues (e.g, with symlinks)
So are the symlinks preserved or not with this patch?
The exact same thing happens as if backups are enabled and the save
fails: If the save works, the new file is still a symlink; if th
Richard Heck wrote:
> There are some issues (e.g, with symlinks)
So are the symlinks preserved or not with this patch?
Pavel
figures out to what name we should backup the original file.
So this seems about as safe as it could be.
The reason we need this patch for 2.1.x is that the more sophisticated
approach needs more refinement, and testing, that it can get before 2.1.1.
Here's a summary of what this patch does
The merge of 2.1.1-staging into 2.1.x has been completed. The 2.1.x.
branch is now open, under the usual rules for committing to what,
henceforth, will be known as "stable".
Richard
On 04/18/2014 11:10 AM, Vincent van Ravesteijn wrote:
Op 18 apr. 2014 16:43 schreef "Richard Heck" <mailto:rgh...@lyx.org>>:
>
>
> The 2.1.x branch has now been created, but please do not commit to
it yet. I need to merge 2.1.1-staging, and that is turning
Op 18 apr. 2014 16:43 schreef "Richard Heck" :
>
>
> The 2.1.x branch has now been created, but please do not commit to it
yet. I need to merge 2.1.1-staging, and that is turning out to be a hassle,
due to conflicts in the documentation files.
>
> Richard
>
You can
The 2.1.x branch has now been created, but please do not commit to it
yet. I need to merge 2.1.1-staging, and that is turning out to be a
hassle, due to conflicts in the documentation files.
Richard
On 04/11/2014 12:21 PM, Kornel Benko wrote:
Am Freitag, 11. April 2014 um 18:12:27, schrieb Richard Heck
> commit 7cdfa9b29a8a74f62fa722a4282d08db43f4f0b3
> Author: Richard Heck
> Date: Fri Apr 11 12:09:54 2014 -0400
>
> Better idea: Let's allow export of 2.1.x
Am Freitag, 11. April 2014 um 18:12:27, schrieb Richard Heck
> commit 7cdfa9b29a8a74f62fa722a4282d08db43f4f0b3
> Author: Richard Heck
> Date: Fri Apr 11 12:09:54 2014 -0400
>
> Better idea: Let's allow export of 2.1.x files. Someone might want to
> do that. But
On 04/11/2014 11:54 AM, Vincent van Ravesteijn wrote:
On Fri, Apr 11, 2014 at 5:50 PM, Richard Heck wrote:
commit d41d84f0b8c3cc10154145d86a3c5e9536b6b643
Author: Richard Heck
Date: Fri Apr 11 11:49:54 2014 -0400
Remove 21x export. LyX 2.1.x already reads 2.0.x files.
+\Format
On Fri, Apr 11, 2014 at 5:50 PM, Richard Heck wrote:
> commit d41d84f0b8c3cc10154145d86a3c5e9536b6b643
> Author: Richard Heck
> Date: Fri Apr 11 11:49:54 2014 -0400
>
> Remove 21x export. LyX 2.1.x already reads 2.0.x files.
>
>
>>> +\F
On 04/11/2014 11:48 AM, Vincent van Ravesteijn wrote:
On Fri, Apr 11, 2014 at 5:42 PM, Richard Heck wrote:
commit 8c3d6f717893b091ae2b461a5b08f4bc77f84691
Author: Richard Heck
Date: Fri Apr 11 11:41:56 2014 -0400
Allow 2.0.8 to read and write 2.1.x files. Also incorporates some
On Fri, Apr 11, 2014 at 5:42 PM, Richard Heck wrote:
> commit 8c3d6f717893b091ae2b461a5b08f4bc77f84691
> Author: Richard Heck
> Date: Fri Apr 11 11:41:56 2014 -0400
>
> Allow 2.0.8 to read and write 2.1.x files. Also incorporates some
> bugfixes in lyx2lyx that
61 matches
Mail list logo
