Re: vim keybindings
Re: vim keybindings
- Subject: Re: vim keybindings
- From: "Tristan O'Tierney" <email@hidden>
- Date: Sat, 3 Jan 2004 21:58:25 -0800 (PST)
honestly, that's *exactly* what i'm looking for.
my big beef with using vi in a separate window is
having to deal with having two separate windows for
coding, why not just integrate the window into xcode?
in general, i'd like it of all cocoa editor based
widgets simply had the ability to be extended system
wide with a plugin to allow vi keys, or emacs keys,
etc. it sounds funny at first, but look: cocoa
widgets already have some basic emacs keys. the only
reason it's easier to implement emacs keys is because
they can be defined with ctrl, alt, shift, and meta
combinations. vi keys require the ability to go in
and out of different modes through the use of ESC.
this functionality is hard to implement without being
able to modify the underlying widget's events. i do
think this needs to be done eventually.
and to dave:
surely there must be a middle ground us unix and mac
developers can agree upon? a quick fix like kevin's
suggestion would work if done properly i think, but it
still is an inbetween fix to the original problem:
editor widgets are too hard to customize. i'm not so
sure extending the apple events support for vim is the
long term solution. so the integration with the
external terminal would be better, but that's just
dodging the issue is it not?
--- Kevin Grant <email@hidden> wrote:
> > Just to set expectations appropriately... It's not
> likely that we'll
> > add vi key binding support anytime soon. The
> command model in vi is
> > just too different from what the AppKit text
> system can handle.
> >
> > Something more likely to happen would be better
> support for
> > AppleEvents in vim. Last I checked, it didn't
> really support them at
> > all, so our integration isn't very good. That
> (mostly) needs to be
> > fixed in vim. And since it's open source, I'd
> encourage people to take
> > a look at getting it done.
> >
> > The next most likely scenario (though far less so)
> would be for
> > someone to do a vim plugin editor for Xcode. Our
> plugin API isn't
> > public yet, but that wouldn't be the biggest
> hurdle. If someone could
> > get vim running inside a Cocoa view (in a
> document-based app would be
> > best), the rest would be pretty easy.
> >
> > I'm certainly in no position to promise anything
> here, but it's pretty
> > likely that we'd be able to help get the
> AppleEvent support working
> > with vim. We would love to see the same level of
> support for it as we
> > currently have for emacs, BBEdit and SubEthaEdit.
> (And we'd love to
> > see the support for all external editors improve
> over time too).
>
>
>
> Rather than "emulate more", why not just run vim
> itself within a VT
> terminal emulator in Xcode? That implies all key
> bindings would be
> solved automatically by virtue of focusing the
> terminal view.
>
> I've often wondered why the Terminal utility is not
> a generic Cocoa
> view. Once you have an entry point for data to be
> streamed to a full
> VT terminal, it is fairly simple to get a Unix
> process to run inside it
> "properly". [I know this because I did it last
> year, for MacTelnet.]
>
> I am hoping the Xcode and Terminal guys can get
> together and have Xcode
> just "instantiate a Terminal" in an Xcode window in
> order to support
> running Unix programs. Is this feasible?
>
> (My terminal implementation might also be useful,
> however it is so
> strongly Carbon-based I have no idea what it would
> take to convert its
> User Pane into a Cocoa view. Probably not simple.)
>
> Thanks,
> Kevin G.
>
__________________________________
Do you Yahoo!?
Find out what made the Top Yahoo! Searches of 2003
http://search.yahoo.com/top2003
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.