Slashdot Mirror
Evil, Almost Full Vim Implementation In Emacs, Reaches 1.0
New submitter karijes writes "Evil is a new Emacs major mode intended to implement full Vim emulation for Emacs editor, and it's reached its first stable release. Evil implements many Vim features and has support for plugins, so there is port for rails.vim, NERDCommenter and mapleader among others. You can find details about this release on the mailing list."
So finally Emacs gets a text editor! I must say, it's a nice operating system but it's been missing a text editor for quite a while... ;)
I'm sorry, I only accept criticism in the form of sed expressions.
they should call it "vagina"
Mainly the Linux emulator for emacs.
Didn't emacs already have this: viper mode? Or was that just straight vi? I for one liked viper mode so I am going to try this new mode out.
If you want to use vim, why wouldn't you just use vim?
Coming up next: Full implementation of Emacs in Vim
Actually it's already done, Emacs is available from Vim in Emacs
Slashdot, fix the reply notifications... You won't get away with it...
If vim and emacs merged into one application, would the resulting application donate Richard Stallman to Uganda?
I heard you like to edit text, so I put a text editor in your text editor so you can edit text while you edit text.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
I'm evil. And I've been evil for years...
vi vi vi, the editor of the beast.
Remain calm! All is well!
Entering Ex mode. Type "visual" to go to Normal mode. :w ::W :W :QW :wq
oh shit what's this
E749: empty buffer
E32: No file name
:
E749: empty buffer
:
E749: empty buffer
:
E749: empty buffer
:
E749: empty buffer
E492: Not an editor command:
E492: Not an editor command: QW
E32: No file name
fuck it, i forgot what I was going to comment anyway
The new EVIL editor was heard demanding "One MILLION bytes of core," to which GNU/Linux distributors reacted by doubling over with laughter.
After a hurried conference with its aides, the EVIL editor revised its demands to "One BILLION bytes of core".
I never liked that newfangled vim. It's far too... colorful. I usually swap it out for nvi, which is much more vi-like. Distributions (like Redhat) that install pico as the default editor make me punch someone. Maybe the guy who thought pico should be considered in any way an acceptable UNIX editor. I always have to swear, abort back to the command line, and export VISUAL=vi.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
It's still emacs.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
The only Linux terminal-mode text editor I can stand using is Midnight Commander.
I'm going back to only supporting closed source software.
Paying taxes to buy civilization is like paying a hooker to buy love.
...or is it more like mixing Star Wars and Star Trek?
That was the feature i was waiting for since 1994, and due to which i switched away from emacs 5 years ago.
I heard you liked an editor in your editor, so we put and editor in your editor so you can edit while you edit!
While funny for slashdot - it's basically like watching people arrange deckchairs on the Titanic. These are tools - tools to get your job done. Use the best tool and stop circle-j-ing about this over that/etc. I use both whenever it suits me; but don't do any serious development in either anymore. There's so, so, so much better tools out there than these tired old things.
By the way, not to belittle the project in any way, but you can already run vim inside of EMACS by the following:
M - x (return) term (choose shell) ; vim
You get the whole vim in an emacs term buffer. What you don't get is any real integration (you are stuck in vim, but your mouse can get you to another buffer if you need to). Evil is much better in that you are still in emacs while you use vim shortcuts and commands and you can get into emacs easier for slime and the rest.
You can even launch screen inside a term buffer - very handy for a quick ssh to a development machine (screen -R). You can even launch emacs on the other machine inside the term buffer for recursive madness.
EMACS is just awesome. And now thanks to Evil it also has an awesome editor.
nothing is like a good holy war, and thats pretty much why i've been following the vi/emacs threads for years without actually trying any of them for more than 2 seconds. the doctors said i stabbed myself with my bare hands in both cases. so what is the difference between these editors anyway ? except for having weird key combos?
Can I light a sig ?
Try this in Vim:
(ESC) : !emacs %e
Edit your file in emacs and then return to vim (just load file "L").
Your welcome.
Try this for your amusement:
Launch emacs.
Step 1: M-x term ; screen vim :!emacs
Step 2: in vim type
Step 3: return to step 1
You can stack as many sessions as you want. Why you would want to do that is of course completely your affair.
Running VMS 3.7 or 3.8, IIIRC. He really liked the vt200 keypad integration of EDT. Was a bit envious of the multiple buffers we had though, and then I wrote an elisp program to convert assembly language listing back to source so we could produce product-specific documentation for the regulators; that was too much. He switched to emacs+edt mode.
My favorite emacs story though is still the guy I worked with who used it as his login shell on BSD.
You are aware that Emacs has a GUI?
You are aware that vim also has a GUI?
Now, please tell me what nedit can do that neither Emacs nor vim can do.
Also, please tell me what you do if you remote login to another computer over a connection which is too slow to run a GUI and want to edit a file there.
The Tao of math: The numbers you can count are not the real numbers.
Every time you post 875, someone's going to have to post 1072.
It is an important stepping stone to have the "viie" (Vim Implemented in Emacs) editor. The next step is to implement Emacs using vim's built-in scripting language, thus giving us the "eiiv" editor. Then it should be a trivial final step to get the "eiiviie" (Emacs Implement In Vim Implemented In Emacs) editor. This tool will serve two important purposes:
1. It can be used to teach the concept of recursion (and mulual recursion) in Computing 101 courses at university.
2. It will give Linux an opportunity to play catch-up with Microsoft bloatware.
If it took you 2 months to figure that out you should have been fired.
is TECO mode! 0LT$$
For those of you old enough to remember the original vi, with a very limited set of commands and no support for the cursor keys:
Once we were trying to explain to an MS-DOS Wordstar user how the VI editor works. Here's what we come up with:
Vi is an editor with two distinguished modes:
In Edit mode you have all the capabilities of grandma's typewriter right under your finger tips! You can make the very same mistakes as you did with granny's typewriter and your possibilities to correct them are about the same.
That's why Vi was provided with a second mode, namely the Beep mode. On a vt100 terminal or compatible you can get into Beep mode by pressing an arrow or escape function key. In this powerful Beep mode even the more innocuous keystroke will promptly produce a Beep sound. As an example, arrows, return, blank spaces and most capital letters will produce beeps in the most arbitrary places of the screen. Just think about the whole world of possibilities that this mode gives to you:
--Compose a monotonic symphony or rap while editing your thesis!
--Send messages in Morse code to the secretary next door!
--Keep yourself awake with the clear sound of the Beep tone!
The variations are endless.
the emacs guys implement a emacs compatibility layer for supporting emacs mode on emacs? That way I can edit on emacs inside emacs on emacs on .. [aborted: out of stack neurons]
Everyone knows that Wordstar was the 'one true editor'.
In step 2 you are just suspending emacs, not running it actively. Trivial. You might as well just run emacs, ^Z, vim, ^Z, ...
Democracy is a sheep and two wolves deciding what to have for lunch. Freedom is a well armed sheep contesting the issue
Clearly, the thing lacking here is for both vim-in-emacs and emacs-in-vim to be so feature complete that you can nest them until you exhaust available memory. I propose that we codename the project to create this "straightline" , as it shall generate infinite jokes on /.
Returned Peace Corps IT Volunteer
Then pay someone to fix your problems. When I'm not at work, I'll write whatever code I want no matter how useless the rest of the world thinks it is; and it's certainly no more a waste than watching TV or getting drunk at tropical destination X.
Ah, now I understand. "Evil" is the NAME of the editor. I thought that the Vim implementation in Emacs was both evil, and almost full.
Geeze, I remember back in the... probably eighties... an VI emulator in Emacs. The Emacs squids (all two of them) were selling it hard as superior to native VI in every way. So I tried it... and it was pants. In order to use it effectively, you had to be skilled in both Emacs *and* VI, which kind-of negates the purpose. I didn't use VI because I thought it was superior, I used it because it was ubiquitous. Having to learn Emacs so that I can use a VI emulator is insanity.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Maybe if the Ctrl key was back on the left side of the keyboard next to the `A` (as God intended it to be) you wouldn't have that problem.
I knew Emacs key bindings before I actually ever used Emacs so my fingers have adapted. My first PC (Columbia XT-clone) shipped with the Perfect programs (PerfectWriter, PerfectCalc, etc.) and they all used Emacs key bindings. A few years later when I worked with a Tektronics 8086-based workstation that had Emacs, I was all set and have never looked back.
My beef with `vi' is that there are so many implementations of it. On some flavors of UNIX, `vi' allows the cursor keys to be used for moving around in the text while you are in input mode while on others you need to drop out of input mode to move to another line. (I can't count how many times I've farked up a file because of that difference and had to bail out with `q!' to ensure I didn't leave any bizarre characters in the file.) At least `ed' is consistent across different vendors' UNIXes and if I find that Emacs is not available, I can always depend on good 'ol `ed', stone axe that it is, especially in single user mode when `vi' might not be available. Back in my DOS days, the `ed' ripoff 'edlin' was a must on any emergency tools floppy -- it didn't require much space on your 360KB diskette -- so when I migrated over to UNIX, I was at right at home.
CUR ALLOC 20195.....5804M
Maybe if the Ctrl key was back on the left side of the keyboard next to the `A` (as God intended it to be) you wouldn't have that problem.
Ah the old PC vs. Sun keyboard challenge. I still have to deal with both every day.
The other nice thing about leaving the standard Emacs key bindings in place is they are generally the default bindings for the Emacs modes in other applications, like Tcsh, Bash, Ksh, readline(), etc...
It must have been something you assimilated. . . .
Since vim isn't extensible, having a phone is unlikely. In emacs I would almost believe it to be possible.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I'm curious: what emacs feature does not have a vim equiv (either built-in, or via a plugin)?
Basically the fact that you can alter any aspect of how the editor (or modes) work while in the editor.
Every Emacs command is like a vim plugin that you can modify on the fly.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I don't think I've ever seen a unix, linux or BSD system that didn't have some kind of vi on it. I've seen very many that don't have emacs.
In the past, yes. For about the last decade? No. Every UNIX made for a long time now includes emacs unless the sysadmin chose to remove it.
The last system I had to add emacs to was around 20 years ago, HPUX/MPE. That and two VAX systems. But luckily it was not too hard to compile emacs for either.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
For scripting text editing, I have a full range of options. For simple tasks, I use bash + sed, for more complex tasks I use Perl, when I need to perform some very complex editing in a million lines of code, bison is the choice.
Even looking back on the 1980's and many different flavours of Unix and now Linux the basic "vi" commands have not changed. If you absolutely needed your keyboard cursor keys to move your screen cursor you still needed to have a decent termcap entry for your particular terminal type, however if you use "h" (left), "j" (down), "k (up)", "l" (right) it always works no matter what terminal you use. Of course knowing other keyboard presses for cursor movement such a "w" (word forward), "b" (word back) as well as "i" (insert) and "a" (append) have not changed since vi was first written. The basic keyboard commands in vi are surprisingly logical if you think about them that is why I never bothered mapping keystrokes to function keys. You can even use vi on a teletype connected to your computer in single line mode.
/usr file-system.
In the DOS days I actually used "little vi" and that fitted on a 360kB floppy disk so I had no real need to run "ed" or "edlin" although I was still proficient in "ed" since when Unix was brought down to single user mode to fix any issues you may not have access to "vi" if you could not mount the
There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
...in a great fireball of self-wrought annihilation brought on by the inherent and overwhelming contradictions of running vim inside Emacs?
-- haaz.
I heard you like to edit, so I put vim in your emacs so you can edit while you edit...
It is on this keyboard I'm using on my Mac Pro (through an ADBUSB adapter).. and you can remap caps lock -> control on other computer/keyboard combinations.