current mcview still considered buggy

2005-06-07 Thread Roland Illig
Hi, i must admit that I have been overly confident with the quality of the rewritten internal viewer. I have found two bugs in the text wrap mode. The first occurs when moving up a line or moving down a line. If the length of the first line on the screen (excluding the newline character) is

Re: current mcview still considered buggy

2005-06-07 Thread Leonard den Ottolander
Morning Roland, On Tue, 2005-06-07 at 08:25, Roland Illig wrote: i must admit that I have been overly confident with the quality of the rewritten internal viewer. I have found two bugs in the text wrap mode. I'm currently working on these bugs and hope they will be fixed today. How about

Re: Release procedure

2005-06-07 Thread Pavel Tsekov
Hello, On Mon, 6 Jun 2005, Leonard den Ottolander wrote: Hello Miguel, On Mon, 2005-06-06 at 22:58, Miguel de Icaza wrote: I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what version should we use? Please

Re: Release procedure

2005-06-07 Thread Pavel Tsekov
Hello, On Mon, 6 Jun 2005, Roland Illig wrote: We continue to use the 4.6.xx family name. I think it might be time to change one of those numbers to identify the changes done since the 4.6.0 release in a more significant way. I would prefer 4.7. (Just to leave the long past of 4.6.*

Re: current mcview still considered buggy

2005-06-07 Thread Pavel Tsekov
Hello, On Tue, 7 Jun 2005, Roland Illig wrote: i must admit that I have been overly confident with the quality of the rewritten internal viewer. I have found two bugs in the text wrap mode. You have always been overly confident with the quality of your code. Period. With your ideas and ways

Re: current mcview still considered buggy

2005-06-07 Thread Roland Illig
Pavel Tsekov wrote: I still wonder why you keep posting this kind of email... I can't see the point. The point is that until yesterday I thought the viewer contained really close to zero bugs. That's what I also told Miguel for considering which CVS branch to release. So now I revert that

Re: current mcview still considered buggy

2005-06-07 Thread Pavel Tsekov
Hello, On Tue, 7 Jun 2005, Roland Illig wrote: Pavel Tsekov wrote: I still wonder why you keep posting this kind of email... I can't see the point. The point is that until yesterday I thought the viewer contained really close to zero bugs. That's what I also told Miguel for considering

[PATCH]: exit_subshell(): Cleanup only if required.

2005-06-07 Thread Pavel Tsekov
Hello, The patch fixes an issue with exit_subshell() cleaning up internal variables even when it should not. To reproduce: 1) Start MC with subshell support and bash as the subshell 2) Press `Ctrl + O' 3) Press `Tab' 4) Press `Ctrl + O' 5) Press `F10' and select `Yes' 6) MC will warn you

Re: New Maintainer for MC Project

2005-06-07 Thread Andrew V. Samoilov
Hello Terry! ... about offering to become the new Maintainer of the Midnight Commander Project. Well, Terry, I have some arguments against your offer, but after reading your letters here I just has to say I don't need such maintainer. It's better have no maintainer than such person. No,

Re: [PATCH]: exit_subshell(): Cleanup only if required.

2005-06-07 Thread Pavel Shirshov (pchel)
Hello Pavel, Tuesday, June 7, 2005, 2:30:48 PM, you wrote: PT Hello, PT The patch fixes an issue with exit_subshell() cleaning up PT internal variables even when it should not. PT To reproduce: PT 1) Start MC with subshell support and bash as the subshell PT 2) Press `Ctrl + O' PT 3) Press

Re: Release procedure

2005-06-07 Thread Miguel de Icaza
Hello, Please use MC_4_6_1_PRE for the release of 4.6.1. Then we can use HEAD for 4.6.2 and onwards. I second that. Sounds good. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel

Re: Release procedure

2005-06-07 Thread Miguel de Icaza
Hello, I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what version should we use? What did you fix? Make distcheck was broken, look at the dist-hook target, it would not build with VPATH/different prefixes.

Keybindings in mcedit

2005-06-07 Thread vitja
Hi, all! I've updated my keybindings patch to work with latest CVS. new stuff: label text command could be changed see cooledit.bindings for example -- Vitja Makarov mcedit-keys.tar.bz2 Description: BZip2 compressed data ___ Mc-devel mailing list

Re: Release procedure

2005-06-07 Thread Miguel de Icaza
hello, I have a tarball made from the branch: http://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz I can rename this to 4.6.1 if people want. Miguel. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel

Re: Release procedure

2005-06-07 Thread Pavel Tsekov
Hello, On Tue, 7 Jun 2005, Miguel de Icaza wrote: hello, I have a tarball made from the branch: http://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz The right link is: http://primates.ximian.com/~miguel/mc/mc-4.6.1-pre5a.tar.gz

Re[2]: Release procedure

2005-06-07 Thread Pavel Shirshov (pchel)
Hello Miguel, Tuesday, June 7, 2005, 5:10:03 PM, you wrote: MdI I have a tarball made from the branch: MdIhttp://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz MdI I can rename this to 4.6.1 if people want. Miguel, Why 4.6.1-pre5a, not pre4a? Please wait before renaming

backport of X11 connection handling

2005-06-07 Thread Roland Illig
I just backported the X11 connection handling from the HEAD branch to the MC_4_6_1_PRE branch. This fixes the so-called OpenSSH bug. Roland ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel

Re: Release procedure

2005-06-07 Thread Jindrich Novy
Hello Leonard, mc-devel, On Mon, 2005-06-06 at 23:34 +0200, Leonard den Ottolander wrote: Hello Miguel, On Mon, 2005-06-06 at 22:58, Miguel de Icaza wrote: I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what

Re: Release procedure

2005-06-07 Thread Roland Illig
Jindrich Novy wrote: --- mc-4.6.1a/src/widget.c.fixes2005-06-06 15:08:52.202559824 +0200 +++ mc-4.6.1a/src/widget.c 2005-06-06 15:08:29.120068896 +0200 @@ -2363,7 +2363,7 @@ buttonbar_set_label_data (Dlg_head *h, i void buttonbar_set_label (Dlg_head *h, int idx, const char *text,

Re: Last TODO items before release [was Re: Release procedure]

2005-06-07 Thread Leonard den Ottolander
On Tue, 2005-06-07 at 20:02, Leonard den Ottolander wrote: Before releasing 4.6.1 there are a few things to be done: - Backporting gcc-4 signedness fixes I understand many of the developers doubt the quality of the warnings from gcc-4, and hence the fixes proski created for them. We can look at

Re: Release procedure

2005-06-07 Thread William Scott Lockwood III
wget http://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz --14:28:46-- http://primates.ximian.com/%7Emiguel/mc/tar.mc-4.6.1-pre5a.tar.gz = `tar.mc-4.6.1-pre5a.tar.gz' Resolving primates.ximian.com... 130.57.169.34 Connecting to primates.ximian.com[130.57.169.34]:80...

Re: New Maintainer for MC Project

2005-06-07 Thread Pavel Roskin
Hello! Sorry, I should have answered this long ago. On Sat, 2005-06-04 at 05:58 -0700, Fudoki wrote: Greetings All! My name is Terry Wilkinson and I am on the Docs Team and also am the Public Relations Coordinator for the Krusader File Manager Project

Re: New Maintainer for MC Project?

2005-06-07 Thread Roland Illig
Fudoki Wilkinson wrote: Roland must be Mr. Icaza's protege, just slinging abuse and saying no before the offer is even on the table; In my opinion the offer of taking over mc could not have been expressed more clearly. I had already been on the table when I said no. The latest statement from

Re: New Maintainer for MC Project

2005-06-07 Thread Fudoki Wilkinson
From - Thu Jun 2 20:53:04 2005X-Account-Key: account1X-UIDL: [EMAIL PROTECTED]X-Mozilla-Status: 0013X-Mozilla-Status2: Return-Path: [EMAIL PROTECTED]Received: from ibm46aec.bellsouth.net ([64.105.159.118]) by imf12aec.mail.bellsouth.net with ESMTP id [EMAIL PROTECTED]

Re: New Maintainer for MC Project

2005-06-07 Thread Fudoki Wilkinson
Hello, Terry!Now I see you actually understand me better than many mc contributorsand better than I initially thought. Maybe I was too harsh in myinitial e-mail. There was a significant fallout in my inbox caused by the recent discussions, and I had to deal with it while being verypressed with

Re: New Maintainer for MC Project?

2005-06-07 Thread Roland Illig
Fudoki Wilkinson wrote: On 6/7/05, Roland Illig [EMAIL PROTECTED] wrote: Fudoki Wilkinson wrote: mainly due to his private notes to our Marketing Manager blasting the MC Project and it's Maintainers. private notes? I only wrote mails to public mailing lists, mc-devel in particular. So this

Re: Last TODO items before release [was Re: Release procedure]

2005-06-07 Thread Roland Illig
Leonard den Ottolander wrote: Roland fixed a memory leak in HEAD but he doesn't know where again g. I have thoroughly check the changes to mcedit, where I assumed the memory leak to have been. The only things I found were two instances where I had replaced use of the catstrs() function with

old bug in achown.c

2005-06-07 Thread Roland Illig
This bug is perhaps the oldest one I could find. Well, to be honest, it wasn't me but the SunPro compiler: /tmp/mc-current-build/src/src/achown.c, line 517: warning: enum type mismatch: arg #2 It's not only gcc's job to emit warnings ... ;) Roland Index: achown.c

Fwd: New Maintainer for MC Project

2005-06-07 Thread Fudoki Wilkinson
Part 1 of 2-- Forwarded message --From: Fudoki Wilkinson [EMAIL PROTECTED] Date: Jun 7, 2005 9:50 PMSubject: Re: New Maintainer for MC ProjectTo: MC Devel List mc-devel@gnome.org, [EMAIL PROTECTED] Pavel, Below is your note posted today. Below that the full text of the letter,

Re: old bug in achown.c

2005-06-07 Thread Oswald Buddenhagen
On Wed, Jun 08, 2005 at 02:45:32AM +0200, Roland Illig wrote: - advanced_chown_callback (h, KEY_RIGHT, DLG_KEY); + advanced_chown_callback (h, DLG_KEY, KEY_RIGHT); heh, wow ... another a good example of why #define is bad and enum is good - provided you have a sufficiently