I agree that this is too slow. I'm on a very fast machine, and when GHC is hot yi starts up pretty quickly (though I still have time to see the "Recompiling custom yi" message). However, when GHC is cold it takes several seconds to start up. I would much prefer simply adding documentation (perhaps even as comments in the example yi.hs files) that informs the user that if their config file depends on any external modules they should simply remember to call `yi --force-recompile` after making any changes. We could even add a --recompile-check flag that invokes GHC exactly as we're doing now, but unlike --force-recompile it won't actually recompile the custom yi if it doesn't have to. I think users who customize their yi.hs in ways not supported by the original heuristic should be smart enough to understand how to use --force-recompile or the proposed --recompile-check.
-Kevin Ballard On Fri, Apr 10, 2009 at 11:09 AM, Jeff Wheeler <j...@nokrev.com> wrote: > > On Fri, 2009-04-10 at 18:20 +0200, Jean-Philippe Bernardy wrote: > > > I don't think it's wise to make "how to load the configuration" > > configurable. We already have a compile-time flag to bypass > > configuration anyway (hacking). > > Yeah, I think you're right . . . that would be a bit silly. > > > At the moment I lean towards rolling back the patch. > > Agreed; the benefits (to me) don't seem to outweigh the startup cost on > every execution (for me). > > Jeff Wheeler > > > > > -- Kevin Ballard http://kevin.sb.org kball...@gmail.com --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
