Elliot Shank wrote:
A.J.Mechelynck wrote:
Elliot Shank wrote:
Change the application title for each vim instance to be what it
would be for a OS-level window in other OSs so that they're
differentiable. (Yeah, I'm probably repeating what a lot of other
people have requested, but...)
see ":help --servername". That setting defines the "program name" as
seen on the titlebar. If you don't edit the same file in different Vim
instances, the filename displayed on the titlebar will also help you
differentiate them.
The Mac version of Vim does not support the +clientserver build option
and thus doesn't support that command-line option.
Anyway, that wouldn't do any good for Vim instances started by the Finder.
You don't understand: switching between windows and switching between
applications are two different things on the Mac. Using command-tab
switches between applications; command-` switches between windows within
an application. When command-tabbing between applications, all you get
is the application name; this isn't anything specific to Vim. It's how
all Mac apps work, e.g., if you've got a word processor with multiple
documents/windows open, all you'll be able to see when switching is the
application's name. Yes, the Vim window title-bar reflects all the
usual information you see in it on other platforms, but that does you no
good when switching between Vim instances.
Actually, to get multiple instances of gvim running on a Mac takes a bit of a
hack. There's only supposed to be a single process running of any given
application at a time. If you try to launch an application while its already
running, no new process is created and the existing process's windows are
brought forward. If that launch attempt was caused by trying to open a
document that that app handles, then the existing process is told to open it.
It's like a --remote command line option is forced to be there, whether you
want it or not.
