Re: posting with PICO

User Market wrote:
> But there is a need to POST an article from time to time. Which is not
> essential but would be a nice options for them to know what I wrote, So,
> PICO opens up when I press P to post which is strange because the
> .slrnrc file states VI as a command_editor.

Perhaps slrn can't find "VI". Maybe the command name is case-sensitive and 
is "vi" instead, or perhaps you'd be better off pointing to vi's full path 
(something like "/usr/bin/vi" on Unix-like systems). Or maybe you could set 
"editor_command" instead of "command_editor". I suggest that you quit slrn, 
change the "editor_command" to an editor you prefer (vi) and relaunching 
slrn. See http://slrn.sourceforge.net/docs/FIRST_STEPS.html for more on 
"editor_command".

> But that's ok I guess. And then when I am dome typing the post I press
> ^X to exit or I save ^O first, but that dont make any difference. And
> then SLRN Confirms the post choice and then it writes 441 error stating
> SLRN cannot post because the body of article being posted is empty which
> is weird , because it was not.

Part of this could be user error with Pico; I'm not a Pico user so I can't 
say what those control keystrokes are supposed to do. But it's possible 
you've told Pico to exit without saving changes, thus leaving your post 
file unmodified from what slrn gave Pico (no body text) which slrn then 
refuses to try to upload to your NNTP server.

I suggest looking at Pico documentation to see how to get that editor to 
save changes to the file and then exit.

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford