One time I used Power BI/Power query language to generate an Ed script that contained all versions of all XML documents in a database and turn them into a Git repo.
I still like writing scripts that generate Git repos but I don't use Ed much.
vi was originally the visual-by-default run mode of ed. And EDLIN on MS-DOS (and maybe CP/M too? don't remember) was based on ed too. That's why EDLIN and vi have similar command sets.
One time I used Power BI/Power query language to generate an Ed script that contained all versions of all XML documents in a database and turn them into a Git repo.
I still like writing scripts that generate Git repos but I don't use Ed much.
vi was originally the visual-by-default run mode of ed. And EDLIN on MS-DOS (and maybe CP/M too? don't remember) was based on ed too. That's why EDLIN and vi have similar command sets.
If I remember correctly, vi was the visual mode of ex. I am trying to find some references for this. Here's one I could find from <https://pubs.opengroup.org/onlinepubs/9699919799/utilities/v...>:
> While ex and vi have historically been implemented as a single utility, this is not required by POSIX.1-2017.
Better references would be very welcome. By the way, we can see this even today. For example, first type the following command in your terminal:
Then at the ex prompt (the colon prompt), type this: This should bring up full blown Vim. The reverse is possible too. For example, in Vim, type: This takes us to Ex mode. Then in Ex mode type: This brings back Vim again.TIL about Rosetta code[0].
And I can't help but wonder what the license of the code in the site is.
If it isn't BSD0 or some similar attempt at preemptive public domain, what is even the point of such a thing.
0. https://rosettacode.org/wiki/Rosetta_Code
Rosetta Code is a great resource and uses the GNU Free Documentation License 1.2.
I see this much, but that's not a code license; it is a documentation one.