-={ mardi, 01 mars 2016, 21:37:53 +0000 }=-

Hey Nicholas!

 NB> It basically quotes like most email clients with only >'s.

Understood.  Quite a bit of BBS software behaves that way.

 NB> Is the part where the header information of FROM/TO is gathered
 NB> and the message is reflowed with quotes (and initials) separate
 NB> from everything else

Yes.  Same with my so-called stored msg format.  I keep the null terminators
for field seperators including the body of the message which is where the text
to be quoted is obtained from.  The header is currently the FTN msg datetime
stamp, To, From and subject.  I think extending it to include Area and getting
rid of it in the msg body would be a good idea.

 NB> (and if not, could it be done easily?)

I am not sure about 'easily' but most of the hard work is done.  It is just a
matter of getting it to work with whatever format you are dealing with so that
when nano returns control back it looks like it needs to look for the BBS's
fornat etc.  That is what will need to be worked out at the moment but the last
time I did something like this I just used 'hpt post' to handle the dirty work.
 It worked fine and didn't corrupt any utf8 characters like most (all?) FTN
editors do.

 NB> I wouldn't mind testing a bash script before nano loads to do just that.

Same here.  I'll have to modify the current WeBeBashing to work with squish
bases, msged and nano and we can take it from there.  At the moment WeBeBashing
is an entire offline-type thingy that only cares about handling things for vim.
 No squish or jam or whatever.

I'll let you know once I have a so-called BBS setup here that more or less
mimicks a standard BBS for testing purposes.  Offhand I think using the husky
stuff will get this idea off the ground.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.42(1)-release (x86_64-unknown-linux-gnu)