vim73brt+vim73bole can't run under windows 2000 sp4
Hi list, I've downloaded vim73 beta(rt.zip+old.zip), after extract them and run gvim.exe, it warns: gvim is not a valid Win32 application. My OS is windows 2000 sp4. -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China -- 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
Re: vim73brt+vim73bole can't run under windows 2000 sp4
On 26/07/10 11:21, Yue Wu wrote: Hi list, I've downloaded vim73 beta(rt.zip+old.zip), after extract them and run gvim.exe, it warns: gvim is not a valid Win32 application. My OS is windows 2000 sp4. Hm, IIUC Bram compiled it with MS Visual C, but maybe MSVC for Vista or for Windows 7. Then of course, getting a new version of Windows is costlier than getting a new version of Linux. I'm not sure what I would do in your place. Maybe compile your own? See: http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial http://users.skynet.be/antoine.mechelynck/vim/compile.htm Best regards, Tony. -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- 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
Re: vim73brt+vim73bole can't run under windows 2000 sp4
On Mon, 26 Jul 2010 17:34:44 +0800, Tony Mechelynck antoine.mechely...@gmail.com wrote: On 26/07/10 11:21, Yue Wu wrote: Hi list, I've downloaded vim73 beta(rt.zip+old.zip), after extract them and run gvim.exe, it warns: gvim is not a valid Win32 application. My OS is windows 2000 sp4. Hm, IIUC Bram compiled it with MS Visual C, but maybe MSVC for Vista or for Windows 7. Then of course, getting a new version of Windows is costlier than getting a new version of Linux. I'm not sure what I would do in your place. Maybe compile your own? See: http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial http://users.skynet.be/antoine.mechelynck/vim/compile.htm As vim72 works find for me, I will stick to it. I want to have a try with 73 beta is just to check that, if the bug of non-working :!cmd completion on windows has been fix in the new version :) -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China -- 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
Re: [patch] added completion to the :setfiletype command.
Hi Dominique!
On Sa, 24 Jul 2010, Dominique Pellé wrote:
Hi
Attached patch adds completion to the :setfiletype command.
Example:
:setf javaCTRL-D
javajavacc javascript
-- Dominique
diff -r 0c8219a26bc9 src/ex_docmd.c
--- a/src/ex_docmd.c Sat Jul 24 20:57:44 2010 +0200
+++ b/src/ex_docmd.c Sat Jul 24 23:36:07 2010 +0200
@@ -3829,6 +3829,7 @@
xp-xp_pattern = arg;
break;
+ case CMD_setfiletype:
case CMD_ownsyntax:
xp-xp_context = EXPAND_FILETYPE;
xp-xp_pattern = arg;
Since we now have filetype completion, why not add this to the
command-completion?
chrisbra t41:~/vim/src [1157]% hg diff ex_docmd.c ../runtime/doc/map.txt
diff -r 5bd81e397907 runtime/doc/map.txt
--- a/runtime/doc/map.txt Sun Jul 25 22:30:20 2010 +0200
+++ b/runtime/doc/map.txt Mon Jul 26 13:22:25 2010 +0200
@@ -1215,6 +1215,7 @@
-complete=mapping mapping name
-complete=menu menus
-complete=optionoptions
+ -complete=syntaxsyntax
-complete=tag tags
-complete=tag_listfiles tags, file names are shown when CTRL-D is hit
-complete=var user variables
diff -r 5bd81e397907 src/ex_docmd.c
--- a/src/ex_docmd.cSun Jul 25 22:30:20 2010 +0200
+++ b/src/ex_docmd.cMon Jul 26 13:22:25 2010 +0200
@@ -5280,6 +5280,7 @@
{EXPAND_MENUS, menu},
{EXPAND_SETTINGS, option},
{EXPAND_SHELLCMD, shellcmd},
+{EXPAND_FILETYPE, syntax},
#if defined(FEAT_SIGNS)
{EXPAND_SIGN, sign},
#endif
In the same way, we could also add compiler and colorscheme completion.
Is that useful?
regards,
Christian
--
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
Re: vim73brt+vim73bole can't run under windows 2000 sp4
Yue Wu wrote: I've downloaded vim73 beta(rt.zip+old.zip), after extract them and run gvim.exe, it warns: gvim is not a valid Win32 application. My OS is windows 2000 sp4. I have build the executable with the MSVC 2010 tools. The binary runs fine on my Windows XP system. But perhaps older systems are not supported by this compiler? I could go back to MSVC 2008, but I'm not sure all the 64 bit stuff works then. We defenitely want to support Windows 7 64bit, it's rapidly becoming wide spread. -- FROG: How you English say: I one more time, mac, I unclog my nose towards you, sons of a window-dresser, so, you think you could out-clever us French fellows with your silly knees-bent creeping about advancing behaviour. (blows a raspberry) I wave my private parts at your aunties, you brightly-coloured, mealy-templed, cranberry-smelling, electric donkey-bottom biters. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.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
Re: :command -complete bug?
Christian J. Robinson wrote: Perhaps I'm just not implementing my complete function properly, but when I try to define a new :command that uses a function for completion, I'm having it return a list with spaces in the list items escaped with a backslash. Nevertheless, when an argument with any escaped spaces is inserted into the command line, any further completion attempt passes ONLY the characters after the last space, even though it is escaped, to the first argument of my complete function. My explanation is probably unclear, but I can reproduce it by sourcing the attached file, typing :Foo and pressing tab (clear away the blank confirm dialog), then pressing backspace to delete the '1' and then pressing tab again. The confirm dialog shows only bar instead of foo\ bar/foo bar. Clearing away that confirm dialog shows foo\ foo\ bar1 on the command line. You also get the whole command line and the cursor position. You can use that to figure out the whole completion. Vim doesn't know that the thing being completed could continue before a space. -- Why is abbreviation such a long word? /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.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
Re: :command -complete bug?
On Mon, 26 Jul 2010, Bram Moolenaar wrote: Christian J. Robinson wrote: My explanation is probably unclear, but I can reproduce it by sourcing the attached file, typing :Foo and pressing tab (clear away the blank confirm dialog), then pressing backspace to delete the '1' and then pressing tab again. The confirm dialog shows only bar instead of foo\ bar/foo bar. Clearing away that confirm dialog shows foo\ foo\ bar1 on the command line. You also get the whole command line and the cursor position. You can use that to figure out the whole completion. Vim doesn't know that the thing being completed could continue before a space. But that doesn't work either. I can use the full command line to figure out the whole completion and return the possible completions, but Vim still inserts the new whole completion (with spaces) only in place of the text after the last space--it does not replace the entire text it should be replacing. Can I somehow tell Vim to replace the entire set of arguments after the command itself during completion? I really do think Vim should treat backslash-escaped spaces as being part of a greater single argument. As far as I can tell, as it is I have no way of effectively dealing with spaces in arguments during custom completion. Perhaps Vim could be altered to do it more like what I want if a command is defined with -nargs=? or -nargs=1 instead of -nargs=*? - Christian -- Christian J. Robinson hept...@gmail.com -- http://christianrobinson.name/ -- 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
Re: [bug] access to free memory with :redir command in Vim-7.2.466 and Vim-7.3b BETA
Dominique Pellé wrote:
$ cat use-free-mem.vim
let temp={}
redir = temp[0]
exe silent! ls
let temp={}
redir = temp[0]
exe silent! ls
$ valgrind --leak-check=yes vim -u NONE -S use-free-mem.vim
2/tmp/valgrind.log
Gives the following error in /tmp/valgrind.log:
...snip...
Script to reproduce the bug can be simplified further.
This is enough to reproduce the bug:
$ cat use-free-mem.vim
let temp={}
redir = temp[0]
let temp={}
redir END
$ valgrind --leak-check=yes vim -u NONE -S use-free-mem.vim 2/tmp/valgrind.log
The deletion of the dictionary, while doing a redir to a member of the
dictionary triggers the bug. I'm looking at the code but it's not simple
to understand.
-- Dominique
--
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
Re: [patch] added completion to the :setfiletype command.
Christian Brabandt wrote:
Hi Dominique!
On Sa, 24 Jul 2010, Dominique Pellé wrote:
Hi
Attached patch adds completion to the :setfiletype command.
Example:
:setf javaCTRL-D
javajavacc javascript
-- Dominique
diff -r 0c8219a26bc9 src/ex_docmd.c
--- a/src/ex_docmd.cSat Jul 24 20:57:44 2010 +0200
+++ b/src/ex_docmd.cSat Jul 24 23:36:07 2010 +0200
@@ -3829,6 +3829,7 @@
xp-xp_pattern = arg;
break;
+ case CMD_setfiletype:
case CMD_ownsyntax:
xp-xp_context = EXPAND_FILETYPE;
xp-xp_pattern = arg;
Since we now have filetype completion, why not add this to the
command-completion?
chrisbra t41:~/vim/src [1157]% hg diff ex_docmd.c ../runtime/doc/map.txt
diff -r 5bd81e397907 runtime/doc/map.txt
--- a/runtime/doc/map.txt Sun Jul 25 22:30:20 2010 +0200
+++ b/runtime/doc/map.txt Mon Jul 26 13:22:25 2010 +0200
@@ -1215,6 +1215,7 @@
-complete=mapping mapping name
-complete=menu menus
-complete=optionoptions
+ -complete=syntaxsyntax
-complete=tag tags
-complete=tag_listfiles tags, file names are shown when CTRL-D is hit
-complete=var user variables
diff -r 5bd81e397907 src/ex_docmd.c
--- a/src/ex_docmd.cSun Jul 25 22:30:20 2010 +0200
+++ b/src/ex_docmd.cMon Jul 26 13:22:25 2010 +0200
@@ -5280,6 +5280,7 @@
{EXPAND_MENUS, menu},
{EXPAND_SETTINGS, option},
{EXPAND_SHELLCMD, shellcmd},
+{EXPAND_FILETYPE, syntax},
#if defined(FEAT_SIGNS)
{EXPAND_SIGN, sign},
#endif
If this is completing filetypes, why call it syntax? I would find
filetype less confusing.
In the same way, we could also add compiler and colorscheme completion.
Is that useful?
Generally completion is useful. Note that I'm not going to include new
features now. But these tiny changes should be OK.
--
Communication is one of the most compli..., eh, well, it's hard.
You know what I mean. Not?
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.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
Question about :find completion support in Vim 7.3b
Hi, I am trying the new completion support for the :find command in Vim7.3b on MS-Windows (XP). The 'path' option is set to the default value (.,,). When I press Tab after typing :find , I expected that the filenames from the current directory will be completed. But none of the filenames are displayed. If I try to complete file names using ./ or .\, then the file names are displayed. Is this the expected behavior? - Yegappan -- 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
Re: Question about :find completion support in Vim 7.3b
On Tue, Jul 27, 2010 at 6:01 AM, Yegappan Lakshmanan yegapp...@gmail.com wrote: Hi, I am trying the new completion support for the :find command in Vim7.3b on MS-Windows (XP). The 'path' option is set to the default value (.,,). Thanks for trying out the :find completion feature on MS-Windows. When I press Tab after typing :find , I expected that the filenames from the current directory will be completed. But none of the filenames are displayed. If I try to complete file names using ./ or .\, then the file names are displayed. Is this the expected behavior? No this is a bug. It should behave as you expected. Does this happen on both console vim and gvim? Sadly I don't have a windows machine handy to reproduce this (maybe it's a blessing? :) Dimitar Dimitrov reported that the :find completion on Windows XP gvim crashes [1]. I'm working on refining the :find completion right now. I will post a new patch soon. nazri. [1] http://article.gmane.org/gmane.editors.vim.devel/27081 -- 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
tarPlugin.vim needs to be updated to handle xz files
In runtime file plugin/tarPlugin.vim, there are no lines for *.txz *.tar.xz which are needed to edit xz compressed tar archives. File plugin/gzip.vim handles *.xz, but tarPlugin.vim needs to be updated. The above is from Richard David Sherman who asked me to send it to vim_dev. Richard has limited computer access at the moment, so has not expanded on the above. Can someone please fill in the details and update the runtime for the 7.3 release. John -- 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
