-={ Sunday, 06 March 2016, 15:11:42 -0500 }=-

Hey Nicholas!

 NB> Is that while using the -$ (softwrap) switch?

No but I just sent another one with the -$ switch and it behaves exactly the
same as you should soon see and confirm.

 NB> While we're on the subject. I'm currently replying to this with
 NB> vim. Seems as though it works fine depending on what telnet
 NB> terminal program I'm using to access the BBS.

Right.  Most, if indeed not all, BBS's are extremely handicapped when it comes
to dealing with a proper terminal program.  I recall old fashioned dumb
terminals having extreme issues properly displaying certain DOS based BBS
packages output way back when.  Same with httpd when it first reared it's ugly
head.

 NB> I'll have to take that up with developers at a later time.

Best of luck with that.  They don't have a decent terminal program as a rule so
it tends to be a waste of time from my experience dealing with so-called
developers.

Kids these days eh?  :::tsk, tsk:::

 NB> it isn't wrapping the whole word to the next line, but rather
 NB> doing the same thing nano does

Try putting 'set lbr' in your personal or global vimrc.  I have it in the
global /etc/vimrc since way back when.  Works like a charm.

For the record here is a copy of my /etc/vimrc as inserted by :read
/etc/vimrc

" Begin /etc/vimrc

set nocompatible
set backspace=2
set viminfo=""
syntax on
filetype plugin indent on
set background=dark
set lbr
highlight statusLine cterm=bold ctermfg=white ctermbg=blue
set statusline=%<%f%h%m%r%=%b\ U+%04B\ \ %l,%v\ %P
set laststatus=2
set softtabstop=2
set shiftwidth=2
set encoding=utf-8
set fileencoding=utf-8

" End /etc/vimrc

Note the statusline which will display unicodes near the right side of the
statusline.

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)