From aliakc at web.de Tue Dec 2 13:43:19 2003 From: aliakc at web.de (Ali Akcaagac) Date: Tue, 02 Dec 2003 14:43:19 +0100 Subject: Rotating Dash is not working anymore. Message-ID: <1070372599.1757.0.camel@localhost> ... Hello, as the topic says the Rotating Dash somehow is not working correctly anymore in current MC HEAD ... From proski at gnu.org Thu Dec 4 08:16:18 2003 From: proski at gnu.org (Pavel Roskin) Date: Thu, 04 Dec 2003 03:16:18 -0500 (EST) Subject: Rotating Dash is not working anymore. In-Reply-To: <1070372599.1757.0.camel@localhost> References: <1070372599.1757.0.camel@localhost> Message-ID: On Tue, 2 Dec 2003, Ali Akcaagac wrote: > ... Hello, as the topic says the Rotating Dash somehow is not working > correctly anymore in current MC HEAD ... It works for me, but the background color of the dash changes erratically. So typical for mc - you look for one bug but find another. Try this patch, it preserves the cursor position and sets the color: ========================== --- src/layout.c +++ src/layout.c @@ -851,6 +851,7 @@ void print_vfs_message (char *msg, ...) void rotate_dash (void) { + int col, row; static char rotating_dash [] = "|/-\\"; static int pos = 0; @@ -859,8 +860,12 @@ void rotate_dash (void) if (pos >= sizeof (rotating_dash)-1) pos = 0; + + getyx (stdscr, row, col); move (0, COLS-1); + attrset (NORMAL_COLOR); addch (rotating_dash [pos]); + move(row, col); mc_refresh (); pos++; } ========================== The CVS repository is closed because of the security issues (http://savannah.gnu.org/statement.html), but I'll apply this patch as soon as the repository is reopened. If the problem persists, please describe in more details how to reproduce it. Bug reports about all visual effects should be accompanied by the output of "mc -V". I only tested the configuration with internal S-Lang. -- Regards, Pavel Roskin From egmont at uhulinux.hu Fri Dec 5 02:17:29 2003 From: egmont at uhulinux.hu (Koblinger Egmont) Date: Fri, 5 Dec 2003 03:17:29 +0100 (CET) Subject: files under sysfs (linux kernel 2.6) Message-ID: Hi, Linux kernel 2.6 has a new virtual filesystem, similar to /proc, it is called sysfs and AFAIK it's supposed to be mounted to /sys. As this one has virtual files, just as /proc, their size is not known in advance, hence stat returns a fix value for the file size. For /proc, 0 is returned for the size by stat, however, I can perfectly view those file with mc or mcedit. Under /sys, stat usually returns 4096 for these files, but their contents is usually much more shorter, only a few bytes. At least joe and vim can open them perfectly. However, mc's viewer and editor fills up the buffer with zero bytes up to the length of 4096 bytes. It shouldn't do so... Tested with mc 4.6.0, kernel 2.6.0-test11. bye, Egmont From biro_arpad at yahoo.com Sat Dec 6 12:16:12 2003 From: biro_arpad at yahoo.com (Arpad Biro) Date: Sat, 6 Dec 2003 04:16:12 -0800 (PST) Subject: Small bug (?) in MC 4.6.0 Message-ID: <20031206121612.8876.qmail@web13706.mail.yahoo.com> Hi, There seems to be a small bug in MC 4.6.0's internal viewer: when searcing in "man" files, highlighted entries are found twice. To see it in action, try searching for "SYNOPSIS" in a "man" file displayed by the internal viewer. Arpad Biro __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ From proski at gnu.org Sat Dec 6 21:38:23 2003 From: proski at gnu.org (Pavel Roskin) Date: Sat, 06 Dec 2003 16:38:23 -0500 (EST) Subject: files under sysfs (linux kernel 2.6) In-Reply-To: References: Message-ID: On Fri, 5 Dec 2003, Koblinger Egmont wrote: > Linux kernel 2.6 has a new virtual filesystem, similar to /proc, it is > called sysfs and AFAIK it's supposed to be mounted to /sys. > > As this one has virtual files, just as /proc, their size is not known in > advance, hence stat returns a fix value for the file size. > > For /proc, 0 is returned for the size by stat, however, I can perfectly > view those file with mc or mcedit. > > Under /sys, stat usually returns 4096 for these files, but their contents > is usually much more shorter, only a few bytes. At least joe and vim can > open them perfectly. However, mc's viewer and editor fills up the buffer > with zero bytes up to the length of 4096 bytes. I confirm this problem. It's not hard to fix. The file size should be adjusted when the end of file is encountered. I hope the bug tracking system will be fixed soon. The CVS repository went up yesterday for a short time, but today it's down again. -- Regards, Pavel Roskin From proski at gnu.org Sat Dec 6 21:39:23 2003 From: proski at gnu.org (Pavel Roskin) Date: Sat, 06 Dec 2003 16:39:23 -0500 (EST) Subject: Small bug (?) in MC 4.6.0 In-Reply-To: <20031206121612.8876.qmail@web13706.mail.yahoo.com> References: <20031206121612.8876.qmail@web13706.mail.yahoo.com> Message-ID: On Sat, 6 Dec 2003, Arpad Biro wrote: > Hi, > > There seems to be a small bug in MC 4.6.0's internal viewer: when > searcing in "man" files, highlighted entries are found twice. To see it > in action, try searching for "SYNOPSIS" in a "man" file displayed by the > internal viewer. Confirmed. You may want to use the bug tracking system when it's fixed. -- Regards, Pavel Roskin From admin at alacakdefteri.com Sat Dec 6 19:39:08 2003 From: admin at alacakdefteri.com (A.Kadir YILMAZ) Date: Sat, 6 Dec 2003 21:39:08 +0200 Subject: Alacak Defteri 2.0 Message-ID: <200312061939.hB6Jd8i15109@ensim.rackshack.net> An HTML attachment was scrubbed... URL: From timur at com.bat.ru Thu Dec 11 16:40:29 2003 From: timur at com.bat.ru (Timur I. Bakeyev) Date: Thu, 11 Dec 2003 17:40:29 +0100 Subject: Some more g_strdup_printf() eliminated In-Reply-To: <200311241612.hAOGCHYO030470@email.zp.ua> References: <200311241612.hAOGCHYO030470@email.zp.ua> Message-ID: <20031211164029.GA98555@com.bat.ru> Hi all! Just a note - if you dealing with paths, it's HIGHLY recommended to use PATH_SEP instead of "/", and corresponding char constant instead of '/'. Please! WBR, Timur. On Mon, Nov 24, 2003 at 06:12:17PM +0200, Andrew V. Samoilov wrote: > vfs/ChangeLog: > * direntry.c (vfs_s_resolve_symlink): Eliminate g_strdup_printf(). > (vfs_s_fullpath): Ditto. > > --- vfs/direntry.c > +++ vfs/direntry.c > @@ -217,7 +217,7 @@ vfs_s_resolve_symlink (struct vfs_class > /* make full path from relative */ > if (*linkname != PATH_SEP) { > char *fullpath = vfs_s_fullpath (me, entry->dir); > - fullname = g_strdup_printf ("%s/%s", fullpath, linkname); > + fullname = g_strconcat (fullpath, "/", linkname, NULL); > linkname = fullname; > g_free (fullpath); > } > @@ -522,7 +522,7 @@ vfs_s_fullpath (struct vfs_class *me, st > ino = ino->ent->dir; > if (ino == ino->super->root) > break; > - newpath = g_strdup_printf ("%s/%s", ino->ent->name, path); > + newpath = g_strconcat (ino->ent->name, "/", path, NULL); > g_free (path); > path = newpath; > } From proski at gnu.org Mon Dec 15 08:17:50 2003 From: proski at gnu.org (Pavel Roskin) Date: Mon, 15 Dec 2003 03:17:50 -0500 (EST) Subject: Some more g_strdup_printf() eliminated In-Reply-To: <20031211164029.GA98555@com.bat.ru> References: <200311241612.hAOGCHYO030470@email.zp.ua> <20031211164029.GA98555@com.bat.ru> Message-ID: On Thu, 11 Dec 2003, Timur I. Bakeyev wrote: > Hi all! > > Just a note - if you dealing with paths, it's HIGHLY recommended to use > PATH_SEP instead of "/", and corresponding char constant instead of '/'. > > Please! Can you explain the reason? The Windows port was dropped. If support for different path separators is still desired, the Windows version should support both slash and backslash. Comparing a character with PATH_SEP is not going to work if more than one path separator is to be supported. Also, I believe VFS has always been using forward slashes. If we want to support different path separators, somebody should describe the syntax of VFS paths first. I don't see any reason to keep this "political correctness" alive until the syntax of VFS paths is documented. I'd rather remove PATH_SEP than have an illusion of portability. -- Regards, Pavel Roskin From proski at gnu.org Mon Dec 15 09:08:22 2003 From: proski at gnu.org (Pavel Roskin) Date: Mon, 15 Dec 2003 04:08:22 -0500 (EST) Subject: Update on Savannah compromise Message-ID: Hello! As you probably know, savannah.gnu.org was compromised recently. The current status of the site can be found here: http://savannah.gnu.org/statement.html CVS access is anonymous only. Write access will be restored using ssh2 keys. Bugs and patches are unavailable. I'm afraid it will take weeks before Savannah is functional again. There is a known good backup dated September 16. The difference between that version and the current CVS version has been posted here: ftp://ftp.gnu.org/savannah/changesets/mc-changes.tar.gz The changes are represented as separate diffs for every revision. The uncompressed size of mc-changes.tar.gz is 3.3 megabytes. Changes in *.c and *.h files under src directory alone comprise more than 800 kilobytes. It will take a lot of time to review all those patches. But it needs to be done so that the project can go on. This is a serious setback for the project, but I'm sure Savannah and GNU Midnight Commander will overcome the difficulties. It was my decision to move development to Savannah. I still believe it was a right decision. We are unlucky to have been hit, but I don't think the GNOME repository was more secure at the time of the move. I'll be on vacation between December 25 and January 11. I'll try to check the moderation queues for the mailing lists from time to time. I hoped to release version 4.6.1 before that, but now it's clear that it's not going to happen. However, I'll try to complete audit of the changes during the next week. If you have any patches or bugreports, please post them to this mailing list while Savannah is down. You may not get a fast reply, but it's still better than to do nothing. If Savannah doesn't recover by January 11, the development will be moved elsewhere, probably to SourceForge. -- Regards, Pavel Roskin From tkuiper at t-online.fr Fri Dec 19 11:53:01 2003 From: tkuiper at t-online.fr (Thomas Kuiper) Date: Fri, 19 Dec 2003 12:53:01 +0100 Subject: FTP inside mc Message-ID: <20031219115301.GA12312@t-online.fr> Hello, I find the FTP interface of mc really useful and I'm willing to develop an extension to it to support FTP profiles. Right now its only possible to connect to a URL style address and its quite annoying to type or search/remember some frequently used FTP sites. I'm thinking about a interface right now and thing it should be like this: Menu Left/Right->Ftp Link opens: ------------------ FTP Link ----------------- Profile Name: ____________________[^] Host: ____________________ User Name: ____________________ Password: ____________________ Port: 22__________________ Init. Remote Dir: ____________________ Comment: ____________________ [ ] Use passive transfer [ ] Don't store password in profile [< Ok >] [ Cancel ] [ Delete Profile ] --------------------------------------------- Rules: + If no Username was specified user "anonymous" is used (with password configured under Options->"Virtual File System Settings". + Profile gets automatically saved when changed or name specified. + If the password isn't supposed to be stored in the profile its asked in a new dialog. + Returns to the dialog in case a connection failed. + Suggestions? Thomas From proski at gnu.org Fri Dec 19 22:24:09 2003 From: proski at gnu.org (Pavel Roskin) Date: Fri, 19 Dec 2003 17:24:09 -0500 (EST) Subject: FTP inside mc In-Reply-To: <20031219115301.GA12312@t-online.fr> References: <20031219115301.GA12312@t-online.fr> Message-ID: On Fri, 19 Dec 2003, Thomas Kuiper wrote: > Hello, > > I find the FTP interface of mc really useful and I'm willing to develop > an extension to it to support FTP profiles. Right now its only possible > to connect to a URL style address and its quite annoying to type or > search/remember some frequently used FTP sites. . From the hints: Hint: Key frequently visited ftp sites in the hotlist: type C-\. That should solve the problem with frequently visited sites. > I'm thinking about a interface right now and thing it should be like > this: > > Menu Left/Right->Ftp Link opens: > > ------------------ FTP Link ----------------- > Profile Name: ____________________[^] > Host: ____________________ > User Name: ____________________ > Password: ____________________ > Port: 22__________________ > Init. Remote Dir: ____________________ > Comment: ____________________ > > [ ] Use passive transfer > [ ] Don't store password in profile > > [< Ok >] [ Cancel ] [ Delete Profile ] > > --------------------------------------------- > > Rules: > > + If no Username was specified user "anonymous" is used (with password > configured under Options->"Virtual File System Settings". > + Profile gets automatically saved when changed or name specified. > + If the password isn't supposed to be stored in the profile its asked > in a new dialog. > + Returns to the dialog in case a connection failed. > + > > Suggestions? I don't quite understand the idea of profiles and whether you are going to use them for FTP connections only, or for fish and samba connections as well. Separate entries for host, username, password and remote directory - should be OK. Those who want to enter the complete URL can do it on the command line. "Comment" - I have no idea what it means. Maybe you want to create an alternative to the hotlist? It was suggested many times, but every time it turned out that the author of the idea wasn't aware of the hotlist. I believe the hotlist has a visibility problem. It's not noticed even by those who need it. Hints don't really help - most users ignore them. Maybe if the "comment" field was used as the hotlist label and was labeled "hotlist label" instead, more users would be aware of the hotlist. "Use passive transfer" - good idea, but needs some work on the VFS side. The hotlist works with directory names, which are plain strings. It doesn't save any hidden attributes, and rightly so. There is currently no way to specify FTP options in the VFS path. There is support for options in fish, which could be extended. In fact, the general syntax of VFS path is undocumented. There is no way to use "@" in usernames, and there have been many complaints about it. I think we should start with "pen and paper" and agree on the syntax of VFS path, including options and ways to escape characters. In case of smbfs, there should be a way to put the workgroup in the URL, so that VFS stops calling nontrivial user interface to request it. Also, the alternate path notations such as ftp://... and rsh://... should be agreed on and documented. Once we agree on the design, the functions for parsing the VFS path should be fixed to implement the new standard. After that we could write the frontend that would create the VFS path in the new syntax and optionally save the new path in the hotlist. "Don't store password in profile" - I still don't understand the idea of profiles. If you agree on reusing the hotlist, we could think how to implement this. Maybe the password should be saved in .netrc, the standard place for all FTP clients? smbfs and fish would save passwords elsewhere, maybe in ~/.mc/fish_pass and ~/.mc/smbfs_pass respectively. . From the user point of view, it would be great if the password was asked for in the same dialog rather than separately, regardless of whether it's saved. But from the security standpoint, it's better not to have the password as part of the VFS path. I tend to think that the user interface should not allow creating a path with the password. However, the user:password syntax should be accepted if entered on the command line. The existing code has some ad-hoc solutions for hiding the password from the path, but I think it's not the best solution. It's easy to forget to strip the password. To sum up, we should start with backend design before writing pretty interfaces. -- Regards, Pavel Roskin From ossi at kde.org Fri Dec 19 23:57:08 2003 From: ossi at kde.org (Oswald Buddenhagen) Date: Sat, 20 Dec 2003 00:57:08 +0100 Subject: FTP inside mc In-Reply-To: References: <20031219115301.GA12312@t-online.fr> Message-ID: <20031219235708.GA8424@ugly.local> On Fri, Dec 19, 2003 at 05:24:09PM -0500, Pavel Roskin wrote: > I think we should start with "pen and paper" and agree on the syntax > of VFS path, including options and ways to escape characters. > this topic was raised two (or more) times on the xdg-list (freedesktop.org) in the last few months. i think it would be a good idea if you cooperated with these guys on that. fwiw, i have no idea, whether something was actually written down already ... greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. From proski at gnu.org Sat Dec 20 08:12:58 2003 From: proski at gnu.org (Pavel Roskin) Date: Sat, 20 Dec 2003 03:12:58 -0500 (EST) Subject: FTP inside mc In-Reply-To: <20031219235708.GA8424@ugly.local> References: <20031219115301.GA12312@t-online.fr> <20031219235708.GA8424@ugly.local> Message-ID: On Sat, 20 Dec 2003, Oswald Buddenhagen wrote: > On Fri, Dec 19, 2003 at 05:24:09PM -0500, Pavel Roskin wrote: > > I think we should start with "pen and paper" and agree on the syntax > > of VFS path, including options and ways to escape characters. > > > this topic was raised two (or more) times on the xdg-list > (freedesktop.org) in the last few months. i think it would be a good > idea if you cooperated with these guys on that. fwiw, i have no idea, > whether something was actually written down already ... I think you mean this: http://www.redhat.com/archives/xdg-list/2003-September/thread.html#00110 I don't think any participation from mc developers would be welcome at this stage. It's a proposal for desktop environments and its designed to be adopted by them. What can mc developers contribute to that project? Additional requirements (e.g. zip inside zip)? Additional limitations (no D-BUS dependency, please)? Additional compatibility issues? When the proposal is ready, it may be worth considering if it can be implemented without adding too much complexity to the project. What I want is a consistent description of what is already implemented in mc, maybe with minor changes to address currently unresolved issues, such as quoting "@" in the username. Adopting a radically different format would break existing hotlists. -- Regards, Pavel Roskin From tkuiper at t-online.fr Sat Dec 20 12:01:59 2003 From: tkuiper at t-online.fr (Thomas Kuiper) Date: Sat, 20 Dec 2003 13:01:59 +0100 Subject: FTP inside mc In-Reply-To: References: <20031219115301.GA12312@t-online.fr> Message-ID: <20031220120159.GA4640@t-online.fr> On Fri, Dec 19, 2003 at 05:24:09PM -0500, Pavel Roskin wrote: > On Fri, 19 Dec 2003, Thomas Kuiper wrote: > > > Hello, > > > > I find the FTP interface of mc really useful and I'm willing to develop > > an extension to it to support FTP profiles. Right now its only possible > > to connect to a URL style address and its quite annoying to type or > > search/remember some frequently used FTP sites. > > >From the hints: > Hint: Key frequently visited ftp sites in the hotlist: type C-\. > > That should solve the problem with frequently visited sites. Thats just a history like browsers offer them. It doesn't give you the possibility to "bookmark" specific sites. > I don't quite understand the idea of profiles and whether you are going to > use them for FTP connections only, or for fish and samba connections as > well. The point of profiles is that you can rapidly type the name of them and browse existing profiles quickly instead of having to fiddle around with the history which also includes all sites you visited only for one time. Point is to make "mc" a good FTP Client. And every FTP Client supports profiles or some bookmark system. mc already offers everything a FTP Client basically need (two windows with local file system in one and remote file system in the second one, etc.). > Separate entries for host, username, password and remote directory - > should be OK. Those who want to enter the complete URL can do it on the > command line. I think for a enduser its much more clear. Don't expect anyone to understand how URI's work. But of course the help of mc is very clear there. I don't want to drop the ideas of URI's. They could continue to be working. Its not necessary to drop the simple "one line" FTP Link dialog. It could it be set in the options if one prefers the simple FTP Link dialog. > "Comment" - I have no idea what it means. Maybe you want to create an > alternative to the hotlist? It was suggested many times, but every time > it turned out that the author of the idea wasn't aware of the hotlist. Comment is just a pointer for you what kind of site that is. People who use FTP servers frequently or have mirror sites in it with just an IP for example its nice to have a description what used the be behind this. You can also store the same site many times with diffrent directories and with long paths its easier to read the comment instead of searching in the long path. > "Use passive transfer" - good idea, but needs some work on the VFS side. > The hotlist works with directory names, which are plain strings. It > doesn't save any hidden attributes, and rightly so. There is currently no > way to specify FTP options in the VFS path. There is support for options > in fish, which could be extended. > In fact, the general syntax of VFS path is undocumented. There is no way > to use "@" in usernames, and there have been many complaints about it. > I think we should start with "pen and paper" and agree on the syntax of > VFS path, including options and ways to escape characters. In case of > smbfs, there should be a way to put the workgroup in the URL, so that VFS > stops calling nontrivial user interface to request it. Also, the > alternate path notations such as ftp://... and rsh://... should be agreed > on and documented. True. It shouldn't be too hard to redesign the VFS Path a little bit to make it possible for options or extensions. Not breaking it with too many escape characters in the same time of course. There are some more issues with passive FTP and its probably quite hard to implement but I just added it to the silly dialog I made cause I think FTP Clients must have it :) > "Don't store password in profile" - I still don't understand the idea of > profiles. If you agree on reusing the hotlist, we could think how to > implement this. Well the password with be asked each time. Check out TKFTP, or the popular windows clients like CuteFTP, WsFTP and so on. > Maybe the password should be saved in .netrc, the standard place for all > FTP clients? smbfs and fish would save passwords elsewhere, maybe in > ~/.mc/fish_pass and ~/.mc/smbfs_pass respectively. I'd prefer to store everything in ~/.mc/ftp-profiles so its easier to backup. > >From the user point of view, it would be great if the password was asked > for in the same dialog rather than separately, regardless of whether it's > saved. But from the security standpoint, it's better not to have the > password as part of the VFS path. I tend to think that the user interface > should not allow creating a path with the password. However, the > user:password syntax should be accepted if entered on the command line. Sometimes people use security by obscurity. Which means they have FTP logins like public/public or its just an account to push something in /incoming where nobody cares if the password is "stolen". > The existing code has some ad-hoc solutions for hiding the password from > the path, but I think it's not the best solution. It's easy to forget to > strip the password. > > To sum up, we should start with backend design before writing pretty > interfaces. Thats what I thought too and thats why I mailed here. Otherwise I would just make it work for myself and send you a diff for your amusement :) But I think its more nice if other peoples ideas are pleased and if it gets in the original source tree :) I set myself a deadly to mid January when I definetly start coding FTP Profiles into mc. Its my main concern but in the end I may just end up on my own and provide some third party supply for mc. Speaking of that mc could also have "module" support for VFS things... but that sounds like work for a whole year until its running completly... tell if you can't follow what I mean. I'll see what other ideas come up here and will post my functional specification what I will implement (considering but not implementing necessarily all what was written in this list) in early January. Now think :) Thomas From alpha at informatica.agh.edu.pl Sat Dec 20 16:25:41 2003 From: alpha at informatica.agh.edu.pl (Adam Byrtek / alpha) Date: Sat, 20 Dec 2003 17:25:41 +0100 Subject: FTP inside mc In-Reply-To: <20031220120159.GA4640@t-online.fr> References: <20031219115301.GA12312@t-online.fr> <20031220120159.GA4640@t-online.fr> Message-ID: <20031220162541.GA18457@mentat.localdomain> On Sat, Dec 20, 2003 at 01:01:59PM +0100, Thomas Kuiper wrote: > > That should solve the problem with frequently visited sites. > > Thats just a history like browsers offer them. It doesn't give you > the possibility to "bookmark" specific sites. It does. Pavel didn't write about 'History' (Alt+H), but 'Hotlist' (Ctrl+\) -- _.|._ |_ _. : Adam Byrtek /alpha alpha at debian.org (_|||_)| |(_| : pgp 0xB25952C0 | From atfield-dt at durchnull.de Sun Dec 21 18:21:37 2003 From: atfield-dt at durchnull.de (Rudolf Polzer) Date: Sun, 21 Dec 2003 19:21:37 +0100 Subject: BUG: no #! line in shell scripts created for menu commands Message-ID: <20031221182137.GA8363@anou.durchnull.ath.cx> rpolzer at katsuragi ~ $ mc -V GNU Midnight Commander 4.6.0 Virtual File System: tarfs, extfs, cpiofs, ftpfs, fish, smbfs With builtin Editor Using system-installed S-Lang library with terminfo database With subshell support as default With support for background operations With mouse support on xterm With internationalization support With multiple codepages support rpolzer at katsuragi ~ $ uname -a FreeBSD katsuragi.durchnull.ath.cx 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10 #6: Mon Nov 10 16:54:07 CET 2003 root at katsuragi.durchnull.ath.cx:/usr/src/sys/i386/compile/DIV0_KERNEL i386 I have lines like p add the files to playd (TEMP) playd put_end prepend %s in my menu file. Now I noticed I get a "cannot execute binary file" error message when the file name contains non-ASCII characters. Looking at the temporary file named in the error message, I saw that the #! line was missing. And really, adding a #!/bin/sh line worked: p add the files to playd (TEMP) #!/bin/sh playd put_end prepend %s So what I first thought was that I misread the documentation. But even the examples don't contain the shebang line. So I see two possible ways to fix this bug: a) document it and correct the examples b) add a "correct" shebang line (#!$SHELL? #!/bin/sh? User-defined setting?) in these temporary files Rudolf Polzer From andrew at email.zp.ua Mon Dec 22 12:06:28 2003 From: andrew at email.zp.ua (Andrew V. Samoilov) Date: Mon, 22 Dec 2003 14:06:28 +0200 (EET) Subject: BUG: no #! line in shell scripts created for menu commands In-Reply-To: <20031221182137.GA8363@anou.durchnull.ath.cx> Message-ID: <200312221206.hBMC6SiA012551@email.zp.ua> > I have lines like > > p add the files to playd (TEMP) > playd put_end prepend %s > > in my menu file. Now I noticed I get a "cannot execute binary file" > error message when the file name contains non-ASCII characters. Looking > at the temporary file named in the error message, I saw that the #! line > was missing. And really, adding a #!/bin/sh line worked: > > p add the files to playd (TEMP) > #!/bin/sh > playd put_end prepend %s > > So what I first thought was that I misread the documentation. But even the > examples don't contain the shebang line. So I see two possible ways to fix > this bug: > > a) document it and correct the examples > b) add a "correct" shebang line (#!$SHELL? #!/bin/sh? User-defined setting?) > in these temporary files Patch attached. -- Regards, Andrew V. Samoilov. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: user.c.diff URL: From proski at gnu.org Tue Dec 23 06:23:06 2003 From: proski at gnu.org (Pavel Roskin) Date: Tue, 23 Dec 2003 01:23:06 -0500 (EST) Subject: Savannah is back online Message-ID: Hello! Savannah is back online. See more details on http://savannah.gnu.org/ The anonymous access uses ssh 2 now. Make sure you have ssh installed and set CVS_RSH to ssh in the environment. To convert an existing anonymous working directory to the new CVS root, use cvschroot.pl script from http://www.red-bean.com/cvsutils/releases/cvsutils-0.2.0.tar.gz and run following in the top-level directory of the source tree: cvschroot.pl :ext:anoncvs at savannah.gnu.org:/cvsroot/mc For new checkouts see http://savannah.gnu.org/cvs/?group=mc -- Regards, Pavel Roskin From dmi_a at qnx.org.ru Tue Dec 23 12:50:34 2003 From: dmi_a at qnx.org.ru (Dmitry Alexeyev) Date: Tue, 23 Dec 2003 15:50:34 +0300 Subject: syntax small fixes Message-ID: <200312231550.34654.dmi_a@qnx.org.ru> Hello! Here are small fixes for syntax/. php.synatx: remove duplicate mail keyword, added two new words spec.syntax: Url, and encoding in summary sql.syntax: some keywords added syntax.c: fix mcedit crash if .syntax file has more than 1024 keywords Syntax: highlight *.h.in as *.h, *.spec.in as *.spec, *.hxx as *.h FAQ: smally typo fix WBR, Dmitry -------------- next part -------------- A non-text attachment was scrubbed... Name: php.syntax.diff Type: text/x-diff Size: 988 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: spec.syntax.diff Type: text/x-diff Size: 653 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sql.syntax.diff Type: text/x-diff Size: 2249 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Syntax.diff Type: text/x-diff Size: 608 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: syntax.c.diff Type: text/x-diff Size: 365 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FAQ.diff Type: text/x-diff Size: 462 bytes Desc: not available URL: From Dmitry.Semyonov at oktet.ru Tue Dec 23 14:06:48 2003 From: Dmitry.Semyonov at oktet.ru (Dmitry Semyonov) Date: Tue, 23 Dec 2003 17:06:48 +0300 (MSK) Subject: Put a remark into NEWS about ISO vfs Message-ID: Hello! NEWS file should mention that mc now supports iso images. In my opinion, from the point of user's view this should be much more interesting feature than any technical detail I can found in NEWS currently. As for me, the iso support was the main reason to upgrade to one of mc snapshots after 4.6.0 release. ...Bye..Dmitry. From dmi_a at qnx.org.ru Tue Dec 23 16:50:54 2003 From: dmi_a at qnx.org.ru (Dmitry Alexeyev) Date: Tue, 23 Dec 2003 19:50:54 +0300 Subject: gpm related crash fix Message-ID: <200312231950.54148.dmi_a@qnx.org.ru> Hello! Some days ago I put my linux in pretty weird state, similar to single user mode. In this mode gpmd dies.. The error was in some rc.d level 6 script, which didn't handle `reboot' properly, so returned to login prompt (single user). When I tried to run mc, it crashed. gdb said gpm_fd was -2, and mc only checks for -1. Attached key.c.diff changes checking for == -1 to < 0, which is more general case. view.c.diff fixes warning. WBR, Dmitry -------------- next part -------------- A non-text attachment was scrubbed... Name: key.c.diff Type: text/x-diff Size: 1131 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: view.c.diff Type: text/x-diff Size: 369 bytes Desc: not available URL: From proski at gnu.org Wed Dec 24 07:16:26 2003 From: proski at gnu.org (Pavel Roskin) Date: Wed, 24 Dec 2003 02:16:26 -0500 (EST) Subject: Put a remark into NEWS about ISO vfs In-Reply-To: References: Message-ID: On Tue, 23 Dec 2003, Dmitry Semyonov wrote: > Hello! > > NEWS file should mention that mc now supports iso images. In my opinion, > from the point of user's view this should be much more interesting > feature than any technical detail I can found in NEWS currently. > > As for me, the iso support was the main reason to upgrade to one of mc > snapshots after 4.6.0 release. Done. Thank you! -- Regards, Pavel Roskin From proski at gnu.org Wed Dec 24 07:43:32 2003 From: proski at gnu.org (Pavel Roskin) Date: Wed, 24 Dec 2003 02:43:32 -0500 (EST) Subject: syntax small fixes In-Reply-To: <200312231550.34654.dmi_a@qnx.org.ru> References: <200312231550.34654.dmi_a@qnx.org.ru> Message-ID: On Tue, 23 Dec 2003, Dmitry Alexeyev wrote: > Hello! > > Here are small fixes for syntax/. > > php.synatx: remove duplicate mail keyword, added two new words > spec.syntax: Url, and encoding in summary > sql.syntax: some keywords added > syntax.c: fix mcedit crash if .syntax file has more than 1024 keywords > Syntax: highlight *.h.in as *.h, *.spec.in as *.spec, *.hxx as *.h > FAQ: smally typo fix I have committed all your patches (including the other message) except the last part of the patch for sql.syntax. It's not explained. Maybe you added it by error. Keywords prevent recognition of the end of the context, so there may be side bad effect of that change. Thank you for your work! -- Regards, Pavel Roskin From dmi_a at qnx.org.ru Wed Dec 24 08:37:11 2003 From: dmi_a at qnx.org.ru (Dmitry Alexeyev) Date: Wed, 24 Dec 2003 11:37:11 +0300 Subject: syntax small fixes In-Reply-To: References: <200312231550.34654.dmi_a@qnx.org.ru> Message-ID: <200312241137.11352.dmi_a@qnx.org.ru> > > I have committed all your patches (including the other message) Thank you! > except the last part of the patch for sql.syntax. It's not > explained. Maybe you added it by error. Keywords prevent > recognition of the end of the context, so there may be side bad > effect of that change. Actually no. \\' added for dumps from web-forums, which have \' inside of text strings. So, I have: INSERT .... VALUES( 'That\'s a string'); Syntax highliughting works between 'That\' and after 's a string'. adding keyword \\' is kinda cheating, but after I have added it I saw same things in c.syntax, php.syntax and so on. WBR, Dmitry From proski at gnu.org Wed Dec 24 17:48:22 2003 From: proski at gnu.org (Pavel Roskin) Date: Wed, 24 Dec 2003 12:48:22 -0500 (EST) Subject: 4.6.1-pre1 pre-release Message-ID: Hello! I have released version 4.6.1-pre1. Please test it. It will become 4.6.1 with minimal changes. News after version 4.6.0: Add --with-glib12 option to configure to force using glib 1.2.x. Add --disable-background option to disable background support. Background support now uses pipes instead of UNIX sockets. libX11 is loaded dynamically using gmodule if possible. Screen saving is now supported on FreeBSD console. Support for SCO UNIX has been removed. User is warned if one mc is run from another. VFS supports iso9660 images. I'll be away until January 11. Bug reports and patches are still welcome. Please help each other, don't ignore questions in mailing lists. Savannah is working now. Project members, please update your passwords and upload ssh2 keys. -- Regards, Pavel Roskin From andrew at email.zp.ua Fri Dec 26 14:56:56 2003 From: andrew at email.zp.ua (Andrew V. Samoilov) Date: Fri, 26 Dec 2003 16:56:56 +0200 (EET) Subject: One more corner case in `ls -lga` parsing and big minors in Solaris Message-ID: <200312261456.hBQEuuTh007172@email.zp.ua> Hello, this patch allow to parse strings like crw------- 1 root sys 109,515 Oct 11 2002 pci at 9,700000:hpc2_slot5 BTW, as you can see minor is more than 256 and now it is shown as 3 in current mc implementation. -- Regards, Andrew V. Samoilov. From andrew at email.zp.ua Fri Dec 26 15:26:38 2003 From: andrew at email.zp.ua (Andrew V. Samoilov) Date: Fri, 26 Dec 2003 17:26:38 +0200 (EET) Subject: One more corner case in `ls -lga` parsing and big minors in Solaris In-Reply-To: <200312261456.hBQEuuTh007172@email.zp.ua> Message-ID: <200312261526.hBQFQcHj008633@email.zp.ua> Sorry, missed patch and sample lslR file. -- Regards, Andrew V. Samoilov. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: utilvfs.c.patch URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: lslR Type: application/octet-stream Size: 278 bytes Desc: not available URL: From andrew at email.zp.ua Fri Dec 26 17:00:23 2003 From: andrew at email.zp.ua (Andrew V. Samoilov) Date: Fri, 26 Dec 2003 19:00:23 +0200 (EET) Subject: Two more '%s' patterns missed Message-ID: <200312261700.hBQH0NXq013088@email.zp.ua> Hello, P.S. BTW waht about patches for doc/ru/mc.1.in? -- Regards, Andrew V. Samoilov. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: message.patch URL: From biro_arpad at yahoo.com Thu Dec 25 22:48:02 2003 From: biro_arpad at yahoo.com (Arpad Biro) Date: Thu, 25 Dec 2003 14:48:02 -0800 (PST) Subject: 4.6.1-pre1: unlocalized strings? Message-ID: <20031225224802.17494.qmail@web13707.mail.yahoo.com> Hi, It seems that the button texts in the "Advanced chown" dialog cannot be localized in 4.6.1-pre1. (The N_ macro does not seem to do the right thing in src/achown.c.) On the other hand, the "basic" chown dialog displays the localized button texts. Let me know if you cannot reproduce it. Arpad Biro __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ From proski at gnu.org Fri Dec 26 22:36:46 2003 From: proski at gnu.org (Pavel Roskin) Date: Fri, 26 Dec 2003 17:36:46 -0500 Subject: Two more '%s' patterns missed In-Reply-To: <200312261700.hBQH0NXq013088@email.zp.ua> References: <200312261700.hBQH0NXq013088@email.zp.ua> Message-ID: <20031226173646.q8mg215w0k8kgkss@webmail.spamcop.net> Quoting "Andrew V. Samoilov" : > Hello, > > P.S. BTW waht about patches for doc/ru/mc.1.in? I'll be on a very slow connection until January 11. Besides, I brought my ssh key on a USB stick, but I don't have USB here. I hope to solve this problem soon, but in the worst case I'll apply all patches after I return. Please do post patches, they are important. Please try to set up your ssh2 key yourself and commit your patches if they are trivial. I know you have some problems with port 22. I could arrange making a proxy for you if the problem persists. Please reply in private about access. I'm posting here just to tell everyone that I'm still alive and (sort of) accessible. -- Regards, Pavel Roskin From dmartina at excite.com Sat Dec 27 18:33:14 2003 From: dmartina at excite.com (David Martin) Date: Sat, 27 Dec 2003 13:33:14 -0500 (EST) Subject: 4.6.1-pre1 pre-release Message-ID: <20031227183314.6FB0E3DE1@xprdmailfe9.nwk.excite.com> I'm still trying to rearrange my CVS access. In a couple of days I'll check Spanish translations and in the worst case I'll mail my update here. Best wishes for these days. David _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! From dmi_a at qnx.org.ru Sun Dec 28 14:03:09 2003 From: dmi_a at qnx.org.ru (Dmitry Alexeyev) Date: Sun, 28 Dec 2003 17:03:09 +0300 Subject: QNX 6.x fixes Message-ID: <200312281703.09498.dmi_a@qnx.org.ru> Hello! Attached: makefile.syntax.diff: adds define and ended keyrowrds perl.syntax.diff: adds break keyword ext.c.diff: Fixes in QNX 6.x (QNX Neutrino) when guessing file type before viewing file (Long standing bug, which I erroneously tried to fix removed waitpid call long time ago) extfs.c.diff: Fixes bug in extfs, which showed 'Inconsistent extfs archive' on small archives and diffs. Also QNX 6.x (QNX Neutrino) specific WBR, Dmitry -------------- next part -------------- A non-text attachment was scrubbed... Name: perl.syntax.diff Type: text/x-diff Size: 293 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: makefile.syntax.diff Type: text/x-makefile Size: 404 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ext.c.diff Type: text/x-diff Size: 346 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: extfs.c.diff Type: text/x-diff Size: 335 bytes Desc: not available URL: From andrew at email.zp.ua Sun Dec 28 16:44:19 2003 From: andrew at email.zp.ua (Andrew V. Samoilov) Date: Sun, 28 Dec 2003 18:44:19 +0200 (EET) Subject: 4.6.1-pre1: unlocalized strings? In-Reply-To: <20031225224802.17494.qmail@web13707.mail.yahoo.com> Message-ID: <200312281644.hBSGiJJV044477@email.zp.ua> Hi, Arpad! > > It seems that the button texts in the "Advanced chown" dialog cannot > be localized in 4.6.1-pre1. (The N_ macro does not seem to do the right > thing in src/achown.c.) > On the other hand, the "basic" chown dialog displays the localized > button texts. > Let me know if you cannot reproduce it. I cannot reporoduce this. I recreate mc.pot & Russian .po file with update.pl and I can see "&Cancel", "&Set" and other N_ marked messages in these files with right location string (i.e # src/achown.c:68 and so on). What system and gettext do you use? -- Regards, Andrew V. Samoilov. From andrew at email.zp.ua Sun Dec 28 17:27:25 2003 From: andrew at email.zp.ua (Andrew V. Samoilov) Date: Sun, 28 Dec 2003 19:27:25 +0200 (EET) Subject: po/POTFILES.in: vfs/utilvfs.c missed Message-ID: <200312281727.hBSHRP0e046082@email.zp.ua> Hello, also it will be fine to write in NEWS about added Mongolian, Serbian and Lithuanian translations. -- Regards, Andrew V. Samoilov. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: POTFILES.in.patch URL: From alpha at informatica.agh.edu.pl Mon Dec 29 18:51:51 2003 From: alpha at informatica.agh.edu.pl (Adam Byrtek / alpha) Date: Mon, 29 Dec 2003 19:51:51 +0100 Subject: 4.6.1-pre1 pre-release In-Reply-To: References: Message-ID: <20031229185151.GA4153@mentat.localdomain> On Wed, Dec 24, 2003 at 12:48:22PM -0500, Pavel Roskin wrote: > I have released version 4.6.1-pre1. Please test it. It will become 4.6.1 > with minimal changes. What about patches submited to Savannah? You promised that you will resolve (apply or reject) them before the release. Regards Adam -- _.|._ |_ _. : Adam Byrtek /alpha alpha at debian.org (_|||_)| |(_| : pgp 0xB25952C0 | From info at affaz.com Mon Dec 29 09:49:37 2003 From: info at affaz.com (vladimir goriagine) Date: Mon, 29 Dec 2003 10:49:37 +0100 Subject: MC: setting transarent color-mode Message-ID: <3FEFF8B1.9000606@affaz.com> -------- Original Message -------- Subject: (no subject) Date: Sun, 28 Dec 2003 20:18:49 +0100 From: vladimir goriagine To: mc-devel at gnome.org Hi, i'd like to have 'mc' started in NO-COLOR mode *as default* (transparent to background). is it possible with your new version mc-4.6.0 (as it was with mc-4.5.55)? i use fvwm2 desktop with linux slackware 9.1 thanks -- regards From proski at gnu.org Mon Dec 29 21:58:09 2003 From: proski at gnu.org (Pavel Roskin) Date: Mon, 29 Dec 2003 16:58:09 -0500 Subject: 4.6.1-pre1 pre-release In-Reply-To: <20031229185151.GA4153@mentat.localdomain> References: <20031229185151.GA4153@mentat.localdomain> Message-ID: <20031229165809.3az4c80ook44ocoo@webmail.spamcop.net> Quoting Adam Byrtek / alpha : > On Wed, Dec 24, 2003 at 12:48:22PM -0500, Pavel Roskin wrote: > > I have released version 4.6.1-pre1. Please test it. It will become 4.6.1 > > with minimal changes. > > What about patches submited to Savannah? You promised that you will > resolve (apply or reject) them before the release. I promised that under the condition that there will be no security issues forcing the next release. There was a buffer overflow in VFS. -- Regards, Pavel Roskin From dmartina at excite.com Wed Dec 31 10:19:21 2003 From: dmartina at excite.com (David Martin) Date: Wed, 31 Dec 2003 05:19:21 -0500 (EST) Subject: User menu l10n Message-ID: <20031231101921.3872A1E413@xprdmailfe24.nwk.excite.com> The patches to localize the user menu have been in the repository for a while now. The idea was quite easy, so I see little risk in including them, just some time to fix Makefiles. Reminder: We automatically make a dummy (real) C file with all messages used in the stock User menu so that it can be included in the search for localizable strings when updating .po files. In the main code just add the usual stuff _( to check for localized strings. Including the code wouldn't mean pressing translators to have all strings localized for the release. Regards to all. Have a nice day. _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!