Re: [LyX/master] Cmake export tests: Make eu_UserGuide.lyx pass the new ctest

Am Sonntag, 31. Dezember 2017 um 02:01:58, schrieb Scott Kostyshak > On Fri, Oct 27, 2017 at 08:56:00PM +, Kornel Benko wrote: > > commit 7e187563ca166ae0f0de015c456276b0392d8d5e > > Author: Kornel Benko > > Date: Fri Oct 27 22:54:15 2017 +0200 > > > > Cmake export tests: Make eu_User

Re: [LyX/master] Cmake export tests: Make eu_UserGuide.lyx pass the new ctest

On Fri, Oct 27, 2017 at 08:56:00PM +, Kornel Benko wrote: > commit 7e187563ca166ae0f0de015c456276b0392d8d5e > Author: Kornel Benko > Date: Fri Oct 27 22:54:15 2017 +0200 > > Cmake export tests: Make eu_UserGuide.lyx pass the new ctest > > Corrected some graphic paths and readde

Re: Beamer usage again

Am Samstag, 30. Dezember 2017 um 11:40:19, schrieb Jürgen Spitzmüller > Am Samstag, den 30.12.2017, 10:32 + schrieb José Abílio Matos: > > The invariant in our stable series was always to keep the same file > > format. In my humble opinion this is a very good practice and > > something that w

Re: Beamer usage again

On Sat, Dec 30, 2017 at 04:07:19PM +, Richard Heck wrote: > That said, this strikes me too as enough of an improvement to warrant a > late change. > I've found these same aspects of the Beamer implementation unintuitive. What exactly are we talking about potentially backporting? Is it the fol

Re: Beamer usage again

On Sun, Dec 31, 2017 at 12:52 PM, Richard Heck wrote: > On 12/30/2017 06:56 PM, Joel Kulesza wrote: > > On Sun, Dec 31, 2017 at 1:55 AM, Jürgen Spitzmüller wrote: > >> Am Samstag, den 30.12.2017, 10:48 +0100 schrieb Pavel Sanda: >> > I think we can safely go for it. >> > Given that we already ha

Re: Fwd: Re: Publication de LyX version 2.3.0rc1

On Tue, Dec 19, 2017 at 10:16:52AM +, Jean-Pierre Chrétien wrote: > Dear Developers > > Emile posted in French on lyx-fr, here is a translation: > > I noticed an improvement of the 'Advanced Search and Replace' functionality. > However I, noticed a behaviour which appears as a bug to me: > >

Re: Beamer usage again

On 12/30/2017 06:56 PM, Joel Kulesza wrote: > On Sun, Dec 31, 2017 at 1:55 AM, Jürgen Spitzmüller > wrote: > > Am Samstag, den 30.12.2017, 10:48 +0100 schrieb Pavel Sanda: > > I think we can safely go for it. > > Given that we already have two overlay item in the

Re: [LyX/master] Don't show append function where it does not make sense.

On Sat, Dec 30, 2017 at 04:04:39PM +, Juergen Spitzmueller wrote: > commit 612536305bea9ddc2709586d61a2967c65f0ab1b > Author: Juergen Spitzmueller > Date: Sat Dec 30 17:04:10 2017 +0100 > > Don't show append function where it does not make sense. > --- > src/frontends/qt4/Menus.cpp |

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:48 +0100 schrieb Pavel Sanda: > I think we can safely go for it. > Given that we already have two overlay item in the menu, we might > want to group > them at the end of insert menu? Done. Jürgen > > Pavel signature.asc Description: This is a digitally signed mes

Re: Beamer usage again

On 12/30/2017 05:52 AM, José Abílio Matos wrote: > > On Saturday, 30 December 2017 10.40.19 WET Jürgen Spitzmüller wrote: > > > Right. I am talking about the layout format here, though. > > > > > > Jürgen > >   > > Oops. :-) > > You are right. > >   > > IIRC we have been a little bit more permissiv

Re: Beamer usage again

Am Samstag, den 30.12.2017, 21:25 +0900 schrieb Joel Kulesza: > I've pulled (1ff34a97) and tested along with your 9261 patch. It > doesn't appear to work for me as I'd expect; please > see: https://youtu.be/sEIFW9Vo0UY. OK, I see now that it does not make sense to have this separate function. I r

Re: Beamer usage again

On 12/30/2017 06:00 AM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 11:30 +0900 schrieb Joel Kulesza: >> I've tried to demonstrate with screen recording what I tried to >> illustrate with my screenshot previously. There are places I can >> position the cursor where the Edit menus vary

Re: Beamer usage again

On Sat, Dec 30, 2017 at 8:52 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 20:19 +0900 schrieb Joel Kulesza: > > > I am not sure how to fix the first issue. Actually, the procedure > > > works. The problem ist, though, that an empty new frame is > > > inserted, > > > which is rightl

Re: Beamer usage again

Am Samstag, den 30.12.2017, 20:19 +0900 schrieb Joel Kulesza: > > I am not sure how to fix the first issue. Actually, the procedure > > works. The problem ist, though, that an empty new frame is > > inserted, > > which is rightly deleted again by the delete empty paragraphs > > mechanism. This is r

Re: Beamer usage again

Am Samstag, den 30.12.2017, 20:25 +0900 schrieb Joel Kulesza: > Thank you for the clarification; however, I would leave out the word > environment (I'm not sure what value it's adding for the novice or > average user). I would suggest adding new expanding menus in the > Insert Menu so > > Insert

Re: Beamer usage again

On Sat, Dec 30, 2017 at 8:19 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 20:09 +0900 schrieb Joel Kulesza: > > One concern: the language used, while precise, isn't too self- > > descriptive for a LaTeX / LyX novice. My understanding is that part > > of the need for precision stem

Re: Use of deprecated hunspell functions, still needed?

Am Samstag, 30. Dezember 2017 um 10:58:54, schrieb Jürgen Spitzmüller > Am Samstag, den 30.12.2017, 09:08 +0100 schrieb Kornel Benko: > > /usr2/src/lyx/lyx-2.0.x-git/src/HunspellChecker.cpp: In member > > function ‘virtual lyx::SpellChecker::Result > > lyx::HunspellChecker::check(const lyx::WordL

Re: Beamer usage again

On Sat, Dec 30, 2017 at 8:00 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 11:30 +0900 schrieb Joel Kulesza: > > Please excuse the typos in: https://youtu.be/yZyx_RaFynU > > > > Please let me know if there is a better way to provide such examples. > > This is excellent, thank you fo

Re: Beamer usage again

Am Samstag, den 30.12.2017, 20:09 +0900 schrieb Joel Kulesza: > One concern: the language used, while precise, isn't too self- > descriptive for a LaTeX / LyX novice. My understanding is that part > of the need for precision stems from covering various environments > (e.g. an inner enumerate versu

Re: Beamer usage again

On Sat, Dec 30, 2017 at 7:14 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 10:46 +0100 schrieb Pavel Sanda: > > > From what I understand, there is no new string that would be added. > > > The > > > question is just about the translations of the help documents. Is > > > that > > > ri

Re: Beamer usage again

Am Samstag, den 30.12.2017, 11:30 +0900 schrieb Joel Kulesza: > Please excuse the typos in: https://youtu.be/yZyx_RaFynU > > Please let me know if there is a better way to provide such examples. This is excellent, thank you for the efforts. > I've tried to demonstrate with screen recording what

Re: Beamer usage again

On Saturday, 30 December 2017 10.40.19 WET Jürgen Spitzmüller wrote: > Right. I am talking about the layout format here, though. > > Jürgen Oops. :-) You are right. IIRC we have been a little bit more permissive in this case. :-) Happy new year. :-) -- José Abílio

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:32 + schrieb José Abílio Matos: > The invariant in our stable series was always to keep the same file > format. In my humble opinion this is a very good practice and > something that we should continue. Right. I am talking about the layout format here, though. J

Re: Beamer usage again

On Saturday, 30 December 2017 10.14.53 WET Jürgen Spitzmüller wrote: > Note, further, that this entails a layout format change. I am not sure > what our current policy is wrt introducing this within a stable series. > If we don't do that, no for 2.3.0 would mean no for 2.3.x. > > Jürgen The invar

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:46 +0100 schrieb Pavel Sanda: > > From what I understand, there is no new string that would be added. > > The > > question is just about the translations of the help documents. Is > > that > > right? > > Unfortunately no, there is another new string for prepending th

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:44 +0100 schrieb Pavel Sanda: > I do not see how this patch affects things out of beamer scope It applies to all environments with a label. But I think they all benefit from the improvement. Jürgen signature.asc Description: This is a digitally signed message part

Re: Use of deprecated hunspell functions, still needed?

Am Samstag, den 30.12.2017, 09:08 +0100 schrieb Kornel Benko: > /usr2/src/lyx/lyx-2.0.x-git/src/HunspellChecker.cpp: In member > function ‘virtual lyx::SpellChecker::Result > lyx::HunspellChecker::check(const lyx::WordLangTuple&)’: > /usr2/src/lyx/lyx-2.0.x-git/src/HunspellChecker.cpp:359:43: warni

Re: Beamer usage again

Jürgen Spitzmüller wrote: > Am Donnerstag, den 28.12.2017, 22:58 +0100 schrieb Pavel Sanda: > > We can definitely do it in the master. > > Any objections to this? I think we can safely go for it. Given that we already have two overlay item in the menu, we might want to group them at the end of in

Re: Beamer usage again

Scott Kostyshak wrote: > On Thu, Dec 28, 2017 at 09:58:23PM +, Pavel Sanda wrote: > > Jürgen Spitzmüller wrote: > > > >a) one looks into insert menu, but starting new beamer environment > > > > is hidden in edit menu once it appears, not intuitive > > > > > > Moving this to Insert is the e

Re: Beamer usage again

Jürgen Spitzmüller wrote: > Am Freitag, den 29.12.2017, 09:52 +0100 schrieb Jürgen Spitzmüller: > > Exactly. Frame is the thing to use if you need just a standard > > paragraph (nested standard is practically the same). > > > > The on-screen display is sub-optimal, which leads to irritation. See >

Use of deprecated hunspell functions, still needed?

/usr2/src/lyx/lyx-2.0.x-git/src/HunspellChecker.cpp: In member function ‘virtual lyx::SpellChecker::Result lyx::HunspellChecker::check(const lyx::WordLangTuple&)’: /usr2/src/lyx/lyx-2.0.x-git/src/HunspellChecker.cpp:359:43: warning: ‘int Hunspell::spell(const char*, int*, char**)’ is deprecated