Comment #4 on issue 276 by gwern0: HConf should be a standalone package http://code.google.com/p/yi-editor/issues/detail?id=276
> Btw I've come to think that the directory layout, with config file and > compilation files in the same directory, looks a little dirty. It's Unix convention for each major app (like a window manager or editor) to have a config file, a directory, or both; doesn't seem like a big deal to me. > It's OK to have two applications, xmonad and yi, doing that, but if we go > for the general case, how about putting compilation files into a seperate .hconf directory, similar to how cabal hides in .cabal? (Idea: When you're doing a backup of ~/.[^.]*, you can exclude .hconf.) This reveals interesting other design problems ;) namely: Should the config files remain in ~/.app/, or go to ~/.app.hs, or even ~/.hconf/app.hs? The advantage of the latter is that you can share code between your configurations, the disadvantage being that we wouldn't hide the name of the library, HConf, from the user. When would one actually share code? I can't think of a single thing that could be shared between the 40 or so xmonad/yi config files I've seen. If there is sharing possible, then there's something wrong... -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
