Re: listbox hotkeys
On 5/24/15, Mike Smithson mdooli...@gmail.com wrote: It's always bugged me that I can only access the first 10 items with the keys 0-9. [...] Keys a-z are very often used by the menu of the dialog the listbox is in, but keys A-Z are not. [...] Now I can access the top 36 items instead of just the top 10. But isn't it hard to count, say, 27 items mentally? Isn't it easier to just press the arrows repeatedly? I think that's a question the maintainers are going to ask you. (Otherwise I don't see a problem with your code. But you'd want to change the - 55 to - 'A' + 10 and remove the curly brackets (that's their laws).) Anyway, you can do all such tweakings in mc^2 without touching the C code. Here, I translated your code to Lua: https://github.com/mooffie/mc/blob/lua-4.8.14-port/src/lua/tests/snippets/listbox_AZ.lua I've also created a new module today that lets you associate hotkeys with the directories there. Again, no C coding is required. Here's a screenshot (note the yellow arrows): http://www.typo.co.il/~mooffie/mc-lua/docs/html/guide/SCREENSHOTS.md.html#Find_as_you_type__hotkeys__clock (Isn't this feature what you *really* want?) I use Directory hotlist a lot. Constantly, really. A few weeks ago somebody said he's using the File edit/view history of Dos Navigator several hundred times a day[1]. After implementing it (better) in mc^2 I can say the same. I mention it because many times (thanks to its Quick filter entry[2]) one can use it as a replacement for the Directory hotlist dialog. [1] http://www.midnight-commander.org/ticket/280#comment:25 [2] http://www.typo.co.il/~mooffie/mc-lua/docs/html/guide/SCREENSHOTS.md.html#Recently_Visited_Files__xterm_titles ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!?
On Thu, May 28, 2015 at 07:26:22AM -0700, Mike Smithson wrote: Bah. Mc is not over. Things change, that's all. [...] That's my 2 cents worth. Take care, and best wishes for those who are moving on to bigger and better things. Thank you for your labors. I agree 100%. -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | GNU/Linux User #78271 | | FSFE fellow #364 | ++ ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!?
Hi all, I'm another long time user of mc. I've used it on Windows, Solaris, HP-UX, and currently on GNU/Linux (mostly Fedora and CentOS). I use it daily and find it an indispensable tool. Thanks to everyone who's worked on it over the years! If mc development is really coming to an end without new developers, I'm willing to devote a little time to working on it. I'm a C programmer and have submitted patches here and there to other projects like Apache and LibXML2. I don't really care much about new mc features but I would like to see work done on fixing bugs. There are mc bugs that have annoyed me for many years, like the keybinding breakage with with GNOME terminal that happened four or five years back and still isn't fixed. Can someone point me to the developer resources like the source code repo? I guess a good starting point is check out the current code and get it compiling. Do new developers need to create an account anywhere to get access? -Steve On Thu, 2015-05-28 at 20:03 +0100, Michal Pirgl wrote: Hi I have been using mc for many years and I would like to thank to everyone who spent their time on this project. I also cannot promise 20hrs in a week but I would like to participate/develop as much as I can to help in free time. Regards, Michal From: Mike Smithson mdooligan gmail com To: mc-devel gnome org Cc: mc gnome org Subject: Re: mc is over!? Date: Thu, 28 May 2015 07:26:22 -0700 Bah. Mc is not over. Things change, that's all. I've been into mc since I don't know when. The first time I used it. Mid/late 90s I'm guessing. I saw how it floundered in the 4.6 series. I shrugged and kept tweaking and hacking my version. A few years went by and I looked it up again, purely out of curiosity. I was delighted that someone had given it a full work over into the 4.8 series. There were some persistent, puzzling, and very annoying bugs that are now gone. Excellent work, gentlemen. Thank you very much. My list of personal patches went from ~30 down to ~5, where they sit now, mostly minor interface tweaks. Mc works, and it works very well. If development stagnates for a while, so be it. There is actually very little to do. Mc is as close to perfect as software gets. There will always be bugs and minor tweaks, and that's what needs to be worked on, now and forever. Yes, mc in its current incarnation is a model from the 1990s. I like it that way. I'm not a big fan of C++. I also don't like eye candy in a tool that is all about functionality and utility, and I very much appreciate a file manager that can operate when XWindows cannot, or the system is barely bootable. It's the perfect size: big enough to be feature-rich and highly usable, yet small enough that a single individual can (theoretically) get his head around the entire code base. It's also fun to hack. I cannot guarantee 20hrs/week, but I would be very interested to work through bug reports and small enhancement requests at my own pace, and see what I can get done. As a last thought for this email: I suppose what we have here is a complete lack of consensus as to the direction to take if we were to move into a 5.0 series. My thinking is along the lines of complete modularity: a basic interface design (that already exists) and everything else is plugins. What if I want to use mc for inventory control? Make a plugin to work with SQL instead of filesystem. Perhaps there needs to be room for people to experiment with this sort of thing. A 4.9beta branch that starts off as mess and arguments but slowly gets sorted into something with vision. That's my 2 cents worth. Take care, and best wishes for those who are moving on to bigger and better things. Thank you for your labors. -- Peace and Cheer ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!?
Hi I have been using mc for many years and I would like to thank to everyone who spent their time on this project. I also cannot promise 20hrs in a week but I would like to participate/develop as much as I can to help in free time. Regards, Michal From: Mike Smithson mdooligan gmail com To: mc-devel gnome org Cc: mc gnome org Subject: Re: mc is over!? Date: Thu, 28 May 2015 07:26:22 -0700 Bah. Mc is not over. Things change, that's all. I've been into mc since I don't know when. The first time I used it. Mid/late 90s I'm guessing. I saw how it floundered in the 4.6 series. I shrugged and kept tweaking and hacking my version. A few years went by and I looked it up again, purely out of curiosity. I was delighted that someone had given it a full work over into the 4.8 series. There were some persistent, puzzling, and very annoying bugs that are now gone. Excellent work, gentlemen. Thank you very much. My list of personal patches went from ~30 down to ~5, where they sit now, mostly minor interface tweaks. Mc works, and it works very well. If development stagnates for a while, so be it. There is actually very little to do. Mc is as close to perfect as software gets. There will always be bugs and minor tweaks, and that's what needs to be worked on, now and forever. Yes, mc in its current incarnation is a model from the 1990s. I like it that way. I'm not a big fan of C++. I also don't like eye candy in a tool that is all about functionality and utility, and I very much appreciate a file manager that can operate when XWindows cannot, or the system is barely bootable. It's the perfect size: big enough to be feature-rich and highly usable, yet small enough that a single individual can (theoretically) get his head around the entire code base. It's also fun to hack. I cannot guarantee 20hrs/week, but I would be very interested to work through bug reports and small enhancement requests at my own pace, and see what I can get done. As a last thought for this email: I suppose what we have here is a complete lack of consensus as to the direction to take if we were to move into a 5.0 series. My thinking is along the lines of complete modularity: a basic interface design (that already exists) and everything else is plugins. What if I want to use mc for inventory control? Make a plugin to work with SQL instead of filesystem. Perhaps there needs to be room for people to experiment with this sort of thing. A 4.9beta branch that starts off as mess and arguments but slowly gets sorted into something with vision. That's my 2 cents worth. Take care, and best wishes for those who are moving on to bigger and better things. Thank you for your labors. -- Peace and Cheer ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!? - post by Ilia Maslakov on Russian-speaking IT site
Another thing that occurred to me: to save on long term development costs, we should simplify the codebase and get rid of alternatives. Slang and ncurses - keep one, drop the other Glib regex and pcre - same Charset: there are 5 possibilities handled by branches throughout the code (built with/without codeset support; if with: data is utf8 or 8bit, display is utf8 or 8bit) - let the most generic code branch handle all cases. Plugins: IIRC some folks already asked for multiple possible languages to write plugins in - hell, no, choose one and stick to that. Etc... Let's not put things on meta level unless there's a good reason. Let's maintain 1 filemanager, not many at once. e. Sent from mobile ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!?
Btw i fixed gnome-terminal's key sequences about a year ago Sent from mobile On May 28, 2015 11:57 PM, Steve Rainwater srainwa...@ncc.com wrote: Hi all, I'm another long time user of mc. I've used it on Windows, Solaris, HP-UX, and currently on GNU/Linux (mostly Fedora and CentOS). I use it daily and find it an indispensable tool. Thanks to everyone who's worked on it over the years! If mc development is really coming to an end without new developers, I'm willing to devote a little time to working on it. I'm a C programmer and have submitted patches here and there to other projects like Apache and LibXML2. I don't really care much about new mc features but I would like to see work done on fixing bugs. There are mc bugs that have annoyed me for many years, like the keybinding breakage with with GNOME terminal that happened four or five years back and still isn't fixed. Can someone point me to the developer resources like the source code repo? I guess a good starting point is check out the current code and get it compiling. Do new developers need to create an account anywhere to get access? -Steve On Thu, 2015-05-28 at 20:03 +0100, Michal Pirgl wrote: Hi I have been using mc for many years and I would like to thank to everyone who spent their time on this project. I also cannot promise 20hrs in a week but I would like to participate/develop as much as I can to help in free time. Regards, Michal From: Mike Smithson mdooligan gmail com To: mc-devel gnome org Cc: mc gnome org Subject: Re: mc is over!? Date: Thu, 28 May 2015 07:26:22 -0700 Bah. Mc is not over. Things change, that's all. I've been into mc since I don't know when. The first time I used it. Mid/late 90s I'm guessing. I saw how it floundered in the 4.6 series. I shrugged and kept tweaking and hacking my version. A few years went by and I looked it up again, purely out of curiosity. I was delighted that someone had given it a full work over into the 4.8 series. There were some persistent, puzzling, and very annoying bugs that are now gone. Excellent work, gentlemen. Thank you very much. My list of personal patches went from ~30 down to ~5, where they sit now, mostly minor interface tweaks. Mc works, and it works very well. If development stagnates for a while, so be it. There is actually very little to do. Mc is as close to perfect as software gets. There will always be bugs and minor tweaks, and that's what needs to be worked on, now and forever. Yes, mc in its current incarnation is a model from the 1990s. I like it that way. I'm not a big fan of C++. I also don't like eye candy in a tool that is all about functionality and utility, and I very much appreciate a file manager that can operate when XWindows cannot, or the system is barely bootable. It's the perfect size: big enough to be feature-rich and highly usable, yet small enough that a single individual can (theoretically) get his head around the entire code base. It's also fun to hack. I cannot guarantee 20hrs/week, but I would be very interested to work through bug reports and small enhancement requests at my own pace, and see what I can get done. As a last thought for this email: I suppose what we have here is a complete lack of consensus as to the direction to take if we were to move into a 5.0 series. My thinking is along the lines of complete modularity: a basic interface design (that already exists) and everything else is plugins. What if I want to use mc for inventory control? Make a plugin to work with SQL instead of filesystem. Perhaps there needs to be room for people to experiment with this sort of thing. A 4.9beta branch that starts off as mess and arguments but slowly gets sorted into something with vision. That's my 2 cents worth. Take care, and best wishes for those who are moving on to bigger and better things. Thank you for your labors. -- Peace and Cheer ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!?
You ask for source code repo and stuff? Do apologize to me,it's alot of shots andd beers speaking of me right now, but if you ask these questions and couldn't figure out the answers for yourself (I mean: the answer is straight there on the opening homepage of mc) then i'm afraid you might not be the kind of person the project's looking for. Sry Sent from mobile On May 28, 2015 11:57 PM, Steve Rainwater srainwa...@ncc.com wrote: Hi all, I'm another long time user of mc. I've used it on Windows, Solaris, HP-UX, and currently on GNU/Linux (mostly Fedora and CentOS). I use it daily and find it an indispensable tool. Thanks to everyone who's worked on it over the years! If mc development is really coming to an end without new developers, I'm willing to devote a little time to working on it. I'm a C programmer and have submitted patches here and there to other projects like Apache and LibXML2. I don't really care much about new mc features but I would like to see work done on fixing bugs. There are mc bugs that have annoyed me for many years, like the keybinding breakage with with GNOME terminal that happened four or five years back and still isn't fixed. Can someone point me to the developer resources like the source code repo? I guess a good starting point is check out the current code and get it compiling. Do new developers need to create an account anywhere to get access? -Steve On Thu, 2015-05-28 at 20:03 +0100, Michal Pirgl wrote: Hi I have been using mc for many years and I would like to thank to everyone who spent their time on this project. I also cannot promise 20hrs in a week but I would like to participate/develop as much as I can to help in free time. Regards, Michal From: Mike Smithson mdooligan gmail com To: mc-devel gnome org Cc: mc gnome org Subject: Re: mc is over!? Date: Thu, 28 May 2015 07:26:22 -0700 Bah. Mc is not over. Things change, that's all. I've been into mc since I don't know when. The first time I used it. Mid/late 90s I'm guessing. I saw how it floundered in the 4.6 series. I shrugged and kept tweaking and hacking my version. A few years went by and I looked it up again, purely out of curiosity. I was delighted that someone had given it a full work over into the 4.8 series. There were some persistent, puzzling, and very annoying bugs that are now gone. Excellent work, gentlemen. Thank you very much. My list of personal patches went from ~30 down to ~5, where they sit now, mostly minor interface tweaks. Mc works, and it works very well. If development stagnates for a while, so be it. There is actually very little to do. Mc is as close to perfect as software gets. There will always be bugs and minor tweaks, and that's what needs to be worked on, now and forever. Yes, mc in its current incarnation is a model from the 1990s. I like it that way. I'm not a big fan of C++. I also don't like eye candy in a tool that is all about functionality and utility, and I very much appreciate a file manager that can operate when XWindows cannot, or the system is barely bootable. It's the perfect size: big enough to be feature-rich and highly usable, yet small enough that a single individual can (theoretically) get his head around the entire code base. It's also fun to hack. I cannot guarantee 20hrs/week, but I would be very interested to work through bug reports and small enhancement requests at my own pace, and see what I can get done. As a last thought for this email: I suppose what we have here is a complete lack of consensus as to the direction to take if we were to move into a 5.0 series. My thinking is along the lines of complete modularity: a basic interface design (that already exists) and everything else is plugins. What if I want to use mc for inventory control? Make a plugin to work with SQL instead of filesystem. Perhaps there needs to be room for people to experiment with this sort of thing. A 4.9beta branch that starts off as mess and arguments but slowly gets sorted into something with vision. That's my 2 cents worth. Take care, and best wishes for those who are moving on to bigger and better things. Thank you for your labors. -- Peace and Cheer ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Article about Midnight Commander on OpenSource.com
Hello David, On Wed, 27 May 2015 08:14:00 -0400 David Both db...@millennium-technology.com wrote: I like Midnight Commander very much. And I have authored several articles for OpenSource.com. My latest, which has been in progress for several weeks - long before the current developers announced that they would be retiring from the project - is about Midnight Commander. Please check it out. That looks very nice, and thanks for these efforts - I'd say that's the area to which few other folks pay attention to, so it's really helpful to know that some people don't just think what will happen when current generation of mc user will die off, but actually try to make sure that new users get acquainted with it. If you want feedback beyond it's cool!, I'd say that you should use default mc theme for screenshots (to give least surprise to users who actually will try it out). Or perhaps have a screenshot with a default theme and your custom theme and then mention in the text that mc is configurable down to the level of theme and colors. http://opensource.com/business/15/5/midnight-commander -- Best regards, Paul mailto:pmis...@gmail.com ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!? - post by Ilia Maslakov on Russian-speaking IT site
Hi guys, I'm sorry to hear about this... but honestly it didn't surprise me. I think anyone could have seen that this was going to happen, it was only a matter of time - few months, a year or two maybe. What I'm really sad about is that the issue has been raised a couple of times already, yet (former) maintainers didn't take the time and effort to involve new people in the project. I would probably be a smoother transition now if they did. I disagree that a 20hrs/week commitment is required from someone. I don't think it's the right model, and we're unlikely to find anyone. There were times (about a year ago) when I had tons of time to contribute, yet mainstream dev's resources were the bottleneck in reviewing these changes. At other times they were active but I didn't have time to contribute. Instead, I believe it should be a core with 3-5 people who have similar working style and similar vision of the project, and each contribute just a few hours per week. There'd be code review for every nontrivial change, but it could be done by anyone from this team who happens to have some free time. IMO that's the way to avoid bottlenecks, yet guarantee a certain level of code quality. 1-2 people at the core will always be bottleneck, and allowing write access to pretty much anyone who has already contributed something could easily lead to the whole project falling apart due to no clear goals, no clear coding and quality standards, every random hacker with hardly any coding experience pushing for their unmaintainable dirty solution to be committed. And, that being said, while I'm open bringing in brand new folks (e.g. Luca), I'm quite conservative here and would prefer to see him joining conversations at some tickets and posting several great patches (that is, gaining trust in those who already have some) before giving him write access. I'd be happy to see Mooffie on the team right away, his work (along with his style and the contents of the homepage) totally convinced me. I'm sorry to say this, but I myself cannot guarantee anything and cannot make any commitments. I'm spending a long vacation right now where I was planning to do some coding on my primary hobby project (gnome-terminal), and maybe address one or two issues on my secondary hobby project (mc); all subject to my mood. After this vacation I'll start a new job which will require 100% of me. So I'd rather stay an occasional contributor as I am now, and not devote myself to anything with mc. G-t is my personal hobby project in the sense that I do hunt down and address bugs that cause problems to other people but I myself don't particularly care about. Mc never reached this level for me, I never took time to look at bugs and patches that I myself wasn't personally interested in. Don't ask me why it turned out this way, I don't know - maybe it was because on g-t I got quick feedback of my work, whereas on mc I often had to wait for so long that I almost lost interest, and often missed the free time I had when I could have worked on these issues. As for the current segfault issue, I think the broken change should be reverted for now and a .15 released until we come up with a proper solution. Generally it would be good to make releases closer to each other, let's say every 2 months or so, and much sooner when some critical bug sneaks in. This is because I think most users will use mc as shipped by their distros, and distros pick the newest tarball at a random time, hardly ever caring about backporting a fix from git, let alone from trac discussions and vagrant patches. Anyway... I really don't have any wise words on how it should work out from here. Let's hope we manage to come up with something great. Giant thanks to you guys who maintained this project for years, I'm sad to see you go, and wish you all the best! e. ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: mc is over!?
Bah. Mc is not over. Things change, that's all. I've been into mc since I don't know when. The first time I used it. Mid/late 90s I'm guessing. I saw how it floundered in the 4.6 series. I shrugged and kept tweaking and hacking my version. A few years went by and I looked it up again, purely out of curiosity. I was delighted that someone had given it a full work over into the 4.8 series. There were some persistent, puzzling, and very annoying bugs that are now gone. Excellent work, gentlemen. Thank you very much. My list of personal patches went from ~30 down to ~5, where they sit now, mostly minor interface tweaks. Mc works, and it works very well. If development stagnates for a while, so be it. There is actually very little to do. Mc is as close to perfect as software gets. There will always be bugs and minor tweaks, and that's what needs to be worked on, now and forever. Yes, mc in its current incarnation is a model from the 1990s. I like it that way. I'm not a big fan of C++. I also don't like eye candy in a tool that is all about functionality and utility, and I very much appreciate a file manager that can operate when XWindows cannot, or the system is barely bootable. It's the perfect size: big enough to be feature-rich and highly usable, yet small enough that a single individual can (theoretically) get his head around the entire code base. It's also fun to hack. I cannot guarantee 20hrs/week, but I would be very interested to work through bug reports and small enhancement requests at my own pace, and see what I can get done. As a last thought for this email: I suppose what we have here is a complete lack of consensus as to the direction to take if we were to move into a 5.0 series. My thinking is along the lines of complete modularity: a basic interface design (that already exists) and everything else is plugins. What if I want to use mc for inventory control? Make a plugin to work with SQL instead of filesystem. Perhaps there needs to be room for people to experiment with this sort of thing. A 4.9beta branch that starts off as mess and arguments but slowly gets sorted into something with vision. That's my 2 cents worth. Take care, and best wishes for those who are moving on to bigger and better things. Thank you for your labors. -- Peace and Cheer ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Article about Midnight Commander on OpenSource.com
Yes, I was looking for more than superficial feedback - so thank you. And perhaps the publicity will attract some developers. My personal opinion, generic as it is because I have been here only a couple weeks, is that someone who has been here for a while should step into the lead role. I am willing to assist by learning more about the code. Based on the recent posts to this list, it seems that someone who can create a defined process would be desirable. Just my 2 cents worth. On 05/28/2015 04:40 AM, Paul Sokolovsky wrote: Hello David, On Wed, 27 May 2015 08:14:00 -0400 David Both db...@millennium-technology.com wrote: I like Midnight Commander very much. And I have authored several articles for OpenSource.com. My latest, which has been in progress for several weeks - long before the current developers announced that they would be retiring from the project - is about Midnight Commander. Please check it out. That looks very nice, and thanks for these efforts - I'd say that's the area to which few other folks pay attention to, so it's really helpful to know that some people don't just think what will happen when current generation of mc user will die off, but actually try to make sure that new users get acquainted with it. If you want feedback beyond it's cool!, I'd say that you should use default mc theme for screenshots (to give least surprise to users who actually will try it out). Or perhaps have a screenshot with a default theme and your custom theme and then mention in the text that mc is configurable down to the level of theme and colors. http://opensource.com/business/15/5/midnight-commander -- * David P. Both, RHCE Millennium Technology Consulting LLC Raleigh, NC, USA 919-389-8678 db...@millennium-technology.com www.millennium-technology.com www.databook.bz - Home of the DataBook for Linux DataBook is a Registered Trademark of David Both * This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel