The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ralph@inputplus.co.uk (Ralph Corderoy)
Subject: [TUHS] OK, no more 80 cols please
Date: Sun, 12 Nov 2017 17:35:25 +0000	[thread overview]
Message-ID: <20171112173525.CEAE21F952@orac.inputplus.co.uk> (raw)
In-Reply-To: <79A1DACC-1E35-4967-8439-52F19023E7B7@bitblocks.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

Hi,

Bakul wrote:
> (I don’t use vim much to know if it can split windows vertically).

Yes, horizontally or vertically.  Start vim, type `^Ws^Wv' where ^ is
Ctrl, and you'll have three windows.

> I didn’t “move” to vim as it did arbitrary undo/redo incompatibly with
> nvi.

That's still the case.  And it branches the undo history now, e.g. you
undo a few times, then make a new edit, and you old undone edits are
still available, but on another branch; the original one.  Occasionally
useful when you accidentally make an edit that would otherwise wipe the
redo.

Larry wrote:
> > Huh, that's news to me.

    What actually happened was that I was in the process of adding
    multiwindows to vi when we installed our VAX, which would have been
    in December of '78.  We didn't have any backups and the tape drive
    broke.  I continued to work even without being able to do backups.
    And then the source code got scrunched and I didn't have a complete
    listing.  I had almost rewritten all of the display code for
    windows, and that was when I gave up.  After that, I went back to
    the previous version and just documented the code, finished the
    manual and closed it off.  If that scrunch had not happened, vi
    would have multiple windows, and I might have put in some
    programmability—but I don't know
        — https://en.wikipedia.org/wiki/Vi#Distribution

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


  reply	other threads:[~2017-11-12 17:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 21:23 Warren Toomey
2017-11-11 21:27 ` Larry McVoy
2017-11-12  2:51 ` George Michaelson
2017-11-12  3:00   ` Dave Horsfall
2017-11-12  3:02     ` George Michaelson
2017-11-12  3:21   ` Steve Nickolas
2017-11-12  4:00     ` Dave Horsfall
2017-11-12  4:04       ` George Michaelson
2017-11-12  9:18       ` Andy Kosela
2017-11-12 10:58       ` Ralph Corderoy
2017-11-12 14:43         ` Bakul Shah
2017-11-12 15:01           ` Ralph Corderoy
2017-11-12 15:10             ` Larry McVoy
2017-11-12 15:24               ` Bakul Shah
2017-11-12 17:35                 ` Ralph Corderoy [this message]
2017-11-12 21:36                   ` Dave Horsfall
2017-11-12  0:08 Norman Wilson
2017-11-12  0:21 ` Henry Bent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171112173525.CEAE21F952@orac.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).