Old vi

Old vi - Old school stuff

Users browsing this thread: 1 Guest(s)

	jkl Offline \| 15-05-2024, 07:08 PM \| #1

I investigated when the flash option was added to vi. It was when System V entered the VAX. 1983.
Result: a new Vim patch…

https://github.com/vim/vim/pull/14778

--
<mort> choosing a terrible license just to be spiteful towards others is possibly the most tux0r thing I've ever seen

	r1w1s1 Offline \| 13-06-2024, 04:32 PM \| #2

I tried some many editors but still come back to vi/vim and today I use only vim for my work.

	jkl Offline \| 16-06-2024, 05:04 PM \| #3

That's unfortunate.

	Odinn Offline \| 20-06-2024, 01:05 PM \| #4

Vim is outstanding!

(13-06-2024, 04:32 PM)r1w1s1 Wrote: I tried some many editors but still come back to vi/vim and today I use only vim for my work.

	ckester Offline \| 20-06-2024, 10:00 PM \| #5

I've been meaning to try vis for a few years now, because it supports Rob Pike's structured regular expressions, but haven't gotten around to it yet due to inertia. So I'm still using vim too.

I've also thought about neovim but am unsure whether the vimoutliner plugin will work with it. Does anyone know? It's old and probably obsolete but it's been a part of my workflow for almost as many years as I've been using vim.

	jkl Offline \| 20-06-2024, 10:04 PM \| #6

Wouldn't it make more sense to try sam instead?

	ckester Offline \| 20-06-2024, 11:04 PM \| #7

I tried sam a few years ago but only with the graphical UI -- which I didn't like. The command language, on the other hand, is lovely.

	jkl Offline \| 21-06-2024, 09:38 PM \| #8

Try sam without the GUI. It's basically ed on steroids - WITH Rob Pike's regex implementation. Granted, unlike vi(s/m), you'll need to print (with or without line numbers) your stuff more often than not, but you'll love it.

sam's GUI is a matter of taste. I understand why it does what it does, to say the least.

--
<mort> choosing a terrible license just to be spiteful towards others is possibly the most tux0r thing I've ever seen

	VMS Offline \| 06-01-2025, 06:31 AM \| #9

I like to use plain vi for file editing and scripting; few years ago I covered my setup in Set up vi(1) for modern usage

	user_66437937 Offline \| 16-01-2025, 08:35 PM \| #10

@vms very nice job, inspired me to spend this evning tinkering around .inputrc and add a couple shortcuts to help when using rlwrap ed.
\C - CTRL
\e - META

Code:
$if ed

"\C-w": "wq\n"

"\er": "\C-L"

"\eg": "1\n"

"\eu": unix-line-discard

"\ev": "!expand -t 4 % > %\n"

"\et": "r !date +\\%Y-\\%m-\\%d\n"

$endif

	freem Offline \| 31-01-2025, 03:33 PM \| #11

The one thing I want to complain about when talking about vi and vim is this one: commands are affected by caps lock state, and this is a serious pain to me, since I use that key for it's purpose: generate text in MAJUSCULE, notably that good old C/C++ idiom that reserves those for macros, or for shell variable.
Semantics is important, but then, using caps lock also modifies the behavior of commands!

I would like, and have been tempted to write, a vi-clone that would act like a game: caps-lock understood for text input, but ignored for commands.

View a Printable Version