On Sep 10, 11:39 pm, Kevin Tough <[email protected]> wrote: > I am just starting to learn vim. I use Fedora and would like to know > whether most programmers use vim from the console or do they/you use > gvim. I have read that using one instance of vim is the best usage. > > ViEmu: would any of the experienced vim users be able to comment on the > completeness of the "ViEmu" software and its compatibility/stability > when used with Visual Studio. > > Namaste, > > Kevin Tough
Unlike those who have posted so far, I use gvim almost exclusively, on both Windows (of various flavors) and Ubuntu. For each *related* task, I use a single instance of Vim. For example, if I'm working on documentation for a tool using HTML, a bugfix for some software (including a diff between two previous versions), and some script updates for automated code changes of some sort, I'll probably have at least 3 and sometimes 4 Vim instances open. Each instance probably has several files open in multiple tab pages, with multiple windows in each tab page. Vim is flexible enough to allow me to work however I want. On Windows, I use file associations to automatically launch file I double-click on in a new tab in Vim: http://vim.wikia.com/wiki/Launch_files_in_new_tabs_under_Windows http://vim.wikia.com/wiki/Windows_file_associations I set have a few pre-defined names set up to align with my workflow, opening .vim files in a VIMCONFIG Vim server, .html and .css files in an HTMLEDIT server, and .c files in the normal GVIM server. I don't have much reason behind my choice, I just like it better. I'm not fond of being bound to a terminal window, I use it when I need to but usually separate from Vim. I do know that the terminal version causes all sorts of headaches; as evidenced by the mailing list, wiki, and IRC channel. More key mappings are normally available in gvim, you don't need to worry about how many colors your term has or how it renders combinations of ctermfg and cterm, color schemes are usually written for gvim, you can set the font quickly and easily, etc. As for interacting with other tools which need to know when the editor is done, there's the -f argument when launching Vim. I'm also not fond of needing to suspend Vim with Ctrl-Z and bring it back up whenever I want to do work with the terminal. I like having them side-by-side. I could launch two terminal windows or start looking into "screen" (I think anyway, never tried it), or I could just launch the GUI and be done with it. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
