I had trouble with jpb's suggestion of pulling out Editor or something; stuff is pretty well-connected, so was ending up bringing tons of stuff. I started a little over a week ago, but haven't played with it much since then:
https://github.com/yi-editor/yi-contrib (I've removed the corresponding things from the main yi package. I'd like to see separate configs for vim/emacs that depend on various extras like Hoogle. That is, don't remove the vim/emacs bindings from core, but remove the contrib stuff from them, then put vim/emacs configs that extend the core ones in contrib.) On Mon, Feb 21, 2011 at 6:48 PM, Tony Miller <mcfiredr...@gmail.com> wrote: > If this is feasible it would be really great. Building Yi at all can > be an arduous process, given all the dependencies. > > On Sun, Feb 6, 2011 at 12:44 AM, Jean-Philippe Bernardy > <berna...@chalmers.se> wrote: >> On Sun, Feb 6, 2011 at 1:32 AM, Jeff Wheeler <wheel...@illinois.edu> wrote: >>> Hey all, >>> >>> If we can get Yi on github/code.google.com, I've got something I think >>> would be great for Yi. >>> >>> I'd like to see us split off a large amount of the cruft in Yi into a >>> separate yi-contrib package. The tricky part of this is the >>> keybindings. Do user configs now have to explicitly import and add >>> keybindings for, say, Hoogle bindings? I doubt there's a good way to >>> have Hoogle "register" its bindings in a default config somehow. >> >> Indeed not; you need to do it the xmonad's way. >> >>> Perhaps the best solution is to copy xmonad and have alternate configs >>> for emacs and vim in yi-contrib (a la gnomeConfig in xmonad) which >>> depend on many of the contrib libraries. >> >> I think you'll want to keep the keybindings for vim & emacs in the core; >> because most people will require this for "testing" yi. Alternatively, >> there could >> be a minimal keybinding by default which is the only one in the core. >> >>> Possible yi-contrib candidates: >>> - Shim (does this even work anymore?) >>> - Yi.Char.Unicode (not sure) >>> - Yi.UI (non-vty ones) >>> - Yi.Verifier >>> - Yi.Completion >>> - Yi.Dired >>> - Yi.GHC (uses Shim) >>> - Yi.Hoogle >>> - Yi.IReader >>> - Yi.Process (maybe not, if important stuff depends on it) >>> - Yi.Scion >>> - Yi.Snippets (this would require dynamically loading snippets, probably) >>> - Yi.Tags >>> - Yi.Templates >>> - Yi.TextCompletion >> >> You could go the other way: take (say) Yi.Editor and pull only the stuff that >> it needs. >> >> Cheers, >> JP. >> >> -- >> Yi development mailing list >> yi-devel@googlegroups.com >> http://groups.google.com/group/yi-devel > > -- > Yi development mailing list > yi-devel@googlegroups.com > http://groups.google.com/group/yi-devel > -- Jeff Wheeler Undergraduate, Electrical Engineering University of Illinois at Urbana-Champaign -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel
