search

gregsexton / gitv

gitk for Vim.
936 stars 59 forks source link

error on OS X #25

Closed phildobbin closed 12 years ago

phildobbin commented 12 years ago

I'm using Gitv on Linux & it works great but on OS X when I hit in the browser window I get:

Error detected while processing function <SNR>85_OpenGitvCommit..<SNR>85_MoveIntoPreviewAndExecute..<SNR>85_RecordBufferExecAndWipe: line 3: E492: Not an editor command: Gedit 8194a06

followed by:

press ENTER or type command to continue

The latest Fugitive is installed on both machines & their runtimes are virtually identical.

gregsexton commented 12 years ago

Hi,

I can't diagnose this without a little more info I'm afraid. I run gitv on both OS X and Linux machines without a problem so I doubt that it's because of OS X.

When you say that the runtimes are virtually identical, what are the differences?

What is the output of :let b:git_dir when you run it from the gitv browser window? Is this the same as when run it in the file buffer that you activate gitv from?

Thanks,

Greg

gregsexton commented 12 years ago

Oh, you should also try stripping down your vim config. If you run vim with an empty .vim/.vimrc and only gitv and fugitive installed does it still do this? Can you reproduce this behaviour every time?

phildobbin commented 12 years ago

this is so simple it's laughable:

on Linux & OS X I'd taken your advice & used the mappings a la:

nmap <leader>gv :Gitv --all<cr>

which worked great but for personal idiosyncratic purposes, on OS X I'd used instead of which it seems caused the error: well, I've just changed it to & it now works & a E492 usually means a vimrc map error.

Sorry for the noise & thanks for the great plugin...

phildobbin commented 12 years ago

sorry that should've read:

on OS X I'd used <CR> instead of <cr>

gregsexton commented 12 years ago

Glad this is fixed for you. Is there really a difference between <cr> and <CR>?! Can you reproduce this if you change it back?

phildobbin commented 12 years ago

No. That's what's so frustrating! I've had similar things happen before involving Vim across all three OSs I'm running it on as my main editor.

Saying that it's mostly OS X on which this happens. I find you have to log out & log in again fairly frequently otherwise the system can get screwy. Linux is fine on the whole...