Steve Hall wrote: > On Mon, Jan 15, 2018 at 1:56 PM, Bram Moolenaar <Bram moolenaar net> > wrote: > > Steve Hall wrote: > > > > > > Any interest in moving the entire Vim installer to NSIS? > > > > There have been a few attempts at this, but they all dropped some > > funcationality. Best would be to do this step by step, making sure > > it still works for all different kinds of users. > > Maybe why nobody has tackeled this. Going through dosinst.c I find all > these options: > > * (Find existing non-standard installation) > * Installation location > * Runtime location > * Working directory location > * Plugins location ($VIM or $HOME) > * Vi, Vim, or Vim+ behavior > * Remap some keys to Windows behavior > * Mouse right button behavior (Unix, Windows, visual) > * Install vim.bat and/or gvim.bat in %PATH% > * Install vimrc > * Install diff.exe > * Install explorer right-click menu (gvimext.dll) > * Create Start Menu shortcuts > * Create Desktop shortcuts > * Register OLE
We are talking about the NSIS installer, not the command line one. > Why not just install with sane defaults? Cream's Vim installer (0.5m > downloads) uses just one pick in three choice screens: > > * Forced acceptance of license (only choice actually required) > * Confirm default behaviors (tick/untick): > + Start Menu shortcut > – (No Desktop shortcut) > + Add Windows Explorer right-click menu > + Native language support > + Install vimrc (prompt to back up if existing) > – (No command prompt .bat files) > + Install Vim extension for MS Visual Studio > – (No plugin directories in %HOMEDRIVE%%HOMEPATH%) > * Confirm default installation path (C:\Program Files (x86)\vim) > > There is one more prompt to overwrite if there is already a (g)vimrc. Let's not try to discuss removing options from the NSIS installer, there is always someone who needs some option. Let's just make it work well and perhaps even add some option. We probably still need to invoke the command line command, e.g. to create the batch files. > Our assumption is that experts don't need a GUI installer, so the NSIS > is for newbies or casual users. It puts runtimes, plugins, diff, etc. > in the sofware directory, registers OLE, installs a single windows > explorer right-click "Edit" menu item, and uses Vim's default options. > > A similar structure to Vim's NSIS would avoid it (and dosinst.c) being > too complex to write and maintain. [Please take as Einstein and Occam > simplicity, not BSB (http://dilbert.com/strip/2017-12-25 ff). ;) ] The command line installer has been around for many years, there is no maintenance problem. -- hundred-and-one symptoms of being an internet addict: 214. Your MCI "Circle of Friends" are all Hayes-compatible. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
