MacOS下Vim可视化模式Chrome搜索选中内容的函数失效求助

Let’s break down why your current setup isn’t working and fix it step by step:

Key Issues in Your Original Code #

1. Incorrect background execution symbol: You used & (an HTML escape sequence) instead of the actual & symbol needed to run the open command in the background. Vim was treating & as part of the URL, not a command to detach the process.
2. Missing URL encoding: If your selected text has spaces, special characters, or non-ASCII characters (like Chinese), directly appending it to the URL will break the search link.
3. Unprocessed whitespace: Visual selections might include extra newlines or leading/trailing spaces, which can lead to empty or invalid searches.

Corrected Vimscript #

function! GoogleSearch()
  " Grab content from the 'g' register and strip extra whitespace/newlines
  let searchterm = trim(getreg("g"))
  " Encode the search term to handle spaces, special chars, and non-ASCII text
  let encoded_term = urlencode(searchterm)
  " Run the open command in the background with a properly formatted URL
  exec ":!open -a Google\\ Chrome 'http://google.com/search?q=" . encoded_term . "' &"
endfunction
vnoremap <F6> "gy<Esc>:call GoogleSearch()<CR>

What Each Change Does #

• trim(getreg("g")): Removes any leading/trailing spaces or newlines from your visual selection, ensuring you’re searching only the text you intended.
• urlencode(): Converts problematic characters (like spaces to %20, Chinese characters to UTF-8 escape codes) into URL-safe format, so Google can correctly parse your search query.
• Replaced & with &: The & tells Vim to run the open command in the background, so you won’t get stuck waiting for Chrome to close before returning to Vim.
• Single quotes around the URL: Prevents conflicts between special characters in your search term and the double quotes used in the Vim command string.

How to Test #

1. Highlight any text in Vim’s visual mode.
2. Press <F6>—Chrome should launch immediately and load the Google search results for your selected text.

内容的提问来源于stack exchange，提问作者Spike