Re: [PATCH] Fix a GCC warning: comparing signed vs. unsigned

Am Dienstag, 20. Mai 2014 schrieb Cyrille Artho: > > It is the correct type on linux as well. Therefore, the approach > > suggested by Cyrille is IMHO the best one: Change the type of nRead > > to ssize_t (note the two s), and change the if-condition to > > > > if (static_cast(nRead) < buf.size()

Re: [PATCH] Fix a GCC warning: comparing signed vs. unsigned

It is the correct type on linux as well. Therefore, the approach suggested by Cyrille is IMHO the best one: Change the type of nRead to ssize_t (note the two s), and change the if-condition to if (static_cast(nRead) < buf.size() - 1) { This is 100% safe: We know that nRead > 0 at the time the

Re: lyx2lyx & beamer

On Mon, May 19, 2014 at 10:34:17PM +0200, Enrico Forestieri wrote: > > With the attached patch I can export beamerlyxexample1.lyx to 2.0 format > and load it with lyx-2.0 without error. But then it fails to compile :( > Someone who really understand what has to happen should have a closer > look.

Re: lyx2lyx & beamer

On Mon, May 19, 2014 at 07:37:15PM +0200, Enrico Forestieri wrote: > On Mon, May 19, 2014 at 09:41:01AM -0400, Richard Heck wrote: > > > On 05/08/2014 02:42 PM, Enrico Forestieri wrote: > > >On Thu, May 08, 2014 at 08:41:09AM +0200, Jürgen Spitzmüller wrote: > > >>2014-05-08 8:29 GMT+02:00 Jürgen

Re: [PATCH] Fix a GCC warning: comparing signed vs. unsigned

Cyrille Artho wrote: > Scott Kostyshak wrote: >> On Sun, May 18, 2014 at 7:58 PM, Richard Heck wrote: >>> On 05/18/2014 07:22 PM, Scott Kostyshak wrote: Is this OK? Note that converting the left hand side to an unsigned int would work also, because it was checked just above that nR

Re: lyx2lyx & beamer

On Mon, May 19, 2014 at 09:41:01AM -0400, Richard Heck wrote: > On 05/08/2014 02:42 PM, Enrico Forestieri wrote: > >On Thu, May 08, 2014 at 08:41:09AM +0200, Jürgen Spitzmüller wrote: > >>2014-05-08 8:29 GMT+02:00 Jürgen Spitzmüller : > >> > >>>Don't see this with current branch. > >>> > >>Ah, you

Re: lyx2lyx & beamer

On 05/08/2014 02:42 PM, Enrico Forestieri wrote: On Thu, May 08, 2014 at 08:41:09AM +0200, Jürgen Spitzmüller wrote: 2014-05-08 8:29 GMT+02:00 Jürgen Spitzmüller : Don't see this with current branch. Ah, you talk about opening in 2.0.x. Can you track it down further? Jürgen, it seems that t

Re: Beamer lyx2lyx error

On 05/18/2014 07:56 PM, Richard Heck wrote: On 05/18/2014 06:48 PM, Scott Kostyshak wrote: I'm not sure if this is a known issue or not. If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and then reopen it in LyX 2.2git, I get an error "Buffer... ended unexpectedly, which means th

Re: beamer suggestion

On 05/19/2014 09:03 AM, Neal Becker wrote: On Mon, May 19, 2014 at 9:01 AM, Richard Heck > wrote: On 05/19/2014 07:17 AM, Neal Becker wrote: How about an 'insert frame', perhaps under 'insert' menu? It would insert a frame, a 'standard' environment n

Re: beamer suggestion

That's my usual workflow for setting up a frame. Often, I would then change that standard env to an itemize, and I'd have a typical frame with bullets. What would you do differently? On Mon, May 19, 2014 at 9:01 AM, Richard Heck wrote: > On 05/19/2014 07:17 AM, Neal Becker wrote: > >> How abo

Re: beamer suggestion

On 05/19/2014 07:17 AM, Neal Becker wrote: How about an 'insert frame', perhaps under 'insert' menu? It would insert a frame, a 'standard' environment nested under the frame, and a separator. Cursor placed into frame title, ready to add a title. Why are you inserting a nested standard environm

beamer suggestion

How about an 'insert frame', perhaps under 'insert' menu? It would insert a frame, a 'standard' environment nested under the frame, and a separator. Cursor placed into frame title, ready to add a title.

Re: Default values for inset arguments

On 19/05/2014 7:07 p.m., Jürgen Spitzmüller wrote: 2014-05-18 23:14 GMT+02:00 aparsloe >: Hullo Jürgen, I have come across an inconsistency/oversight in the treatment of inset arguments. I have a custom inset that inserts a LaTeX command (call it \

Re: Default values for inset arguments

2014-05-18 23:14 GMT+02:00 aparsloe : > Hullo Jürgen, > > I have come across an inconsistency/oversight in the treatment of inset > arguments. I have a custom inset that inserts a LaTeX command (call it > \blah) which has two optional arguments preceding the main argument. It > makes sense for the