I see you're using vim. Let me fix that for you.

'fuv' is a programmer's editor that is an excellent replacement for vim.

If you've been using vim for a while, you're probably frustrated with its lack of hardcore power.

In vim it's far too easy to wimp out and use 'insert mode' to type text directly into a document.

fuv fixes that.

In fuv, there is no direct entry of text.

There is just a regular expression search/replace function.

*All* editing is done by searching and replacing over the existing text, using regular expressions.

And every search term *must* contain at least one non-escaped regular expression special character.

If, for example, you tried to replace "a" with "b" -- fuv wouldn't run it. It would emit the 'why bother?' error message and discard your document.

Instead you'd want to try replacing "[a]" with "b", only then will fuv consider your input worthy of applying.

If no matches are found for any given search/replace then fuv revises its opinion of you and discards your document. It may, on a whim, locate another document on your machine and discard that too.

fuv's native format for storing a document, a .fuv file, is not the resulting text but rather the series of replacements required to recreate that document from scratch. This is particularly helpful for avoiding merge conflicts from source control systems, mostly because it ensures that no one else will contribute.

Oh, and it's worth mentioning that fuv does not let you see the document itself. Upon launching fuv, all of your monitors go blank. Thereafter you must issue at least one command every minute or fuv assumes you have died and summarily discards all your work, overwriting every byte on disk at least 8 times to avoid recoverable data remanence. And it's certainly best to keep fuv busy, as it only uses *spare* cycles for searching your hard drives in order to locate configuration files from competing editors that it can delete, reverse, or otherwise insidiously corrupt. fuv is playful. i guess.

To exit fuv you need to enter the termination command ::q&*$&(#&. Be careful to get it right. And please, whatever you do, don't try to "paste" in the termination command, or any other command. fuv treats all use of the clipboard as a dire insult. I've promised not to reveal what happens, lest it should happen again to myself or the people I love (fuv is reading this as i type). Let me put it this way. Have you seen any of the "saw" films? fuv makes "saw" look like the dux of charm school.

Once you tire of fuv, it's time to consider emacs. Be careful though; emacs is no picnic. After you've been coddled by the niceties of fuv, emacs can seem outright cruel.

I've implemented the core features of fuv and put the source on codeplex. Download the source, compile it, or, if you're feeling particularly foolish, get the binary here.

Get "fuv.exe" Now (not a sane choice)

Visit fuv on codeplex (wiser)

Sorry, TECO got there 40 years before you! http://en.wikipedia.org/wiki/Text_Editor_and_Corrector

When I log into my Xenix system with my 110 baud teletype, both vi *and* Emacs are just too damn slow. They print useless messages like, 'C-h for help' and '"foo" File is read only'. So I use the editor
that doesn't waste my VALUABLE time.

Ed, man! !man ed

http://www.gnu.org/fun/jokes/ed.msg

Bug: A simple replacement (a/b) invokes the "Why bother?" message.

Here's a pull request:

:oc:\projects\fuv\fuv\Form1.cs
IndexOfAny.../IndexOfAny("[/

@Michael L Perry -- closed as 'it's not a bug it's a feature'.
But *love* the pull request technique.

@oxFAN -- sed doesn't really even apply in this situation as it's not a real "editor".

For the love of god, do not run fuv then attempt to use the scroll wheel. I tried, and now I'll never father children again.

I had a spare can of bathworms on my workbench until this morning. This morning I dropped my bathworms can on the floor and they spilled everywhere. That wasn't the end of it, the damned dog smelled them and dived under the table and started to eat them. I only managed to rescue four bathworms and that is how I got here.

Anway, the communications towers are watching, waiting for the erroneous message to flow through the node. They be waiting a long time for that hey-ha!

Made me lol multiple times.

I hope someone takes you up on the 1 year fuv challenge.

@MacAddict I guess so, but since on macs keyboards are optional and the mouse is mandatory, it only works by sending the commands as morse code with the mouse button (it works better with the old 1-button mouse of the 1984 original mac).

Is there any good reason why the source code has not been made available in .fuv format?

@jaysea How could you say that about sed? sed is DEFINITELY an editor.

sed -i 's/abc/def/' file

is equivalent to:

ed file
1,$ s/abc/def/
w
q

I sat next to the man and his editor - http://en.wikipedia.org/wiki/The_Hessling_Editor

Found this page searching, as I do every few years, to see if anyone is seriously working on a replacement for vim ... made me lol

You’re a very persuasive writer. I can observe this in your article. You’ve got a method of creating compelling information and facts which sparks very much interest.

I see you're using vim. Let me fix that for you.

NimbleText is a Powerful FREE Tool

Articles

Twitter, baby

Recommended Reading

Recommended blogs

Aggregated Links

Human Link Machines