Re: status update on the export tests

On 2015-10-26, Scott Kostyshak wrote: > OK. I just want to make sure we define "there are no regressions". These > tests passed before edd37de8. So it is quite possible that documents > that users have that compile with LyX 2.1.x suddenly fail to compile > with LyX 2.2.0 because of edd37de8. In th

Re: status update on the export tests

Am Montag, 26. Oktober 2015 um 09:13:44, schrieb Stephan Witt ... > > These tests fails because of language switching done with polyglossia, but > > I'm not sure what the root problem is: > > export/doc/fr/UserGuide_pdf5_systemF > > export/examples/fr/Foils_pdf5_systemF > > # kluwer gives the fol

Re: status update on the export tests

Am 25.10.2015 um 05:29 schrieb Scott Kostyshak : > Dear all, > > There seems to be more interest in running the export tests. This is great and > will encourage me to improve the (shamefully lacking) documentation for these > tests. > > First, I am focusing on the test results after reverting (l

Re: [patch] update modernCV layout file

On Mon, Oct 26, 2015 at 03:50:43AM +0100, Uwe Stöhr wrote: > The attached patch adds support for the modernCV features introduced by > version 1.5 from April 2013. > > I think it is safe enough to support 2 years old features and would > therefore like to put it in. Do we have any policy on this?

Re: status update on the export tests

On Sun, Oct 25, 2015 at 11:10:56AM +0100, Georg Baum wrote: > Scott Kostyshak wrote: > > > The following tests are currently expected to fail because of issues with > > nested language handling and polyglossia. Georg, if you still have > > interest and time for fixing this type of issue, take a lo

[patch] update modernCV layout file

The attached patch adds support for the modernCV features introduced by version 1.5 from April 2013. I think it is safe enough to support 2 years old features and would therefore like to put it in. Since a style is added, this would be a simple fileformat change. OK to go on? regards Uwe di

Re: status update on the export tests

Scott Kostyshak wrote: > The following tests are currently expected to fail because of issues with > nested language handling and polyglossia. Georg, if you still have > interest and time for fixing this type of issue, take a look at these: > > export/doc/nb/Intro_pdf5_systemF > export/doc/sk/Int

status update on the export tests

Dear all, There seems to be more interest in running the export tests. This is great and will encourage me to improve the (shamefully lacking) documentation for these tests. First, I am focusing on the test results after reverting (locally) two commits, as follows: git revert --no-edit 664ef2c

Re: Update on the patches

Le 23/10/2015 09:54, Jean-Marc Lasgouttes a écrit : Le 20/10/2015 19:23, Guillaume Munch a écrit : http://www.emacswiki.org/emacs/SmartTabs Indeed, thanks. Do you use it? JMarc Not yet because it does not seem straightforward to install here, but I am convinced that Georg's solution is t

Re: Update on the patches

Le 20/10/2015 19:23, Guillaume Munch a écrit : http://www.emacswiki.org/emacs/SmartTabs Indeed, thanks. Do you use it? JMarc

Re: Update on the patches

Le 09/10/2015 22:07, Jean-Marc Lasgouttes a écrit : Le 09/10/2015 22:06, Georg Baum a écrit : Even more interesting. I always thought that LyX uses the "use tabs for logical indentation, and spaces for visual alignment" model for C++ code. This way, it does not matter at all whether you display

Re: Update on the patches

Le 09/10/2015 22:06, Georg Baum a écrit : Even more interesting. I always thought that LyX uses the "use tabs for logical indentation, and spaces for visual alignment" model for C++ code. This way, it does not matter at all whether you display a tab as 4 or 8 spaces wide or anything else, and thi

Re: Update on the patches

Guillaume Munch wrote: > Le 01/10/2015 00:43, Pavel Sanda a écrit : > >> This is interesting, I thought default tab is 8 and always >> edited our sources this way. Kind of surprising that we didn't >> conflicted yet about the visual appearance of indented blocks, >> like in void ViewSourceWidget::

Re: Update on the patches

Le 01/10/2015 00:43, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: Le 15/09/2015 17:54, Guillaume Munch a écrit : I can remove more irrelevant parts and do that, but before that I am hoping to get some better configuration if anybody else is using emacs. BSD is just close to your style; the

Re: Update on the patches

Jean-Marc Lasgouttes wrote: > Le 15/09/2015 17:54, Guillaume Munch a écrit : >> I can remove more irrelevant parts and do that, but before that I am >> hoping to get some better configuration if anybody else is using emacs. >> BSD is just close to your style; the question is more: what is the >> pr

Re: Update on the patches

On 09/27/2015 11:47 PM, Guillaume Munch wrote: Le 28/09/2015 04:31, Guillaume Munch a écrit : Le 13/09/2015 22:28, Richard Heck a écrit : On 09/12/2015 09:31 PM, Guillaume Munch wrote: MathData::updateMacros() breaks text selection and search/replace : I

Re: Update on the patches

Le 15/09/2015 17:54, Guillaume Munch a écrit : I can remove more irrelevant parts and do that, but before that I am hoping to get some better configuration if anybody else is using emacs. BSD is just close to your style; the question is more: what is the proper style to use? Personally, I have

Re: Update on the patches

Le 28/09/2015 04:31, Guillaume Munch a écrit : Le 13/09/2015 22:28, Richard Heck a écrit : On 09/12/2015 09:31 PM, Guillaume Munch wrote: MathData::updateMacros() breaks text selection and search/replace : I believe that these two calls to clearSelection()

Re: Update on the patches

Le 13/09/2015 22:28, Richard Heck a écrit : On 09/12/2015 09:31 PM, Guillaume Munch wrote: MathData::updateMacros() breaks text selection and search/replace : I believe that these two calls to clearSelection() are not (or no longer) useful. I am very happy

Re: Update on the patches

Le 15/09/2015 17:49, Guillaume Munch a écrit : Le 14/09/2015 08:53, Jean-Marc Lasgouttes a écrit : * Where should I commit po files? I vaguely remember reading somewhere that these should be against stable, do I remember correctly and in that case is it better to commit to master at the same t

Re: Update on the patches

Le 14/09/2015 08:53, Jean-Marc Lasgouttes a écrit : * Where should I commit po files? I vaguely remember reading somewhere that these should be against stable, do I remember correctly and in that case is it better to commit to master at the same time? In general the po files of master are rei

Re: Update on the patches

Le 14/09/2015 09:03, Jean-Marc Lasgouttes a écrit : Le 14/09/2015 02:22, Guillaume Munch a écrit : One thing that would have helped was to have emacs configuration files with the correct coding style that you use. For instance my .emacs now reads (omitting irrelevant parts): Such information

Re: Update on the patches

Le 14/09/2015 23:39, Richard Heck a écrit : On 09/13/2015 10:09 PM, Guillaume Munch wrote: Le 13/09/2015 22:28, Richard Heck a écrit : On 09/12/2015 09:31 PM, Guillaume Munch wrote: * I would like to discuss another set of patches that makes it convenient to navigate within floats: see

Re: Update on the patches

On Tue, Sep 15, 2015 at 02:50:46AM +0100, Guillaume Munch wrote: > Le 14/09/2015 05:04, Scott Kostyshak a écrit : > >On Mon, Sep 14, 2015 at 03:42:15AM +0100, Guillaume Munch wrote: > >>Le 14/09/2015 03:17, Scott Kostyshak a écrit : > >>>put a link to the lyx-devel message on the trac ticket. > >>

Re: Update on the patches

Le 14/09/2015 05:04, Scott Kostyshak a écrit : On Mon, Sep 14, 2015 at 03:42:15AM +0100, Guillaume Munch wrote: Le 14/09/2015 03:17, Scott Kostyshak a écrit : put a link to the lyx-devel message on the trac ticket. How do you find this link? Well, I just do [a and mutt copies it to my clipb

Re: Update on the patches

On 09/13/2015 10:09 PM, Guillaume Munch wrote: Le 13/09/2015 22:28, Richard Heck a écrit : On 09/12/2015 09:31 PM, Guillaume Munch wrote: * I would like to discuss another set of patches that makes it convenient to navigate within floats: see . To test the

Re: Update on the patches

Le 14/09/2015 02:22, Guillaume Munch a écrit : One thing that would have helped was to have emacs configuration files with the correct coding style that you use. For instance my .emacs now reads (omitting irrelevant parts): Such information could go in the relevant code rule file in developmen

Re: Update on the patches

Le 14/09/2015 02:44, Guillaume Munch a écrit : I read: !Important Changes in LyX 2.2.0 (: This file lists interface changes that might affect users in 2.2.0, some known problems in LyX 2.2.0 and some things you have to take into account when upgrading from earlier versions to a vers

Re: Update on the patches

mentioned? I am still unsure how to go about this. From what I understand, whenever committing to branch, you should always update status.21x. As for master, when I know that one of my commits will *not* be backported to branch, I look at RELEASE-NOTES and see if the change belongs to one of the

Re: Update on the patches

On Mon, Sep 14, 2015 at 03:42:15AM +0100, Guillaume Munch wrote: > Le 14/09/2015 03:17, Scott Kostyshak a écrit : > >put a link to the lyx-devel message on the trac ticket. > > How do you find this link? Well, I just do [a and mutt copies it to my clipboard (I have a script). I am guessing you co

Re: Update on the patches

Le 14/09/2015 03:17, Scott Kostyshak a écrit : put a link to the lyx-devel message on the trac ticket. How do you find this link?

Re: Update on the patches

On Sun, Sep 13, 2015 at 01:55:59PM +0200, Georg Baum wrote: > Guillaume Munch wrote: > > > * I would like to discuss another set of patches that makes it > > convenient to navigate within floats: see > > . To test the patch please compare > > the behaviour, bef

Re: Update on the patches

& type) + : InsetCollapsable(buffer), caption_type_(type) {} + /// + std::string const & captionType() const { return caption_type_; } + /// + docstring floatName(std::string const & type) const; + /// +protected: + /// + virtual void setCaptionType(std::string const & type

Re: Update on the patches

I am still unsure how to go about this. From what I understand, whenever committing to branch, you should always update status.21x. ...do make sure to do this for stable. Done. I think one does NOT need to update RELEASE-NOTES for fixes that also go to stable, since they are documented in

Re: Update on the patches

Le 14/09/2015 01:22, Guillaume Munch a écrit : and the .dir-locals.el reads: ((nil . ((indent-tabs-mode . t) (tab-width . 4) (fill-column . 80))) (c-mode . ((c-file-style . "BSD") (c-basic-offset . 4) (c-set-style . "bsd"))) (c++-mode . ((c-ba

Re: Update on the patches

Le 14/09/2015 01:00, Scott Kostyshak a écrit : On Mon, Sep 14, 2015 at 12:39:38AM +0100, Guillaume Munch wrote: Le 13/09/2015 12:55, Georg Baum a écrit : Guillaume Munch wrote: * Where should I commit po files? I vaguely remember reading somewhere that these should be against stable, do I rem

Re: Update on the patches

On Mon, Sep 14, 2015 at 12:39:38AM +0100, Guillaume Munch wrote: > Le 13/09/2015 12:55, Georg Baum a écrit : > >Guillaume Munch wrote: > > > >>* Where should I commit po files? I vaguely remember reading > >>somewhere that these should be against stable, do I remember > >>correctly and in that case

Re: Update on the patches

Le 13/09/2015 12:55, Georg Baum a écrit : Guillaume Munch wrote: * Where should I commit po files? I vaguely remember reading somewhere that these should be against stable, do I remember correctly and in that case is it better to commit to master at the same time? Note that you do not need to

Re: Update on the patches

On 09/12/2015 09:31 PM, Guillaume Munch wrote: * I would like to discuss another set of patches that makes it convenient to navigate within floats: see . To test the patch please compare the behaviour, before and after, of the navigation menus and of the o

Re: Update on the patches

understand, whenever committing to branch, you should always update status.21x. ...do make sure to do this for stable. I think one does NOT need to update RELEASE-NOTES for fixes that also go to stable, since they are documented in status.21x. Only changes that are master-only need to go there, and

Re: Update on the patches

Guillaume Munch wrote: > * Where should I commit po files? I vaguely remember reading somewhere > that these should be against stable, do I remember correctly and in that > case is it better to commit to master at the same time? Note that you do not need to change po files if you don't want to (e

Re: Update on the patches

If so, do all the little bug fixes have to be mentioned? I am still unsure how to go about this. From what I understand, whenever committing to branch, you should always update status.21x. As for master, when I know that one of my commits will *not* be backported to branch, I look at RELEASE-NOTES

Re: Update on the patches

confirm the code is safe or asks you if you are confident. > * Am I responsible for updating the release notes? If so, do all the > little > bug fixes have to be mentioned? I am still unsure how to go about this. From what I understand, whenever committing to branch, you should always upda

Update on the patches

Dear list, I've pushed the patches that we discussed. * f3008c30 and 4d1ad336 are suitable for stable. Shall I commit them? * Am I responsible for updating the release notes? If so, do all the little bug fixes have to be mentioned? * Where should I commit po files? I vaguely remember readin

Re: [LyX/master] Update default path prefix for Mac OS to include the texbin folder inside the TeX Library path and remove old powerpc path entries. The upcoming Mac OS version 10.11 (El Capitan) will

On 07/19/2015 10:50 AM, Stephan Witt wrote: Am 16.07.2015 um 21:59 schrieb Stephan Witt : commit c11c4fd7674f0e45e985ae1b6cfdd6a1a60aa509 Author: Stephan Witt Date: Thu Jul 16 21:52:55 2015 +0200 Update default path prefix for Mac OS to include the texbin folder inside the TeX Library

Re: [LyX/master] Update default path prefix for Mac OS to include the texbin folder inside the TeX Library path and remove old powerpc path entries. The upcoming Mac OS version 10.11 (El Capitan) will

Am 16.07.2015 um 21:59 schrieb Stephan Witt : > commit c11c4fd7674f0e45e985ae1b6cfdd6a1a60aa509 > Author: Stephan Witt > Date: Thu Jul 16 21:52:55 2015 +0200 > >Update default path prefix for Mac OS to include the texbin folder inside > the TeX Library path and remov

LyX-Function textstyle-update

Hi, could we please have also a more user friendly lyx-function? For instance we have to use textstyle-update ... color 16 ... to set the color to "red". Any key-binding using numbers has a risk of being invalid if the corresponding number changes. (As recently happend) The fu

Re: [LyX/master] Update comment.

2015-06-17 8:53 GMT+02:00 Scott Kostyshak: > Now that TL 2015 has been released, is there anything that should be > done here? Or did you mean once TL 2015 has been out long enough to be > the standard? > It's probably too early to presuppose TL 2015. Jürgen > > Scott >

Re: [LyX/master] Update comment.

On Sat, May 16, 2015 at 7:49 AM, Juergen Spitzmueller wrote: > commit 673217593e102586c5638ce3855178783e14c047 > Author: Juergen Spitzmueller > Date: Sat May 16 13:48:17 2015 +0200 > > Update comment. > > diff --git a/lib/languages b/lib/languages > index 1661699

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

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

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

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

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

This reverts commit e44612f0f215d70cb266c4dbf28c126caf2ce992. Revert "layouttranslations: Arabic update by Hatim" This reverts commit 407d5bf228a8fd297aedc933b396a10e976df09b. It is not permitted to change lib/layoutranslations during a

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

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 before the 2.1.0 rel

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

Am Dienstag, 9. Juni 2015 um 00:31:16, schrieb Uwe Stöhr > Am 04.06.2015 um 18:12 schrieb Georg Baum: > > > It is forbidden to update layouttranslations in a stable release, and if an > > update is done in master it must not be done by hand, > > Richard kindly already r

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

Am 04.06.2015 um 18:12 schrieb Georg Baum: It is forbidden to update layouttranslations in a stable release, and if an update is done in master it must not be done by hand, Richard kindly already reverted it. However, I don't understand all this complicated stuff anymore. The file sta

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

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

Re: update arabic translation

Am 26.05.2015 um 14:13 schrieb hatim ali: i hope you can help me: 1st: Nomenclature and indexs not work in arabic language?! Can you please report this as bug in our bug tracking system? 2nd: can i translate this string or not? &New:[[index]] Yes. Only keep the brackets. regards uwe

RE: update arabic translation

gt; To: dr.ha...@hotmail.com > Subject: Re: update arabic translation > > Am 25.05.2015 um 05:05 schrieb hatim ali: > > > I apologize, it was just an inadvertent mistake. > > Hi Hatim, > > no problem! > > I changed it before I committed. > > regards

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On 05/20/2015 08:56 AM, Jean-Marc Lasgouttes wrote: Le 20/05/2015 14:55, Enrico Forestieri a écrit : Incidentally, for this same reason I cannot simply run ./autogen.sh but have to run "bash autogen.sh". This is really minor, though, as What is the error with autogen.sh? Is it the "!" with mak

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Le 20/05/2015 14:55, Enrico Forestieri a écrit : Incidentally, for this same reason I cannot simply run ./autogen.sh but have to run "bash autogen.sh". This is really minor, though, as What is the error with autogen.sh? Is it the "!" with make? Yes, exactly. Is it better now? Yes, thanks.

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On Wed, May 20, 2015 at 12:25:16PM +0200, Jean-Marc Lasgouttes wrote: > Le 16/05/2015 17:06, Enrico Forestieri a écrit : > >On Sat, May 16, 2015 at 01:50:26PM +0200, Jean-Marc Lasgouttes wrote: > > > >>Le 16/05/2015 03:48, Enrico Forestieri a écrit : > >>>Incidentally, for this same reason I cannot

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Le 16/05/2015 17:06, Enrico Forestieri a écrit : On Sat, May 16, 2015 at 01:50:26PM +0200, Jean-Marc Lasgouttes wrote: Le 16/05/2015 03:48, Enrico Forestieri a écrit : Incidentally, for this same reason I cannot simply run ./autogen.sh but have to run "bash autogen.sh". This is really minor, t

Re: boost update?

Le 18 mai 2015 22:24:54 CEST, Vincent van Ravesteijn a écrit : >Op 18 mei 2015 22:20 schreef "Georg Baum" >: >> >> Vincent van Ravesteijn wrote: >> >I remember losing my way in many boost::next errors and >ununderstandable >paragraph iterators. Let's see tomorrow whether your fix(es) solve(s) >m

Re: boost update?

Op 18 mei 2015 22:20 schreef "Georg Baum" : > > Vincent van Ravesteijn wrote: > > > Last time I tried (not so long ago), I hit a lot of new compiler errors, > > which I didn't know how to fix. > > > > Thank you for fixing those.. > > It was easy, it was only one: b596330093d. Maybe our code has som

Re: boost update?

Vincent van Ravesteijn wrote: > Last time I tried (not so long ago), I hit a lot of new compiler errors, > which I didn't know how to fix. > > Thank you for fixing those.. It was easy, it was only one: b596330093d. Maybe our code has some self- healing capabilities:-) Georg

Re: boost update?

Georg Baum schreef op 16-5-2015 om 10:19: Hi, I tested LyX with boost 1.58, and it compiles and runs fine. Shall I update the included boost? This would get rid of some compiler warnings, and since 2.2 will live for a while I guess it is good to start with a recent boost, since a boost update

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Am Sonntag, 17. Mai 2015 um 14:28:37, schrieb Georg Baum > Kornel Benko wrote: > > > Am Samstag, 16. Mai 2015 um 10:43:04, schrieb Georg Baum > > > >> To make it very clear: The automatic update is _not_ meant to be run by > >> default for any build or test

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Kornel Benko wrote: > Am Samstag, 16. Mai 2015 um 10:43:04, schrieb Georg Baum > >> To make it very clear: The automatic update is _not_ meant to be run by >> default for any build or test target. It is not meant either to be run >> without looking at the results. Manu

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On Sat, May 16, 2015 at 01:50:26PM +0200, Jean-Marc Lasgouttes wrote: > Le 16/05/2015 03:48, Enrico Forestieri a écrit : > >Incidentally, for this same reason I cannot simply run ./autogen.sh > >but have to run "bash autogen.sh". This is really minor, though, as > > What is the error with autogen

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On Sat, May 16, 2015 at 11:12:04AM +0200, Georg Baum wrote: > Enrico Forestieri wrote: > > > I have not investigated, but I think this is due to some script assuming > > that /bin/sh is really /bin/bash, and this is not true on solaris. > > In fact I did not know that ! is bash specific. It shou

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Le 16/05/2015 03:48, Enrico Forestieri a écrit : Incidentally, for this same reason I cannot simply run ./autogen.sh but have to run "bash autogen.sh". This is really minor, though, as What is the error with autogen.sh? Is it the "!" with make? JMarc

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Am Samstag, 16. Mai 2015 um 10:43:04, schrieb Georg Baum > To make it very clear: The automatic update is _not_ meant to be run by > default for any build or test target. It is not meant either to be run > without looking at the results. Manual verification is still required (see >

Re: boost update?

Yes, definitely. JMarc Le 16 mai 2015 10:19:47 CEST, Georg Baum a écrit : >Hi, > >I tested LyX with boost 1.58, and it compiles and runs fine. Shall I >update >the included boost? This would get rid of some compiler warnings, and >since >2.2 will live for a while I gues

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Enrico Forestieri wrote: > I have not investigated, but I think this is due to some script assuming > that /bin/sh is really /bin/bash, and this is not true on solaris. In fact I did not know that ! is bash specific. It should work now. > Incidentally, for this same reason I cannot simply run ./

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

format is empty, then I expect for each file an updated format number and nothing else. This can be verified in 10 seconds by looking at the diff. In case of the color update by Uwe the verification was still quite simple: I looked at the new colors in the diff, then at the orginal .tex files,

boost update?

Hi, I tested LyX with boost 1.58, and it compiles and runs fine. Shall I update the included boost? This would get rid of some compiler warnings, and since 2.2 will live for a while I guess it is good to start with a recent boost, since a boost update for a stable release is more risky

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Uwe Stöhr wrote: > Thanks for taking care and adding the note. However, the huge diff shows > that tex2lyx is not yet producing the same as LyX. Can#t we do anything > or shouldn't we do anything here? Some time ago the whitespace differences were even larger, and I already reduced them a bit. I

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On Fri, May 15, 2015 at 09:06:34PM +0200, Georg Baum wrote: > > Can you try again pelase? c_str() was not instantiated explicitly (because > on linux it is automatically instantiated). Yes, it now compiles on both solaris and cygwin. However, on solaris, a spurious warning is printed after each

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Am 15.05.2015 um 21:41 schrieb Georg Baum: 1) It is impossible to manually verify in this huge diff whether the new references are really correct. I wondered about that too. Thanks for taking care and adding the note. However, the huge diff shows that tex2lyx is not yet producing the same as

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Am Freitag, 15. Mai 2015 um 21:45:51, schrieb Georg Baum > Kornel Benko wrote: > > > Am Donnerstag, 14. Mai 2015 um 21:05:23, schrieb Georg Baum > > > >> Kornel Benko wrote: > >> > >> > This does not cover all tex2lyx tests used under cmake. > >> > >> IMHO calling these tests tex2lyx tests is

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Am Freitag, 15. Mai 2015 um 21:41:37, schrieb Georg Baum > Am 14.05.2015 um 23:13 schrieb Uwe Stöhr: > > commit afdfc3cf43501a0728cef79385b31afe6f4cf877 > > Author: Uwe Stöhr > > Date: Thu May 14 23:13:14 2015 +0200 > > > > tex2lyx testfiles: update

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Kornel Benko wrote: > Am Donnerstag, 14. Mai 2015 um 21:05:23, schrieb Georg Baum > >> Kornel Benko wrote: >> >> > This does not cover all tex2lyx tests used under cmake. >> >> IMHO calling these tests tex2lyx tests is confusing. They test nothing in >> tex2lyx which the standard tex2lyx tests

Re: [LyX/master] tex2lyx testfiles: update to latest fileformat

Am 14.05.2015 um 23:13 schrieb Uwe Stöhr: commit afdfc3cf43501a0728cef79385b31afe6f4cf877 Author: Uwe Stöhr Date: Thu May 14 23:13:14 2015 +0200 tex2lyx testfiles: update to latest fileformat Uwe, I appreciate your effort to update the tests, but unfortunately it does not work like

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Enrico Forestieri wrote: > Sure. This is on Solaris: > > g++ -fPIC -O2-L/usr/local/lib -Wl,-R/usr/local/lib -L/opt/lib > -Wl,-R/opt/lib -L/usr/X11/lib -Wl,-R/usr/X11/lib -o check_trivstring > check_trivstring.o dummy_functions.o boost.o liblyxsupport.a -liconv > ../../boost/liblyxboost.a -L/

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On Thu, May 14, 2015 at 09:09:57PM +0200, Georg Baum wrote: > Enrico Forestieri wrote: > > > $ cd build > > $ make alltests > > ... > > CXXLD check_trivstring > > Undefined first referenced > > symbol in file > > _ZNK3lyx14trivial_stringIcE5c_s

Re: [LyX/master] Update tex2lyx and tests after 306b136c

4. Mai 2015 um 01:03:17, schrieb Enrico Forestieri > >> > > >> > > commit 7144f8dad84b5b321f7c87143efec9eb2b6195dc > >> > > Author: Enrico Forestieri > >> > > Date: Thu May 14 01:02:37 2015 +0200 > >> > > > >> > >

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Enrico Forestieri wrote: > $ cd build > $ make alltests > ... > CXXLD check_trivstring > Undefined first referenced > symbol in file > _ZNK3lyx14trivial_stringIcE5c_strEv check_trivstring.o > _ZNK3lyx14trivial_stringIwE5c_strEv check_trivstring

Re: [LyX/master] Update tex2lyx and tests after 306b136c

t 7144f8dad84b5b321f7c87143efec9eb2b6195dc >> > > Author: Enrico Forestieri >> > > Date: Thu May 14 01:02:37 2015 +0200 >> > > >> > > Update tex2lyx and tests after 306b136c >> > >> > Tests which are calling runtests.py with paramet

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Benko wrote: > > > > Am Donnerstag, 14. Mai 2015 um 01:03:17, schrieb Enrico Forestieri > > > > > > > > > commit 7144f8dad84b5b321f7c87143efec9eb2b6195dc > > > > > Author: Enrico Forestieri > > > > > Date: Thu May 14 01:02:37 2015

Re: [LyX/master] Update tex2lyx and tests after 306b136c

> > > > > > > commit 7144f8dad84b5b321f7c87143efec9eb2b6195dc > > > > Author: Enrico Forestieri > > > > Date: Thu May 14 01:02:37 2015 +0200 > > > > > > > > Update tex2lyx and tests after 306b136c > > > > >

Re: [LyX/master] Update tex2lyx and tests after 306b136c

t; > Author: Enrico Forestieri > > > Date: Thu May 14 01:02:37 2015 +0200 > > > > > > Update tex2lyx and tests after 306b136c > > > > Tests which are calling runtests.py with parameter 'uselyx2lyx' are failing > > now if testing is n

Re: [LyX/master] Update tex2lyx and tests after 306b136c

t; > Author: Enrico Forestieri > > > Date: Thu May 14 01:02:37 2015 +0200 > > > > > > Update tex2lyx and tests after 306b136c > > > > Tests which are calling runtests.py with parameter 'uselyx2lyx' are failing > > now if testing is no

Re: [LyX/master] Update tex2lyx and tests after 306b136c

On Thu, May 14, 2015 at 10:37:17AM +0200, Kornel Benko wrote: > Am Donnerstag, 14. Mai 2015 um 01:03:17, schrieb Enrico Forestieri > > > commit 7144f8dad84b5b321f7c87143efec9eb2b6195dc > > Author: Enrico Forestieri > > Date: Thu May 14 01:02:37 2015 +0200 > > &g

Re: [LyX/master] Update tex2lyx and tests after 306b136c

Am Donnerstag, 14. Mai 2015 um 01:03:17, schrieb Enrico Forestieri > commit 7144f8dad84b5b321f7c87143efec9eb2b6195dc > Author: Enrico Forestieri > Date: Thu May 14 01:02:37 2015 +0200 > > Update tex2lyx and tests after 306b136c Tests which are calling runtests.py

Re: [LyX/master] Update paths of included files when saving to a different folder.

Am Dienstag, 5. Mai 2015 schrieb Enrico Forestieri : > I think it is better not to update the path at all if the file does not > exists at the old location, whether or not this is a bibtex database. That's what I was trying to propose, actually. Jürgen > I am going to commit thi

Re: [LyX/master] Update paths of included files when saving to a different folder.

> >> Date: Sun May 3 23:55:19 2015 +0200 > >> > >> Update paths of included files when saving to a different folder. > >> > >> Fixes #9528 and #5115. > >> > >> > > This introduces a severe problem: When saving a file with

Re: [LyX/master] Update paths of included files when saving to a different folder.

2015-05-05 15:14 GMT+02:00 Jürgen Spitzmüller: > 2015-05-03 23:58 GMT+02:00 Enrico Forestieri: > >> commit 8c351e32be92fca91e2dd1f9ec478d5cb1ce6c8c >> Author: Enrico Forestieri >> Date: Sun May 3 23:55:19 2015 +0200 >> >> Update paths of included fil

Re: [LyX/master] Update paths of included files when saving to a different folder.

2015-05-03 23:58 GMT+02:00 Enrico Forestieri: > commit 8c351e32be92fca91e2dd1f9ec478d5cb1ce6c8c > Author: Enrico Forestieri > Date: Sun May 3 23:55:19 2015 +0200 > > Update paths of included files when saving to a different folder. > > Fixes #9528 and #5115.

Re: lyx fi translation update

On 23.04.2015 11:29, Jürgen Spitzmüller wrote: > 2015-04-22 11:11 GMT+02:00 Jari-Matti Mäkelä: > >> Updated the finnish translation from ~2900 strings to 3500. Used the >> stable version but I hope it's useful for the dev version, too. >> > > Thanks. I have pushed this to stable and master (dev).

Re: [LyX/master] Update doc-files due to icon rename, this time correct

Am Montag, 30. März 2015 um 16:23:51, schrieb Enrico Forestieri > On Sun, Mar 29, 2015 at 05:22:13PM +0200, Kornel Benko wrote: > > > commit 7b72010408142d605799c3b4245cfc3052eb3c1f > > Author: Kornel Benko > > Date: Sun Mar 29 17:20:35 2015 +0200 > > > &

<    7   8   9   10   11   12   13   14   15   16   >