On Thu, 2007-12-27 at 09:41 +0900, 강예형 <philmasterplus gmail com> wrote: > > I've noticed that while the Cream/Vim one-click MS Windows installer > looks more "modern" (by using the Modern UI provided by NSIS), it > provides less configuration options than the Windows installer > provided by the Vim project itself.
True. Most of this is because Vim's version actually relies on an included binary executable that does some of the configuration. > Because I am a Korean, I need some automatic language > configurations, which are automated by default. I'm curious what these are, how does it know what to do? Do you have to select the language from the list or does it detect language somehow from the environment? > Also, the installation is missing vim (because it works only on > gVim, obviously) plus many batch file configurations. Our gvim installer without Cream has both. But we don't include it with the Cream one since they are not compatible. (Besides, vim in a Windows Command Prompt is flakey at best according to the help.) > Am I asking too much by wanting both flexibility and ease of use? Not at all, although I'm not certain all the utility of the binary installer can be reproduced in NSIS. > The only way for me, I suppose, is to download the source > installation and install it myself. If you can help me pinpoint exactly what is missing, we may be able to fix things. We don't ever want to leave users out in the cold, but sometimes there are a lot of dependencies to make something work. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ cream-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cream-general
