I believe that the built-in "pine composer" is actually not pico at all. It is truly built-in and tightly integrated, so that you can cursor up into the header area from the message body, and ctrl-x is all you need to do to send the file. You can also do ctrl-o to postpone the composition while in the message body, and you cannot do any of those things in pico. Pico is an editor patterned after the pine composer, and that is very different from saying that pine uses pico by default. It does not! So in fact if you specified pico as your pine editor, you would get behavior very like nano. You could not cursor up from the message body into the header area, you could not postpone the message while in the message body, and you would have to explicitly exit pico with ctrl-x and then separately send the message with another ctrl-x. So what you now have with nano is as good as it gets! <smile> Chuck On Thu, 4 Apr 2002, Dan Murphy wrote: > Hi Chuck and Janina. Here's how I have it configured. > I have the alternate editor implicitly option enabled. I have nano > chosen as the editor of choice with the "-t" along with other things > specified on the command line, and now it seems to be doing what I was > hoping for. > thanks again, Chuck. > it seems you can not totally replace the default editor in pine but must > use one of the alternate editor options in order for pine to bring up > your chosen editor. > > > Dan Murphy > mailto:mweeby at earthlink.net > Let us not look back in anger or forward > in fear, but around us in awareness. > -- James Thurber > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > Visit me at http://www.valstar.net/~hallenbeck The Moon is Waning Crescent (47% of Full)
