Earlier quoted context omitted.
Also worth remembering is that every command that deletes really cuts . Which is to say, deletion commands like x and dd store the deleted content in the register that will be used when you hit p or P. This is important to know both because it can be very useful sometimes and because it can get in your way other times (e.g., if you're trying to repeat an action and keep replacing a line with another line, you'll have…
Or you can specify the register name. Don't limit yourself to the unnamed register.
Vim is hard, I just want to click around
61–70 of 98 posts
Re: Vim is hard, I just want to click around
#62Earlier quoted context omitted.
Or even alias vimtab="gvim -f --remote-tab-silent" in your .bashrc, .zshrc or equivalent
The Mac OS X command open allows this directly: $ open -a macvim filename.ext which permits: $ alias mvim="open -a macvim" as a shortcut.
Re: Vim is hard, I just want to click around
#63Earlier quoted context omitted.
It has vimscript, but vimscript is at best emacs-lisp's inbred nephew who is just as old but huffs glue and has sex with chickens.
Actually, you can also use mzscheme, perl, python, ruby, and lua to script vim.
Re: Vim is hard, I just want to click around
#64Getting familiar with GNU screen and within vim, liberal use of :tabnew foo got me to prefer a terminal emulator for working and notes over eclipse / gedit / nautilus. (gt and gT move to different tabs and :tabm N moves the current tab to tab N btw). If from within vim you :mksession bar.vim, vim saves all your open tabs so you can :wqall and open the tabs again from the shell with vim -S bar.vim
Like seemingly everyone, I organize projects into project/doc, project/src, project/data, project/bin etc. For example, I have a start.vim each in project/doc and project/src.
Then I put lines in ~/.screenrc
chdir /home/horseshoes/workin/myproject/doc
screen -t myproject_doc vim -S start.vim
chdir /home/horseshoes/workin/myproject/src
screen -t myproject_src vim -S start.vim
screen -t bash bash
When I start screen it automatically opens one window containing a vim sesh with all my most-looked-at documentation tabs (so I can refer to wth I was thinking and organize my mental pushdown stack a little), one window containing a sesh for the source files I currently work on, and a third window holds a shell so I can look for and alter other files or start sqlite3 or make or w/e.The point is it fires up work for me so I just have to open a terminal and type screen and it's instantly ready compared to opening eclipse or visual studio and then navigating to the relevant related notes and documents, or cluttering up the place with a billion (or even 2 or 3) terminal emulators, since screen multiplexes them. I also like to have screen windows open with cmus (music) and a python interpreter (my calculator and preferred random 'what to make for dinner' decision maker).
I also prefer the command-line environment for programming and also most general use because of the kool tools it's full of you are no doubt very acquainted with (ls, locate, grep, less, ps, pipes et al).
(End of mysteriously censored post.)
I have no idea why this might have been censored. Maybe it's the obnoxious use of "w/e" as an abbreviation for "whatever"?
Re: Vim is hard, I just want to click around
#65Re: Vim is hard, I just want to click around
#66Re: Vim is hard, I just want to click around
#67Reposting this for horseshoes; it seems to have been mysteriously censored. Getting familiar with GNU screen and within vim, liberal use of :tabnew foo got me to prefer a terminal emulator for working and notes over eclipse / gedit / nautilus. (gt and gT move to different tabs and :tabm N moves the current tab to tab N btw). If from within vim you :mksession bar.vim, vim saves all your open tabs so you can :wqall and…
This is why I browse with dead comments enabled. A single particularly poor comment is a rather inaccurate indicator of future comment quality.
Re: Vim is hard, I just want to click around
#68I have a hard time watching people traditionally navigate filetrees and tabs with emacs and ido-mode enabled I press Ctrl+X B to open a buffer, Ctrl+X F to open a file, I typically type 2 or 3 characters from the filename and emacs gives me a list of matches (with autocomplete), usually the first suggestion is correct and I press return to open the file. I barely need to think while I do this, there is no visual clut…
Re: Vim is hard, I just want to click around
#69Earlier quoted context omitted.
The reason that people use (mac)vim is not necessarily the ‘powerful navigation keys’ etc. For me it’s the ability to deal with large files and the crazy indentation rules people use and I know it’s the same for quite some other users. The way people work differs from person to person, the idea that someone should always just keep on trying, even if something doesn't feel right, is in my opinion useless. The real mor…
Agreed - this is pretty much the only reason MacVim lives on my machines. It handles huge files way better than anything else I've tried. I can use vim. I know it pretty well. But the inescapable fact is that, for me, it's clunky and requires more thinking than just using a mouse and pointing at something, then typing what I want to type. I use it because I haven't found something better (and I'm sure it exists, I ju…
Re: Vim is hard, I just want to click around
#70I have a hard time watching people traditionally navigate filetrees and tabs with emacs and ido-mode enabled I press Ctrl+X B to open a buffer, Ctrl+X F to open a file, I typically type 2 or 3 characters from the filename and emacs gives me a list of matches (with autocomplete), usually the first suggestion is correct and I press return to open the file. I barely need to think while I do this, there is no visual clut…