Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Basically, I really like vi[m]'s key-bindings, but not the rest of the editor. I really dislike emacs key-bindings, but like the rest of the editor.
viper-mode seems like the best of both worlds, but it's not perfect..
What vim features did you miss in emacs (and more importantly, how did you get them back)? What config-tweaks did you do to make viper-mode nicer to use?
As a start: I really missed vim's visual-selection mode.. vimpulse adds this to emacs!
As far as I know, VIM/VI has always had the :set nu feature to show line numbers along-side the lines themselves. By default, emacs only had line-number-mode which showed the line-number of the current line in the mode-line (not the same thing).
To fix that, I always found linum.el pretty useful. Starting with the upcoming emacs 23, the linum mode would be included in the standard distribution. But for emacs <= 22, one still needs to install it manually.
I also miss the incremental search with / and ? . Something like
what is posted here first in the TODO section.
http://common-lisp.net/project/vial/darcs/extended-viper/vimlike.el
If anyone can provide it, it would be great. Jurta ?
I would recommend you use my version of the emacs starter kit. It is totally customized for heavy (symbiotic) use of emacs and vi/vim (via viper and vimpulse) together.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I like the eye-candy, but spacemacs does come with a greater speed penalty. What makes spacemacs worth keeping?
Evil-mode is just a single Emacs
package providing a minor mode to emulate vi-like features. There are
thousands of "packages" that can be installed in various ways at
any time.
Spacemacs is a full-blown,
opinionated, kitchen-sink starter kit distribution. It features Evil-mode front-and-center, but also provides and configures many other ambitious packages like Helm, and themes, and its own
necessary documentation (which seemed pretty good). Installation of
starter kits is more involved than packages and is the starting point
if you choose to use one.
You have to decide if you want to adopt the whole Spacemacs
experience/philosophy, or rather just bring over your vi habits via
Evil for some familiar bindings in a traditional Emacs. Doing the
latter gives more flexibility -- you can individually add other
packages that Spacemacs leverages.
After 15 years of Vim, I successfully switched to Emacs and opted to
let Emacs just be Emacs and learn its natural bindings (still
learning, of course!). I found this makes Emacs books, documentation,
and people easier to make sense of, and now I don't miss the modal
editing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am new to Vim and after using it for about 3 days i am in love with it. I used sublime-text before this and i decided to try vim because i heard a lot of people (maybe some) hate and love it. I know that learning Vim require time investment + patience but for the basic shortcut and command I am okay preety smooth but when i reach the .vimrc configuration I start to feel frustrated and 'uhhh'. Overall I like the way how the work-flow goes and in the past 3 days i manage to implement the basic shortcut.
I watched and read a lot of tutorial, and most of it asked us to find "someones .vimrc configuration and use it". I searched at Google 'vim .vimrc', I found 2 links from Github and I am amazed with all the massive lines and I was like 'What! How am i going to understand what each of this line for!' :/ i tried to search all the 'set' and the basic config but i am not happy without knowing what each of the line does. Please if anyone here can help me or explain how the configuration works. I tried the :help and there were about 8000 lines .>< for now i am using the https://github.com/tpope/vim-sensible Vim-Sensible and i am hoping to know how it work. Thanks guys.
For plugin, I think it's fine for now.
What you see in people's posted ~/.vimrc files either is:
the result of years of using and tweaking Vim; don't be intimitated, just start out small and it will grow automatically with your continues use (hopefully in a benign way). The mentioned vim-sensible plugin is a good way to start.
just copied from colleagues / somewhere on the net without real understanding; this is dangerous and best avoided. Vim "distributions" like spf-13 and Janus lure you with a quick install and out-of-the-box settings, but you pay the price with increased complexity (you need to understand both Vim's runtime loading scheme and the arbitrary conventions of the distribution) and inflexibility (the distribution may make some things easier, but other things very difficult). Vim is incredibly customizable, using someone else's customization makes no sense. Doubly so for canned, ready-made "distributions".
Yes, the built-in :help is large, but you don't need to read it in one go :-) It is excellent, too, and contains most of what you need - for years to come!
This article by Vim's creator explains the philosophy behind Vim very well (there's also a recorded talk): start small, using only basic commands (also taught by vimtutor), and gradually become a master of all kinds of text editing tasks!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I understand and can write commands in Vim. But i would like to know what happens in the background in Vim. Like whats files are called and how plugins come into play?
Your question isn't very specific and clear. Basically, any configuration is put into a ~/.vimrc file, like with many other (Unix-based) programs (the native Windows way is more complex). Plugins go into a directory structure in ~/.vim/. It's basically just putting the files there, and restarting Vim. Many also use plugin managers like Pathogen, Vundle, etc.
You'll find all the details under :help startup. Learn how to look up commands and navigate the built-in :help; it is comprehensive and offers many tips. You won't learn Vim as fast as other editors, but if you commit to continuous learning, it'll prove a very powerful and efficient editor.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I just installed GVIM, went through the menus, and changed a bunch of settings.
I closed GVIM, and the settings were all lost. :(
I made my changes again.
Now how do I keep my settings?
You can use :set command to list all settings and put it to ${HOME}/.vimrc.
:se[t] Show all options that differ from their default value.
I wonder why nobody mentioned to use a vim session to save global settings and the views for all windows. Of course mastering .vimrc should be on the agenda of any serious vim user, but sessions can help further. Especially since they are similar to 'profiles' which are familiar to many people.
There also exist a plugin for gvim that facilitates the dealing with sessions further (sessions.vim : Easy session management for gvim.
You should really learn how to use .vimrc. Like VIM itself, learning to do this the hard way means more power and ease of use later.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Are there any Vi clones that are still in wide use today (besides Viper mode in Emacs ;)), other than Vim? If so, what are the pros/cons to using it instead of Vim?
Kate (KDE Advanced Text Editor?) has a Vi editing mode.
It's not strictly a clone, but real live no-kidding vi is available open-source now. Also lots of sources and links to many versions on the vi-lovers page.
From the Vi Lovers Home Page - http://thomer.com/vi/vi.html#versions
I don't know what your requirements or expectations are, but Wikipedia has a great comparison page here that should help you figure out which version is best for you.
ActiveState Komodo has a vi mode too.
I use Vim for all my editing except when I use Visual Studio. Fortunately there's the ViEmu plug-in for Visual Studio. Unfortunately it is not free nor a complete Vim implementation, but it's not expensive either and it close enough for my needs.
Visual Slickedit ($$$) has a very nice VI emulation mode. Vslick has other features that make it quite nice as a programmers' editor (e.g., dynamic tag generation instead of having to re-run ctags).
QT Creator has 'fake vim' mode.
VILE
Sublime text has a 'Vintage' mode which replicates many vi/m commands.
I used the vi-plugin in Eclipse a while and it is quite good. But since my colleagues don't have a clue about vi they ran in to problems when they were trying to edit on my workstation.
I used to use elvis to satisfy my enhanced-vi needs, but can't really offer a comparison (other than that both are very good) because I switched to vim a couple years back for the sake of using something that was easier to find support for (if only because it's what everyone else uses).
I often use nvi when I want a stripped down version of vi.
Not any real pros of using it instead of vim. More lightweight and doesn't load all the plugins I have with vim.
Vim still has lot more features (tabs, plugins, better multi-buffer support...).
Yzis
The main website http://www.yzis.org/ is no longer functional. However, the source code can still be found on GitHub: https://github.com/chrizel/Yzis