Re: PATCH new OOo2 file extensions

2005-05-16 Thread Leonard den Ottolander
Hi Pavel, On Mon, 2005-05-16 at 19:33, Pavel Roskin wrote: > What's your definition of "latest gcc"? According to gcc.gnu.org, it's > 4.0.0. Kinda missed that line, but already understood this from Nerijus. And at the time of the MC_4_6_1_PRE "freeze", in december 2004 there was no such compiler

Re: PATCH new OOo2 file extensions

2005-05-16 Thread Roland Illig
Pavel Roskin wrote: I believe an X error handler is needed. http://mail.gnome.org/archives/mc-devel/2005-May/msg00039.html I have committed a fix some months ago. See HEAD:src/x11conn.c Roland ___ Mc-devel mailing list http://mail.gnome.org/mailman/listin

Re: PATCH new OOo2 file extensions

2005-05-16 Thread Pavel Roskin
Hello, Leonard! On Sat, 2005-05-14 at 12:00 +0200, Leonard den Ottolander wrote: > On Sat, 2005-05-14 at 00:13, Pavel Roskin wrote: > > For example, the "stable" > > branch compiles with a significant amount of warnings by the latest gcc. > > This wasn't the case when 4.6.0 was released. > > I do

Re: PATCH new OOo2 file extensions

2005-05-14 Thread Nerijus Baliunas
On Sat, 14 May 2005 12:00:16 +0200 Leonard den Ottolander <[EMAIL PROTECTED]> wrote: > I don't see any warning on the MC_4_6_1_PRE branch Pavel is probably using gcc 4.0. > P.S. I did commit this to MC_4_6_1_PRE. Thanks. Regards, Nerijus ___ Mc-deve

Re: PATCH new OOo2 file extensions

2005-05-14 Thread Leonard den Ottolander
Hello Pavel, On Sat, 2005-05-14 at 00:13, Pavel Roskin wrote: > For example, the "stable" > branch compiles with a significant amount of warnings by the latest gcc. > This wasn't the case when 4.6.0 was released. I don't see *any* warning on the MC_4_6_1_PRE branch, which is the branch that shoul

Re: PATCH new OOo2 file extensions

2005-05-13 Thread Nerijus Baliunas
On Fri, 13 May 2005 18:13:29 -0400 Pavel Roskin <[EMAIL PROTECTED]> wrote: > > IMHO it's safe to apply to MC_4_6_1_PRE too. > > Most changes are safe to apply, but it takes additional time. I'm Yes, but not in this trivial case :) > thinking of skipping 4.6.1 and going to 4.7.0 because the cha

Re: PATCH new OOo2 file extensions

2005-05-13 Thread Pavel Roskin
Hi, Nerijus! On Fri, 2005-05-13 at 18:36 +0300, Nerijus Baliunas wrote: > IMHO it's safe to apply to MC_4_6_1_PRE too. Most changes are safe to apply, but it takes additional time. I'm thinking of skipping 4.6.1 and going to 4.7.0 because the changes accumulated so far exceed by far what is expe

Re: PATCH new OOo2 file extensions

2005-05-13 Thread Nerijus Baliunas
On Fri, 13 May 2005 11:02:57 -0400 Pavel Roskin <[EMAIL PROTECTED]> wrote: > > --- mc.ext.orig 2005-04-21 10:15:14.0 +0300 > > +++ mc.ext 2005-05-12 21:52:22.0 +0300 > > @@ -347,8 +347,9 @@ > > Open=(ooffice %f &) > > > > # StarOffice 6 and OpenOffice.org formats > >

Re: PATCH new OOo2 file extensions

2005-05-13 Thread Pavel Roskin
Hello, Nerijus! On Thu, 2005-05-12 at 22:04 +0300, Nerijus Baliunas wrote: > Hello, > > Please apply this patch: > > --- mc.ext.orig 2005-04-21 10:15:14.0 +0300 > +++ mc.ext 2005-05-12 21:52:22.0 +0300 > @@ -347,8 +347,9 @@ > Open=(ooffice %f &) > > # StarOffice 6

PATCH new OOo2 file extensions

2005-05-12 Thread Nerijus Baliunas
Hello, Please apply this patch: --- mc.ext.orig 2005-04-21 10:15:14.0 +0300 +++ mc.ext 2005-05-12 21:52:22.0 +0300 @@ -347,8 +347,9 @@ Open=(ooffice %f &) # StarOffice 6 and OpenOffice.org formats -regex/\.(sxw|stw|sxc|stc|sxi|sti|sxd|std|sxm|sxg)$ +regex/\.(odt|ott