On Thu, Dec 24, 2009 at 1:22 PM, Sergey Khorev wrote: > > 1) the installer does not work on Vista/Windows 7 with UAC turned on. > If distutils don't support request of elevated rights, there is a > simple workaround: add 'setup' word to the installer name, e.g., > pyclewn-1.0.win32_setup.exe
Thanks for the workaround. I will change the name of the installer. > 2) I wonder why Pyclewn commands are not allowed in the initial > (empty) buffer? It's quite inconvenient to open a file if your current > plan is to use Cfile command only. Vim does not like netbeans keystring pressed on a buffer that has not yet been registered by netbeans (see Vim function netbeans_keystring). This defeats the trick of using netbeans keystrings as gdb commands when in the NoName buffer. I will make a Vim patch. I agree it is very inconvenient. > 3) Vim creates .(clewn)_console.swp files in its starting directory. > It is especially noticeable if Pyclewn starts from desktop and Vim > crashes. Maybe its worth setting 'noswap' for console buffer? Right, and since there is now the --maxlines option, setting the 'swapfile' option to limit the amount of memory used by Vim is not necessary anymore. I will set the 'noswapfile' on the console and variables buffer. Xavier ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
