Old workflow: Search MXR for identifier -> click on a result (nsISomething.cpp
line 500) -> wait for a 6000-line file to load -> decide that you want to edit
this file -> open this file in vim
New workflow: Search MXR for identifier -> click on a result -> result opens in vim.
mxr-vim needs to know three things:
These pieces of information can be set via about:config. They are located under
- where the source tree on your disk is located (no default)
- where your shell is located (default /bin/sh)
- where vim is located (default /usr/local/bin/mvim)
To complete the circle of mxr-vim integration, I use the following mappings in
my .vimrc, which fire off a search of MXR for the word under the cursor:
nnoremap <c-f>i :! open -a Aurora.app 'http://mxr.mozilla.org/mozilla-central/ident?i=<cword>'<cr><cr>
nnoremap <c-f>f :! open -a Aurora.app 'http://mxr.mozilla.org/mozilla-central/search?string=<cword>'<cr><cr>
This page is part of the LegacyCollector website.
Disclaimer: All material on this site is property of their respective owners and available under
open licenses to the best of our knowledge. If you are an author and would like anything removed,
then please write an e-mail to legacy [at] collector dot org.