Tuesday, July 16, 2013

MacVim forces last pattern search with flags to vim

I've got a problem with MacVim that I'm hoping can be accepted here. I find that MacVim forces certain flags to be used which are mostly inconvenient. Can this be fixed in any way?

When using /usr/local/bin/mvim to start vim directly from the command line benign flags are used and can be adjusted in /usr/local/bin/mvim anyway:

$ ps aux | grep vim
/usr/bin/grep -i vim
/Applications/MacVim.app/Contents/MacOS/MacVim -MMNoWindow yes
/Applications/MacVim.app/Contents/MacOS/Vim -f -g test.txt

When double clicking a text file in the Mac Finder MacVim uses two flags which force particular behaviour.

The '-o' flag is supposed to open multiple files in separate windows.
I don't want this behaviour as I prefer splits, but actual behaviour varies for unknown reasons.

The '+/' initates a search on the last pattern used.
This is reliable and consistent but again elicts unwanted behaviour.

When the last pattern matches the file comes up highlighted due to my settings.
I have to type :nohl to view the file properly.
Often this is the entire text that is highlighted in red.

When the pattern does not match it still causes a problem.
Vim responds "error detected" and "pattern not found".
This requires a confirmation every time before I start editing.

$ ps aux | grep vim
/Applications/MacVim.app/Contents/MacOS/MacVim -psn_0_3105526
/usr/bin/grep -i vim
/Applications/MacVim.app/Contents/MacOS/Vim -g -f +/ -o /Volumes/Data/Users/user/Desktop/test.txt

See the plus slash "+/" and the "-o" ? That's the culprit right there!

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: