[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vim-mac
Subject:    Re: Vim on Mac: What's NeXT? ;)
From:       Gregory Seidman <gseidman () acm ! org>
Date:       2001-11-07 5:40:12
[Download RAW message or body]

Dany St-Amant sez:
} Hi,
} 
}   It's probably time for a quick survey as I don't seem to work on what 
} people want.
} What should be the priority work done in Vim for Mac?
} (You can also answer as: who what to do what?)
} 
} -Dialog boxes?
}    (currently in progress)

Not vastly important to me.

} -Drop to shell?
}    (Huh? this currently work on my development stream can't believe it)

Er, this should work flawlessly in MacOS X. It is *high* priority.

} -pre-MacOS X bug: filename weirdness?

I don't know what that means. Colon as a separator or something?

} -Terminal/Carbon combo version?

What I'd really love is one binary capable of one of the OS X GUIs (Cocoa
or Carbon), one of the X11 GUIs (Athena, Motif, or GTK), and the terminal
non-GUI. It would make me happy to be able to ssh in and have the terminal
frontend, run it from Terminal.app and have it pop up (having forked!) as a
.app with a doc icon and all, and run it from an xterm and have it pop up
on my X display. Determining which to do can be handled by checking certain
environment variables (DISPLAY, and something else for the Terminal.app)
and whether it was given a -psn commandline flag.

Nonetheless, I consider it low priority, since several separate binaries
can coexist nicely and use the same .vim files, and I can write a script to
distinguish when to use which.

} -Find/Replace/Font Selection dialogs?

Font selection is desirable, but I don't care about dialogs for
find/replace... :s is sufficient for that. And as long as there is some
hacky way to change the font (e.g. mess with some file within the Vim.app
directory tree), I don't need to change the font on the fly.

} - --remote from Terminal.app for Carbon?

Oh, yes please! Call it medium priority.

} -Toolbar?
}     (Seem easy as 123 in Cocoa, but in Carbon, yikes)

I don't care for the toolbar, myself.

} -Cocoa version?
}     (who come first main.c or gui_carbon.m? Any NeXT expert around?)

I consider this fairly high priority. I would really like to have things
set up so that the Cocoa version is source-compatible with GNUstep.

} -Terminal/Motif/Carbon combo version?
}    (could ask the main stream for a Motif/GTK version first)

Oops, I talked about this above. A cool feature, but low priority.

} Other main concern?

I tend to use vim in several separate sessions. I do so because there is no
support for multiple heads (what emacs calls frames and what every GUI
toolkit calls windows) in a single session. Under MacOS X I would be likely
to run Vim from Terminal.app multiple times, filling the dock with multiple
Vim icons. I'd prefer to open another head with a file. First, though, we
have to handle multiple heads in all the other frontends so there is a
reasonable and consistent interface. I consider this the highest priority
for vim development, on MacOS X or otherwise.

} Dany
--Greg

[prev in list] [next in list] [prev in thread] [next in thread]