Surprised PeepOpen hasn't been mentioned yet. I use it exclusively with MacVim on OSX. It is a bit unconventional but works amazingly well: http://peepcode.com/products/peepopen
PeepOpen is the main reason I use MacVim. So excellent.
Vim is hard, I just want to click around
71–80 of 98 posts
Re: Vim is hard, I just want to click around
#72I 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…
I recently wrote something very similar to Emacs' ^xf for VIM. Sadly I haven't the time to work on it as much as I would like. For those who are interested: you can grab it at https://github.com/Bogdanp/quicksilver.vim .
Re: Vim is hard, I just want to click around
#73Earlier quoted context omitted.
> don't give up Yes. All the tutos I have read recently insist on using hjkl, which is a matter of taste, but do not emphasize what I believe is the most important (for terminal use): cut and paste. - Easy cut and paste in Vim is done with yy and p, avoid mouse and ctrl-c/v or any other trick that is not "inside" Vim. - Good trick are to first select a block with . - Don't forget P, which is pasting above current lin…
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…
vnoremap p "_dP
"_ is the blackhole register, with this the replaced text disappears and you can continue "putting" the new text at will.
Re: Vim is hard, I just want to click around
#74Surprised PeepOpen hasn't been mentioned yet. I use it exclusively with MacVim on OSX. It is a bit unconventional but works amazingly well: http://peepcode.com/products/peepopen
PeepOpen is the main reason I use MacVim. So excellent.
I have struggled for a while to get PeepOpen and MacVim working together. I can run :PeepOpen, and it will switch to the running peepopen application, but it doesn't load up with the project files. I've tried all sorts of .vimrc config settings that the internet has to offer, but none worked.
What's in your config for it?
Re: Vim is hard, I just want to click around
#75The times I open new file vs times :e line is already in my vim/bash history is tiny. And that tiny amount is handled fine by vim's filename completion.
There seems to be a big divide in usage between gui vim'ers who are probably doing one window/ide thing vs terminal vim'ers who probably have multiple terms/vim's open and use unix/cmd line as their die.
Note I make value judgment as to which is better (I'm sure people vary and so should their tools). My point is you should figure out which one you are and filter vim suggestions appropriately
Re: Vim is hard, I just want to click around
#76Reposting 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…
horseshoes is hellbanned for this comment: http://news.ycombinator.com/item?id=2928894 This is why I browse with dead comments enabled. A single particularly poor comment is a rather inaccurate indicator of future comment quality.
Certainly some moderation is appropriate for that comment, but I think a permanent invisiban is a bit of an overreaction to that. Does this kind of thing happen frequently?
Re: Vim is hard, I just want to click around
#77Earlier quoted context omitted.
Unfortunately, the remote features require a GUI version of vim. Personally, I prefer to run vim in a tab of my terminal.
Under Linux I always run vim in a terminal. Part of this is habit because I (in the past) often edit files on remote computers and I like the consistency. On my mac I end up using MacVim mostly so that my Vim and Terminal apps can be considered separate apps for the purpose of things like spaces, and it just seemed to integrate a little better with the Mac infrastructure. But in general I haven't found a reason to pr…
The reasons I run gvim rather than terminal vim are basically all because sufficiently capable terminals do not exist:
- The excellent "solarized" colour scheme only works properly with 24-bit color unless you're willing to mess with the terminal palette and break all your other terminal apps. No terminal I know of supports 24-bit color.
- I have a handy keybinding that cycles through open windows and tabs, I find it makes the most sense bound to Ctrl-Tab and Ctrl-Shift-Tab. Neither key can be bound in any terminal I know of.
Re: Vim is hard, I just want to click around
#78I've always been a little puzzled by people who use a file-drawer or file-list or similar addon with Vim, and I now I think I know why: I'm guessing most of these people have Vim open as their One Tool, much like another programmer might have Xcode or Visual Studio open as their One Tool, and they want to get everything done in it. At work, I usually have at least two windows open at all times: Vim full-screen on one…
Unfortunately, the remote features require a GUI version of vim. Personally, I prefer to run vim in a tab of my terminal.
The remote features require a version of Vim with GUI features compiled in, but you don't have to run vim in GUI mode to use them. The only difference is that when started in console mode, Vim won't register itself as a server unless it's explicitly told to use a particular server name:
vim --servername FOO
vim --servername FOO --remote-tab ~/.bashrcRe: Vim is hard, I just want to click around
#79I've always been a little puzzled by people who use a file-drawer or file-list or similar addon with Vim, and I now I think I know why: I'm guessing most of these people have Vim open as their One Tool, much like another programmer might have Xcode or Visual Studio open as their One Tool, and they want to get everything done in it. At work, I usually have at least two windows open at all times: Vim full-screen on one…
Or even alias vimtab="gvim -f --remote-tab-silent" in your .bashrc, .zshrc or equivalent
Ah, but if I set it up as an alias, I can't use it with other apps that have a configurable "Send to editor" function. :)
Re: Vim is hard, I just want to click around
#80Earlier quoted context omitted.
The Mac OS X command open allows this directly: $ open -a macvim filename.ext which permits: $ alias mvim="open -a macvim" as a shortcut.
I have found issue with this recently. When I have multiple tabs open, and then attempt to open multiple files after that, it opens them all in a split view :/
:help 'tabpagemax'