Re: LyX 2.1 -- master closed

2013-06-03 Thread BH
Thanks, Pavel. Actually, I realize I misnamed it: it's a *window titlebar* patch. At any rate, it's not an important "fix", as nothing can really be said to be broken with how things currently are. Moreover, it will need to be checked to make sure it's not too kludgey (as I indicated in my previou

Re: LyX 2.1 -- master closed

2013-06-03 Thread Richard Heck
On 06/03/2013 06:59 PM, Uwe Stöhr wrote: Am 03.06.2013 12:21, schrieb Vincent van Ravesteijn: In the meantime, I would like to ask to test current master, and report any bugs and/or regressions. I tested the installer for LyX 2.1-beta and noticed one potential RC issue: The file lyxrc.defau

Re: [LyX/master] add toFilesystemEncoding for -

2013-06-03 Thread Enrico Forestieri
On Mon, Jun 03, 2013 at 06:36:31PM +0200, Stephan Witt wrote: > Am 03.06.2013 um 09:53 schrieb Stephan Witt : > > > Am 03.06.2013 um 02:58 schrieb Enrico Forestieri : > > > >> On Sun, Jun 02, 2013 at 10:47:01AM +0200, Stephan Witt wrote: > >>> Am 02.06.2013 um 10:24 schrieb Georg Baum > >>> : >

Re: LyX 2.1 -- master closed

2013-06-03 Thread Uwe Stöhr
Am 03.06.2013 12:21, schrieb Vincent van Ravesteijn: In the meantime, I would like to ask to test current master, and report any bugs and/or regressions. I tested the installer for LyX 2.1-beta and noticed one potential RC issue: The file lyxrc.defaults is created in Format 11 while the prefe

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Richard Heck wrote: > On 06/03/2013 03:27 PM, Pavel Sanda wrote: >> Richard Heck wrote: >>> a look, I've attached it. I'm not sure why it would be base64. >> If you look on the header of cvs-list mails do you see this line: >> Content-Transfer-Encoding: base64 > > Yes, I see it now, and the source

Re: New Email Scripts

2013-06-03 Thread Richard Heck
On 06/03/2013 03:27 PM, Pavel Sanda wrote: Richard Heck wrote: a look, I've attached it. I'm not sure why it would be base64. If you look on the header of cvs-list mails do you see this line: Content-Transfer-Encoding: base64 Yes, I see it now, and the source of the message looks weird, too.

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Richard Heck wrote: > a look, I've attached it. I'm not sure why it would be base64. If you look on the header of cvs-list mails do you see this line: Content-Transfer-Encoding: base64 ? Pavel

Re: New Email Scripts

2013-06-03 Thread Richard Heck
On 06/03/2013 03:16 PM, Pavel Sanda wrote: Pavel Sanda wrote: (new mails are encapsulated in base64 encoding that's why coloring works). Actually no, I seem to be fooled by my own scripts ;) Why do you use base64 encoding? Can't we continue with plain text version of the mails? I didn't know

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Pavel Sanda wrote: > (new mails are encapsulated in base64 encoding that's why coloring works). Actually no, I seem to be fooled by my own scripts ;) Why do you use base64 encoding? Can't we continue with plain text version of the mails? Pavel

Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Uwe Stöhr
Am 03.06.2013 19:57, schrieb Vincent van Ravesteijn: Yes, documentation can go in. I have put in everything that I had in my tree. - I prepared an installer for the beta release (current master) and from this point of view everything works so far (quick test.) regards Uwe

Automate detection of hunspell dictionaries path

2013-06-03 Thread Scott Kostyshak
Would it make sense to automate the detection of the hunspell dictionaries path? If so, would this go into configure.py? Hunspell allows the following option: -D Show detected path of the loaded dictionary, and list of the search path and the available dictionaries. So we could parse the fol

Re: LyX 2.1 -- master closed

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > Dear all, > > As LyX 2.1 beta1 is closing in on us, I want to freeze master and I would > like to allow in only the fixes we are waiting for, important fixes (after > an ok from me), translations and documentation. > > More specifically, I'm holding the release to

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Richard Heck wrote: > There seemed to be a sense that we shouldn't send multiple emails for a > single push in gsoc and featrues. I agree. I was merely talking about output format, not frequency of sending (new mails are encapsulated in base64 encoding that's why coloring works). If it's complica

Re: [LyX/master] sciword.bind update (fix #8364

2013-06-03 Thread Scott Kostyshak
On Mon, Jun 3, 2013 at 4:52 AM, Pavel Sanda wrote: > Scott Kostyshak wrote: >> commit 3a8da38944d1e349249810064cec393cac2a15a3 >> Author: Scott Kostyshak >> Date: Fri May 24 21:48:30 2013 -0400 >> >> sciword.bind update (fix #8364) >> >> - added bindings for 'math-delim' as a workaround

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Richard Heck wrote: > It should now be working. Everything is configurable, so let me know if > something isn't the way you'd like it to be. Nice. How hard is to synchronize output format for scripts used in different repos like GSoC? I use specific processing for lyx-cvs mails and having two dif

Re: New Email Scripts

2013-06-03 Thread Richard Heck
On 06/03/2013 02:32 PM, Pavel Sanda wrote: Richard Heck wrote: It should now be working. Everything is configurable, so let me know if something isn't the way you'd like it to be. Nice. How hard is to synchronize output format for scripts used in different repos like GSoC? I use specific proce

Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Pavel Sanda
Uwe Stöhr wrote: > Is RELEASE-NOTES up to date? I think one of the recent changes deserve it > to be mentioned. This is a good point. We should highlight such menu movement maybe even in announcement(?), IMHO this is sensitive change which will affect almost anyone and old time users would be ann

Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Uwe Stöhr
Am 03.06.2013 20:05, schrieb Vincent van Ravesteijn: Have you looked in the Document menu ? Not yet. It is there but strange that I missed this change. I find this a bit confusion because I want to view the file - Hmm but the document menu also makes sense. I think such important menu change

Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 19:33, Uwe Stöhr schreef: Am 03.06.2013 12:21, schrieb Vincent van Ravesteijn: As LyX 2.1 beta1 is closing in on us, I want to freeze master Sorry for my commit, saw it too late. However, there is a release blocker in my opinion: the View->Format menus are no longer there. So I

Re: Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Kornel Benko
Am Montag, 3. Juni 2013 um 19:33:42, schrieb Uwe Stöhr > Am 03.06.2013 12:21, schrieb Vincent van Ravesteijn: > > > As LyX 2.1 beta1 is closing in on us, I want to freeze master > > Sorry for my commit, saw it too late. > > However, there is a release blocker in my opinion: the View->Format men

Re: [LyX/master] Fix problem with chunk lyx2lyx conversion spotted by Scott.

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 19:59, Richard Heck schreef: On 06/03/2013 01:02 PM, Richard Heck wrote: commit 89ced5c3c33c788c6539c4956c96a051f079ae1b Author: Richard Heck Date: Mon Jun 3 13:01:39 2013 -0400 Fix problem with chunk lyx2lyx conversion spotted by Scott. We assume chunks come at us

Re: [LyX/master] Fix problem with chunk lyx2lyx conversion spotted by Scott.

2013-06-03 Thread Richard Heck
On 06/03/2013 01:02 PM, Richard Heck wrote: commit 89ced5c3c33c788c6539c4956c96a051f079ae1b Author: Richard Heck Date: Mon Jun 3 13:01:39 2013 -0400 Fix problem with chunk lyx2lyx conversion spotted by Scott. We assume chunks come at us in a certain form. If not, then we

Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 19:33, Uwe Stöhr schreef: Am 03.06.2013 12:21, schrieb Vincent van Ravesteijn: As LyX 2.1 beta1 is closing in on us, I want to freeze master Sorry for my commit, saw it too late. However, there is a release blocker in my opinion: the View->Format menus are no longer there. So I

Re: [LyX/master] Additional.lyx: update description for multiple columns (step 2/2)

2013-06-03 Thread Uwe Stöhr
Am 03.06.2013 19:49, schrieb Scott Kostyshak: Thanks for looking into it. I think you mean Basque. For Indonesian, there is no Additional manual. Yes. I will remove this file too because it is in the same state as the Polish version. I furthermore just found a path bug in the other Additiona

Re: [LyX/master] Additional.lyx: update description for multiple columns (step 2/2)

2013-06-03 Thread Scott Kostyshak
On Mon, Jun 3, 2013 at 1:38 PM, Uwe Stöhr wrote: > Am 03.06.2013 18:08, schrieb Scott Kostyshak: > > >>> Additional.lyx: update description for multiple columns (step 2/2) >> >> >> Does this also need to be applied to pl/Additional.lyx and >> eu/Additional.lyx? They are not compiling now. I g

Re: lyx2lyx broken for noweb?

2013-06-03 Thread Scott Kostyshak
On Mon, Jun 3, 2013 at 1:04 PM, Richard Heck wrote: > On 06/03/2013 12:04 PM, Scott Kostyshak wrote: >> >> To reproduce, with 2.1git open examples/noweb2lyx. I get: >> noweb2lyx.lyx is from an older version of LyX and the lyx2lyx script >> failed to convert it. >> >> Is this still being worked on?

Re: [LyX/master] Additional.lyx: update description for multiple columns (step 2/2)

2013-06-03 Thread Uwe Stöhr
Am 03.06.2013 18:08, schrieb Scott Kostyshak: Additional.lyx: update description for multiple columns (step 2/2) Does this also need to be applied to pl/Additional.lyx and eu/Additional.lyx? They are not compiling now. I get: Layout `Begin Multiple Columns' was not found. Indeed. I was

Re: LyX 2.1 -- master closed - serious regression bug

2013-06-03 Thread Uwe Stöhr
Am 03.06.2013 12:21, schrieb Vincent van Ravesteijn: As LyX 2.1 beta1 is closing in on us, I want to freeze master Sorry for my commit, saw it too late. However, there is a release blocker in my opinion: the View->Format menus are no longer there. So I cannot view files as DVI or XeTeX anymo

Re: LyX 2.1 -- master closed

2013-06-03 Thread Yihui Xie
Liviu is correct. And in knitr, I really do not want to support `<<>>= xx` either, although for now, xx is ignored. Regards, Yihui -- Yihui Xie Phone: 515-294-2465 Web: http://yihui.name Department of Statistics, Iowa State University 2215 Snedecor Hall, Ames, IA On Mon, Jun 3, 2013 at 4:07 AM,

Re: lyx2lyx broken for noweb?

2013-06-03 Thread Richard Heck
On 06/03/2013 12:04 PM, Scott Kostyshak wrote: To reproduce, with 2.1git open examples/noweb2lyx. I get: noweb2lyx.lyx is from an older version of LyX and the lyx2lyx script failed to convert it. Is this still being worked on? All right, so the problem is that this does not have the sort of fo

Re: [LyX/master] add toFilesystemEncoding for -

2013-06-03 Thread Stephan Witt
Am 03.06.2013 um 09:53 schrieb Stephan Witt : > Am 03.06.2013 um 02:58 schrieb Enrico Forestieri : > >> On Sun, Jun 02, 2013 at 10:47:01AM +0200, Stephan Witt wrote: >>> Am 02.06.2013 um 10:24 schrieb Georg Baum : , or trac: http://www.lyx.org/trac/browser/lyxgit/src/support/Package.cp

Re: lyx2lyx broken for noweb?

2013-06-03 Thread Richard Heck
On 06/03/2013 12:04 PM, Scott Kostyshak wrote: To reproduce, with 2.1git open examples/noweb2lyx. I get: noweb2lyx.lyx is from an older version of LyX and the lyx2lyx script failed to convert it. Is this still being worked on? I'll have a look. rh

lyx2lyx broken for noweb?

2013-06-03 Thread Scott Kostyshak
To reproduce, with 2.1git open examples/noweb2lyx. I get: noweb2lyx.lyx is from an older version of LyX and the lyx2lyx script failed to convert it. Is this still being worked on? Scott

Re: [LyX/master] Additional.lyx: update description for multiple columns (step 2/2)

2013-06-03 Thread Scott Kostyshak
On Sat, Jun 1, 2013 at 12:16 PM, Uwe Stöhr wrote: > commit a853132e127b251f044569a852ffaddb3741e236 > Author: Uwe Stöhr > Date: Sat Jun 1 18:16:01 2013 +0200 > > Additional.lyx: update description for multiple columns (step 2/2) Does this also need to be applied to pl/Additional.lyx and eu

[PATCH] Small post-kill-gettext cleanup

2013-06-03 Thread Jean-Marc Lasgouttes
THe following patch moves a Qt workaround where it belongs, and solves a weird error message spotted by Vincent. Vincent, can this go in? JMarc >From 72f7b30f365b1dfe18f36d4a9240320a452c4333 Mon Sep 17 00:00:00 2001 From: Jean-Marc Lasgouttes Date: Mon, 3 Jun 2013 18:08:53 +0200 Subject: [PAT

Re: [PATCH] Small post-kill-gettext cleanup

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 18:18, Jean-Marc Lasgouttes schreef: THe following patch moves a Qt workaround where it belongs, and solves a weird error message spotted by Vincent. Vincent, can this go in? JMarc Yes. Vincent

Re: Regression in trunk

2013-06-03 Thread Jürgen Spitzmüller
Stephan Witt wrote: > I wouldn't call this a fix. > > Isn't it better to change the offending conversions in > lyx/src/support/convert.cpp? > > http://www.boost.org/doc/libs/1_47_0/libs/conversion/lexical_cast.htm#lexica > l_cast says: > > "Where a higher degree of control is required over conve

Re: Regression in trunk

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 17:53, Jean-Marc Lasgouttes schreef: 03/06/2013 17:49, Stephan Witt: Isn't it the safest to add "setlocale(LC_NUMERIC, "C") to GuiApplication::setLocale()" ? We used to do this before, and this fixes also the other places where we might get hit. I wouldn't call this a fix. Isn'

Re: Regression in trunk

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 17:49, Stephan Witt schreef: Am 03.06.2013 um 17:33 schrieb Vincent van Ravesteijn : Op 3-6-2013 17:05, Jürgen Spitzmüller schreef: Jean-Marc Lasgouttes wrote: However, the problem might hit us on more places, and the question is if we want convert to be at all locale dependent.

Re: Regression in trunk

2013-06-03 Thread Jean-Marc Lasgouttes
03/06/2013 17:49, Stephan Witt: Isn't it the safest to add "setlocale(LC_NUMERIC, "C") to GuiApplication::setLocale()" ? We used to do this before, and this fixes also the other places where we might get hit. I wouldn't call this a fix. Isn't it better to change the offending conversions in

Re: Regression in trunk

2013-06-03 Thread Stephan Witt
Am 03.06.2013 um 17:33 schrieb Vincent van Ravesteijn : > Op 3-6-2013 17:05, Jürgen Spitzmüller schreef: >> Jean-Marc Lasgouttes wrote: However, the problem might hit us on more places, and the question is if we want convert to be at all locale dependent. >>> I think that nothing sh

Re: Regression in trunk

2013-06-03 Thread Jürgen Spitzmüller
Vincent van Ravesteijn wrote: > Isn't it the safest to add "setlocale(LC_NUMERIC, "C") to > GuiApplication::setLocale()" ? > > We used to do this before, and this fixes also the other places where we > might get hit. Yes, after your analysis of the problem, I think so, too. The attached patch

Re: Regression in trunk

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 17:05, Jürgen Spitzmüller schreef: Jean-Marc Lasgouttes wrote: However, the problem might hit us on more places, and the question is if we want convert to be at all locale dependent. I think that nothing should be locale dependent. So should we replace the lexical_casts with stream

Re: Regression in trunk

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 16:41, Vincent van Ravesteijn schreef: Op 3 jun. 2013 12:58 schreef "Jürgen Spitzmüller" > het volgende: > > In trunk, if you open a file that uses the outputLaTeXColor method of > Color.cpp with a German locale, a wrong LaTeX output is generated (float > valu

Re: Regression in trunk

2013-06-03 Thread Jürgen Spitzmüller
Jean-Marc Lasgouttes wrote: > > However, the problem might hit us on more places, and the question is if > > we > > want convert to be at all locale dependent. > > I think that nothing should be locale dependent. So should we replace the lexical_casts with stream conversions? Would this affect p

Re: Regression in trunk

2013-06-03 Thread Jean-Marc Lasgouttes
03/06/2013 16:46, Jürgen Spitzmüller: However, the problem might hit us on more places, and the question is if we want convert to be at all locale dependent. I think that nothing should be locale dependent. JMarc

Re: Regression in trunk

2013-06-03 Thread Jürgen Spitzmüller
Jürgen Spitzmüller wrote: > In trunk, if you open a file that uses the outputLaTeXColor method of > Color.cpp with a German locale, a wrong LaTeX output is generated (float > values with comma as separator), and LaTeX fails. Try the attached example > file with LANG=de_DE. > > This is a regress

Re: Regression in trunk

2013-06-03 Thread Vincent van Ravesteijn
Op 3 jun. 2013 12:58 schreef "Jürgen Spitzmüller" het volgende: > > In trunk, if you open a file that uses the outputLaTeXColor method of > Color.cpp with a German locale, a wrong LaTeX output is generated (float > values with comma as separator), and LaTeX fails. Try the attached example > file w

Re: Build Broken For Me

2013-06-03 Thread Richard Heck
On 06/03/2013 09:40 AM, Jean-Marc Lasgouttes wrote: Le 01/06/2013 16:21, Richard Heck a écrit : I take it the problem is that the autoconf script for po/ still depends upon certain macros that are defined by gettext. We used to include them in our source. Now they are gone. In particular:

Re: [LyX/master] Initialize initial_value_.

2013-06-03 Thread Richard Heck
On 06/03/2013 06:52 AM, Jean-Marc Lasgouttes wrote: 02/06/2013 15:42, Richard Heck: commit bbce65b68ea69deaf99c2ac26d4f2ef5670c92f2 Author: Richard Heck Date: Sun Jun 2 09:40:44 2013 -0400 Initialize initial_value_. Well, the previous code was more adapted to the goal of the bug ("al

Re: New Email Scripts

2013-06-03 Thread Richard Heck
On 06/03/2013 04:54 AM, Vincent van Ravesteijn wrote: On Mon, Jun 3, 2013 at 10:41 AM, Pavel Sanda > wrote: Vincent van Ravesteijn wrote: > Maybe, it is not that useful to send a mail to everyone for each commit in > the gsoc repo. I hope the students wi

Re: Build Broken For Me

2013-06-03 Thread Jean-Marc Lasgouttes
Le 01/06/2013 16:21, Richard Heck a écrit : I take it the problem is that the autoconf script for po/ still depends upon certain macros that are defined by gettext. We used to include them in our source. Now they are gone. In particular: AC_LIB_RPATH is def'd in lib-link.m4 AC_LIB_PROG

Re: LyX 2.1 -- master closed

2013-06-03 Thread Vincent van Ravesteijn
Op 3-6-2013 12:38, Liviu Andronic schreef: On Mon, Jun 3, 2013 at 12:21 PM, Vincent van Ravesteijn wrote: In the meantime, I would like to ask to test current master, and report any bugs and/or regressions. I expect the above issues to be fixed early this week. This means that we can hopefully

Re: LyX 2.1 -- master closed

2013-06-03 Thread Liviu Andronic
On Mon, Jun 3, 2013 at 12:43 PM, Jean-Marc Lasgouttes wrote: > 03/06/2013 12:21, Vincent van Ravesteijn: > >> Dear all, >> >> As LyX 2.1 beta1 is closing in on us, I want to freeze master and I >> would like to allow in only the fixes we are waiting for, important >> fixes (after an ok from me), t

Re: LyX 2.1 -- master closed

2013-06-03 Thread Jürgen Spitzmüller
Vincent van Ravesteijn wrote: > - an advice on what to do for bug #8408 (use of pLatex and encodings). If nothing happens, this needs to be reverted: http://www.lyx.org/trac/changeset/0bff66b8a5a8a289dfb36bfb339e9586b3a02d51/lyxgit/lib/configure.py The -kanji switch was implemented wrongly. Curre

Regression in trunk

2013-06-03 Thread Jürgen Spitzmüller
In trunk, if you open a file that uses the outputLaTeXColor method of Color.cpp with a German locale, a wrong LaTeX output is generated (float values with comma as separator), and LaTeX fails. Try the attached example file with LANG=de_DE. This is a regression to 2.0. Jürgen color.lyx Descrip

Re: [LyX/master] Initialize initial_value_.

2013-06-03 Thread Jean-Marc Lasgouttes
02/06/2013 15:42, Richard Heck: commit bbce65b68ea69deaf99c2ac26d4f2ef5670c92f2 Author: Richard Heck Date: Sun Jun 2 09:40:44 2013 -0400 Initialize initial_value_. Well, the previous code was more adapted to the goal of the bug ("allow to start inset counter at a random value"). wasn'

Re: LyX 2.1 -- master closed

2013-06-03 Thread Jean-Marc Lasgouttes
03/06/2013 12:21, Vincent van Ravesteijn: Dear all, As LyX 2.1 beta1 is closing in on us, I want to freeze master and I would like to allow in only the fixes we are waiting for, important fixes (after an ok from me), translations and documentation. More specifically, I'm holding the release to

Re: LyX 2.1 -- master closed

2013-06-03 Thread Liviu Andronic
On Mon, Jun 3, 2013 at 12:21 PM, Vincent van Ravesteijn wrote: > In the meantime, I would like to ask to test current master, and report any > bugs and/or regressions. I expect the above issues to be fixed early this > week. This means that we can hopefully tag the first beta release next > weeken

LyX 2.1 -- master closed

2013-06-03 Thread Vincent van Ravesteijn
Dear all, As LyX 2.1 beta1 is closing in on us, I want to freeze master and I would like to allow in only the fixes we are waiting for, important fixes (after an ok from me), translations and documentation. More specifically, I'm holding the release to wait for: - tex2lyx part for the new chunk

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > I proposed to my student to work in feature branches in the gsoc repo. When > something is sort of ready, it is merged into the gsoc/outliner/master > branch. When gsoc/outliner/master has acquired enough to be usable by the > general public, it can be merged into ly

Re: [LyX master] Add formats and converters for cropped PDF/EPS

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > > NewInLyX21 wiki? P > > > > > Yes, good idea. Go ahead ;). Dear Liviu :)) P > > Vincent

Re: [LyX master] Add formats and converters for cropped PDF/EPS

2013-06-03 Thread Vincent van Ravesteijn
On Mon, Jun 3, 2013 at 11:38 AM, Pavel Sanda wrote: > Vincent van Ravesteijn wrote: > > commit 704273eea0ad8c26ae4e147aa19230f98ede5f75 > > Author: Vincent van Ravesteijn > > Date: Thu May 23 15:04:12 2013 +0200 > > > > Add formats and converters for cropped PDF/EPS > > > > With LyX co

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > If we make the script such that all updates to a certain branch sends an > e-mail that is part of the same e-mail thread, it might be much more > comfortable for the recipient... if the recipient chose to use a suitable > mail client. > > Would that be a good idea ?

Re: [LyX master] Add formats and converters for cropped PDF/EPS

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > commit 704273eea0ad8c26ae4e147aa19230f98ede5f75 > Author: Vincent van Ravesteijn > Date: Thu May 23 15:04:12 2013 +0200 > > Add formats and converters for cropped PDF/EPS > > With LyX configured in this way, the user would only need to: > >

Re: [LyX/master] PrefsUi: Remove unneeded widths

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > commit 83399dcb7a83d79cddba505ab71388c0737228c6 > Author: Vincent van Ravesteijn > Date: Sun Jun 2 23:30:06 2013 +0200 > > PrefsUi: Remove unneeded widths nice nice nice! p

Re: LyX crash when editting Long Table Paragraph Setting

2013-06-03 Thread Vincent van Ravesteijn
> > Could not reproduce (linux, lyx 2.0.6). Maybe more specific steps are > necessary. Pavel > I could reproduce with 2.1git. Fixing the easy way is easy, the LFUN_PARAGRAPH_PARAMS_APPLY should be send to all cells individually. However, the more general problem is that there are cases in which w

Re: New Email Scripts

2013-06-03 Thread Vincent van Ravesteijn
Oh.. and something that I proposed a long time ago. If we make the script such that all updates to a certain branch sends an e-mail that is part of the same e-mail thread, it might be much more comfortable for the recipient... if the recipient chose to use a suitable mail client. Would that be a

Re: LyX crash when editting Long Table Paragraph Setting

2013-06-03 Thread Pavel Sanda
#CHEW KOK HON# wrote: > Dear developers, > > I am currently using LyX version 2.0.5.1 and I found a bug in Lyx which will > trigger crash of program. These are the steps lead to crash: > > Steps: > > 1) Create a table > > 2) Convert it into a long table > > 3) Type paragraphs i

Re: New Email Scripts

2013-06-03 Thread Vincent van Ravesteijn
On Mon, Jun 3, 2013 at 10:41 AM, Pavel Sanda wrote: > Vincent van Ravesteijn wrote: > > Maybe, it is not that useful to send a mail to everyone for each commit > in > > the gsoc repo. I hope the students will commit and push frequently, so > the > > mentors can see what they are doing. > > It mea

Re: [LyX/master] sciword.bind update (fix #8364

2013-06-03 Thread Pavel Sanda
Scott Kostyshak wrote: > commit 3a8da38944d1e349249810064cec393cac2a15a3 > Author: Scott Kostyshak > Date: Fri May 24 21:48:30 2013 -0400 > > sciword.bind update (fix #8364) > > - added bindings for 'math-delim' as a workaround > for US keyboards with Windows > - added

Re: New Email Scripts

2013-06-03 Thread Pavel Sanda
Vincent van Ravesteijn wrote: > Maybe, it is not that useful to send a mail to everyone for each commit in > the gsoc repo. I hope the students will commit and push frequently, so the > mentors can see what they are doing. It means that GSOC work would be visible through mail-diffs only at the f

Re: [LyX master] moderncv.layout: support the command \social

2013-06-03 Thread Pavel Sanda
Uwe Stöhr wrote: >>> That is something I don't understand. Ubuntu is the OS and nothing more. >>> Imagine Windows would change the behaviour of a program - the web would >>> be full of complaints. TeXLive has its own package manager and I think >>> it is a bug that an OS offers own packages that br

Re: [LyX/master] add toFilesystemEncoding for -

2013-06-03 Thread Stephan Witt
Am 03.06.2013 um 02:58 schrieb Enrico Forestieri : > On Sun, Jun 02, 2013 at 10:47:01AM +0200, Stephan Witt wrote: >> Am 02.06.2013 um 10:24 schrieb Georg Baum : >>> , or trac: >>> http://www.lyx.org/trac/browser/lyxgit/src/support/Package.cpp?annotate=blame >>> >>> . This tells you that Enrico

Re: GSoC: UI Improvement and Non-Linear Writing Enhancement

2013-06-03 Thread Pavel Sanda
Cyrille Artho wrote: > I agree that it's much better to update progress on the GSoC projects on > the wiki. First, we need the original proposal (on Melange) as a reference; Note that original proposal are not visible to non-mentors, so maybe good idea to copy&paste them into wiki. Pavel