Alexei Alexandrov wrote: > Ben Schmidt wrote: >>> Is it possible to get what I want? >> With a little jiggerypokery it should be! Perhaps something like >> >> gvim --remote-send "<C-\><C-N>:cfile build.log<CR>:call foreground()<CR>" >> >> You'd obviously want to wrap that in a shell script or alias... >> >> And there are other possibilities if that doesn't work... If you're on >> Windows, running remote_foreground() in the client might be better than >> running foreground() in the server, for instance; then you'd have to run >> a remote_send in the client, too, via a :call not using the >> --remote-send argument. >> > > Err... I'll play with it, thanks! But I just realized that I don't like > --remote-send since it doesn't create a new Vim instance in case when no > server is running yet... > > Keeping thinking and trying...
If not on Windows, perhaps an autocommand to automatically raise Vim whenever it opens a file? In .vimrc: augroup AutoForeground au! au BufReadPost * :call foreground() augroup END Ben. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
