Re: Re: [nbdev] Too many editor tabs?

> 
> I don't have an original vi to try here, since on this OS vi maps to  
> vim, but is it true that the original vi only supports a single open  
> file?

Yes.
To edit multiple files you either started multiple vi's or switched
between editing files (not between editing buffers).

> If not, it must support having edited files in memory. These  
> are not identical to the disk version. That's what I'm calling a  
> buffer, and it seems like a useful concept.
> 

How is it useful?
If you have a bunch of unedited, semi-edited, maybe edited buffers
in memory doesn't put that a higher load on your mind?

Consider that in newer IDE's the concept of saving a file is very blurred.
Compilers work on the buffers, files may get saved automatially you
have editing history that doesn't really require you remembering whether
you saved your file or not.


Inasmuch as Tabs have 1-1 mappings with buffers I again don't understand
their use. They seem to be an odd vestige of the following:
MDI was invented to allow multiple documents to be edited. This started out
as multiple open windows in a larger frame. You could iconize and
deiconize them. This goes back to I think windows 3.X. Eventually
for some reason they proved impractical and they got replaced with tabs.
Now you have a single editor view which switches between buffers ...
replace buffers with files and you lose nothing.

That's why I was advocating getting rid of tabs.