On 4/4/2017 3:36 PM, Charlie Gibbs wrote:
> On 2017-04-04, rickman  wrote:
>
>> On 4/4/2017 6:27 AM, Kerr Mudd-John wrote:
>>
>>> I'm thinking of getting it vaguely back on topic-ish as Yet Another vi v
>>> emacs debate!
>>
>> Which side are you on.  My old editor, Codewright has had a stroke and I
>> am finally learning a new one so I can use the same editor on the rPi
>> and the PC.  Right now I am struggling to learn Emacs as I have heard so
>> much good about it.  But it doesn't do much through the GUI.  :(
>
> I took a look at emacs a while ago.  However it was just a bit too
> foreign to wrap my head around.  I think tab handling was the straw
> that broke the camel's back.

What does it do with tabs?  Codewright could be pretty weird.  The
choices were to replace tabs with spaces (which means deleting them is a
PITA) or using tabs (which means putting them in lots of times when you
are trying not to).  Didn't seem to have a middle ground of inserting
tabs when you hit the tab key one.  But maybe I missed an option or two.


>> Does VI even run on the PC?  How well does it deal with the Unix NL vs.
>> PC CR/LF issue?  Codewright would just preserve what it saw used in the
>> file being edited.  That was *great*.
>
> Dunno about a Windoze version of vi, but I'm sure something exists.
> However, if I call up a file that has CRLF line endings in vi on my Linux
> box, each line has a blue "^M" at the end; the CRLF endings are preserved.

What did it do on your Linux box when you opened a DOS file and typed
some extra lines?  Did the new lines have the CR inserted too?

--

Rick C

--- SoupGate-Win32 v1.05