> > > joe is everything but user-friendly. That's the Ctrl-K D one. How can I > > > guess I need this to save a file? mcedit is indeed much better, but mc > > > is not installed by default, or is it?
This isn't for you Fabrice, I'm just gonna vent a bit here :) Joe is every bit as user friendly as Qedit was. Not to date myself too much, I remember using Qedit for all of my DOS editing needs. There is nothing wrong with having to use Wordstar "like" commands. If you've changed the file in memory joe will prompt you to save the file before quitting. At least joe gives you a title bar with "Ctrl-K H for help" on it which is far better than the vi option. What's more is joe's help screen can be left in place while you work saving having to Ctrl-k H continually. mc edit is great, if it's there (I prefer cooledit, but it's gui only), failing that joe is about as user friendly as you're gonna get for a stand alone app for the CLI. How user friendly does one need a simple editor to be? And no, I don't believe mc is or should be installed by default. The trouble as I see it, is that Uncle Bill and company have convinced the pc users of the world that it is ok to be ignorant of a CLI. As it is, when you run into a big problem (registry corruption for instance), Microsoft's standard answer is "Re-install, and if still doesn't work, call us back" What's worse, is all of those who insist that any given *nix distro (be it Solaris, Linux, OpenBsd) be just like Windoze. Why? Gosh dang, I could write a book here! WinDoze is WinDoze. Linux isn't and never will be (I hope). God help me when I have to tolerate an OS that tells me what to do. On Mon, 2002-01-21 at 06:46, Fabrice FACORAT wrote: > 1�/ when fail to launch miserably and you have to edit config files by > hand At least you have the luxury of being able to do it. Call and try asking Microsoft how to manually edit a registry file! I can hear the laughter already. > 3�/ when there is a pb and have to edit some files by hand without > having X So goes life in the world of *nix and it's variants. I doubt that'll ever change, at least no time soon. At least you can run lynx to go find help. Try that from an out-of-the-box DOS (WinDoze without the gui is still DOS) CLI !!! > 4�/ if there was a very easy console text editor installed by default, > when I will tell someone to modify a file, I will just tell it : > "my_simple_editor file_to_modify". Why ? because it's faster than > browsing to find the file and because we should encourage user to know a > minimum the CLI And what CLI editor do you know of that will simply go find some flat text file that is buried 6 some directories deep for DOS, Win-anything, *nix or anything else? From a commandline? I'd like to see it. whereis or find will track a file down for me quickly enough, but I have to decide which file is the one I want. Therefore, "my_simple_editor file_to_modify" becomes "whereis file_to_edit" make a choice and then, joe file_to_edit. How much easier does it need to be? The bottom line is, for someone coming out of the WinDoze environment, nothing CLI based is going to be _easy_ to use. Ladies and Gentlemen, welcome to the wonderful world of learning something new. Shara
