Sorry for the copy direct to you Alan. I'm fixing my reply options for this folder now <sigh>.
On Wed, 29 Nov 2006 09:01:29 -0500 Alan Isaac <[EMAIL PROTECTED]> wrote: > On Tue, 28 Nov 2006, "Gerald V. Livingston II" wrote: > > Eww. Not a vi* fan. I'll dig around and see if I can get > > something else working. > > If you do not like modal editing, you can use Cream > (essentially Vim with the modes hidden). > > But as a more general observation, I always suspect anyone > who dislikes modal editing refused to spend any time with > it. (Forgive any presumption here.) The Vim tutorial takes > only 20 minutes to get you up and running. Your technical > skill level is clearly higher than mine, so if I can love it ... > > To get OT, Vim works great with Mahogany. > > Cheers, > Alan Isaac My first computer text file editing was done with 'edlin' in DOS. That was fun, having to replace whole lines to fix a misspelling. From there I went to WordStar on CP/M. That's what I'm most comfortable with. When I started using slackware Linux in the mid 90's I learned vi because at the time it was easier than compiling and installing several other editors to find one I MIGHT like. I used it for over a year. I can be proficient in it if it's the only editor available on a machine I have to maintain. But, having to switch back and forth between stock Windows and various Linux machines I prefer to do all of my text editing in either point-and-click or WordStar keystroke editors WITHOUT having to install and customize before use. For Windows machines I carry around an installable copy of something called "Crimson Editor" which lets me save in DOS or Linux CR/LF format. For Linux, most every distro has pico, nano, ae, or joe available out of the box. Now, the actual problem is finding ANY editor that can be customized to handle email word-wrapping correctly. To look for the "> " pair as the first two characters of a line and if that line exceeds the wrap-length add a NEW "> " pair at the beginning of the next line, move the extra characters down past that addition, Look for "> " on the next line and if it is there then delete it and move the remainder of the line up to the end of the current line then start over counting from the beginning of the current line. And THAT, of course, is just the logic for dealing with a single nested level of quoting. It actually needs to look for ">>> " and "XXX> " and "> > > " and ... I'm digging into the joe documentation now to see how much I can customize the word-wrap functions. It has special modes for many program file extensions already so I may be able to talk it into doing proper email wrapping if I can tell it to ignore ">" unless it is at the beginning of a line. Most MUA's have an "internal" editor that works, maybe one of the others has one that I can rip out of the package. The internal editing in M 0.66 worked fine. 0.67 no longer wraps properly. Thanks, Gerald ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mahogany-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mahogany-users
