RE: [patch] Re: 7.3 unable to load ruby 1.9.2?
Jon wrote: any feedback from a core committer as to whether this patch is acceptable to be merged into default? Bram (see :help credits) is the Vim developer. It's an awkward time currently because Bram was super busy preparing the Vim 7.3 release over the last few weeks, so if there is no response now, I think it would be best to raise the matter again, starting from scratch, in say two weeks. 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
Re: [Suggestion]: Use different colors to make :dig output more readable
The script consists of two parts. One enables Unicode completion of either Unicode Codepoints or Unicode Names using Ctrl-X_Ctrl_U and the other part is using digraph completion using Ctrl-X_Ctrl_C (think of char). For the digraph completion, if you want a with acute you press a and afterwards Ctrl-X_Ctrl_C and the omnicompletion popup presents all glyphs, that are available using 'a' and any second character. (see also the help, that comes with the plugin) Thank you for pointing me to the right direction, Christian! I still don't understand the unicode part of the script, how to use effectively the '2-char-grep-of-unicode-list'. But the digraph part works. The problem was that C-XC-C mapping does not work in my vim 7.1 and that confused me. I remapped it to F2 and it started to work. It's much more comfortable than the full list od :dig command. Thank you for it! Milan -- 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: Possible bug: cchar not applied to region start token when cole=2
On Aug 25, 9:31 am, Vince Negri vne...@asl-control.co.uk wrote: From: Ben Fritz [mailto:fritzophre...@gmail.com] Forwarded from vim_use...potentially the changeset mentioned below missed a change or two. Chip Campbell noticed this, although in his case it turned out there was an easier way to do what he was trying to do. Nothing got missed out from the changeset, I think there is still a funny with specifying a cchar for concealends. I never imagined someone would want to do that (since cchar was for things like entity replacement.) Well, I suppose I don't really *need* this feature either. I have a plugin that provides something akin to rich text within Vim. It accomplishes the formatting with regions introduced by single- character tokens, which are concealed, either through normal syntax concealment methods, or (for versions that support it) with the 'conceal' feature. At one point, a user suggested it would be nice to have a mapping that made the tokens temporarily visible. When I saw how 'cole' could be varied dynamically to switch between total concealment and cchar representation, I thought I had found a nice way to accomplish this; however, it's really a minor feature, so I won't be devastated if you decide it's not worth fixing. If you don't fix it, however, I would suggest that the expected behavior be documented in the help; as it is now, I think a user would reasonably expect to see cchar on both ends of the region. More generally, I think he would expect for cchar to work the same for concealends as it does for conceal. At any rate, I'm very glad this excellent feature has made it into Vim proper. Thanks, Brett Stahlman Chip's original comment: A cchar with concealends seems to show up only on the right side, and the left side persistently shows [the default conceal character] Vince -- 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
doc fix for syntax.txt
The following patch fixes section number. diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt --- a/runtime/doc/syntax.txt +++ b/runtime/doc/syntax.txt @@ -4612,7 +4612,7 @@ When splitting the window, the new window will use the original syntax. == -16. Color xterms *xterm-color* *color-xterm* +17. Color xterms *xterm-color* *color-xterm* Most color xterms have only eight colors. If you don't get colors with the default setup, it should work with these lines in your .vimrc: -- Yukihiro Nakadaira - yukihiro.nakada...@gmail.com -- 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: Suggest ':TOhtml' to use 'fileencoding' rather than 'encoding' as default html charset
On Aug 25, 11:11 pm, JiaYanwei jia...@126.com wrote: e.g. If the system/vim encoding is 'UTF-8', but a text file encoding is 'latin-1'. If the default HTML charset is 'encoding', after ':TOhtml', we should change the HTML charset to 'iso-8859-1', or save the generated HTML file by ':w ++enc=utf-8'. Hmm...unless I understand correctly, the sequence is: Load text file. File encoding is latin-1, Vim encoding is utf-8. Do :TOhtml to create a new html buffer. File encoding defaults to empty, Vim encoding is still utf-8. :TOhtml sees encoding and sets the charset in the generated markup to UTF-8. :w the new html buffer. Vim sees empty file encoding, so uses utf-8 as the new file's encoding. Thus file encoding matches the html charset. You claim that the new html buffer has latin-1 encoding. Am I missing something here? I still think using fileencoding might be the correct way to do it, but doing so would require 2html.vim to set the file encoding of the new html buffer explicitly to be equal to the source file. This also brings up another shortcoming of 2html, because using g:html_use_encoding may change the html charset meta tag, but it does NOT change the actual character encoding of the file. It looks like I will need to set the fileencoding of the new html buffer to whatever corresponds to the supplied user option as a separate fix. Any thoughts? -- 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
make -f make_cyg.mak with vim 7.3
Hello! I usually build vim myself with cygwin + make -f make_cyg.mak . However, I'm getting a message gcc: The -mno_cygwin flag has been removed; use a mingw targeted cross-compiler. on the first file it tries to compile (blowfish.o), and, sad to say, no gvim.exe . Regards, Chip Campbell -- 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: make -f make_cyg.mak with vim 7.3
Charles E Campbell Jr wrote: Charles E Campbell Jr wrote: Hello! I usually build vim myself with cygwin + make -f make_cyg.mak . However, I'm getting a message gcc: The -mno_cygwin flag has been removed; use a mingw targeted cross-compiler. on the first file it tries to compile (blowfish.o), and, sad to say, no gvim.exe . I read in make_cyg.mak a suggestion to try make_ming.mak, so here's my try: errors about no definition for _MAX_PATH. I added _MAX_PATH=1024 to DEFINES. Next problem: conflicting types for gettimeofday (main.c:3326 vs time.h:74). Interim solution: #if 0 ... #endif around gettimeofday in main.c . Of course, I don't know yet if it'll link. Next problem: netbeans.c:204 storage size of 'server' isn't known . There are more errors, too; attempting disabling netbeans. Next problem: xxd still uses Make_cyg.mak, which in turn complains about -mno_cygwin. Next problem: lots of undefined references. Here's my list of undefined references: (attempted to build gvim.exe) gobj/os_win32.o:os_win32.c:(.text+0x43c): undefined reference to `_wcsicmp' gobj/os_win32.o:os_win32.c:(.text+0x617): undefined reference to `__wfopen' gobj/os_win32.o:os_win32.c:(.text+0x6b5): undefined reference to `__wopen' gobj/os_mswin.o:os_mswin.c:(.text+0x913): undefined reference to `_IID_IPersistFile' gobj/os_mswin.o:os_mswin.c:(.text+0x20af): undefined reference to `__wstat' gobj/os_mswin.o:os_mswin.c:(.text+0x2178): undefined reference to `__wchdir' gobj/os_mswin.o:os_mswin.c:(.text+0x2b83): undefined reference to `__wfullpath' gobj/if_cscope.o:if_cscope.c:(.text+0x1e37): undefined reference to `__open_osfhandle' gobj/if_cscope.o:if_cscope.c:(.text+0x1e7c): undefined reference to `__open_osfhandle' collect2: ld returned 1 exit status make: *** [gvim.exe] Error 1 -- 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: make -f make_cyg.mak with vim 7.3
On 27/08/2010 8:37 PM, Charles E Campbell Jr wrote: Charles E Campbell Jr wrote: Hello! I usually build vim myself with cygwin + make -f make_cyg.mak . However, I'm getting a message gcc: The -mno_cygwin flag has been removed; use a mingw targeted cross-compiler. You need the MinGW compiler tool chain available from the Cygwin installer to support the '-mno-cygwin' option. on the first file it tries to compile (blowfish.o), and, sad to say, no gvim.exe . I read in make_cyg.mak a suggestion to try make_ming.mak, so here's my try: This may work, but again, you would need to use a MinGW compiler, by default 'gcc' would be the native Cygwin compiler. errors about no definition for _MAX_PATH. I added _MAX_PATH=1024 to DEFINES. _MAX_PATH in Windows is 260. Next problem: conflicting types for gettimeofday (main.c:3326 vs time.h:74). Interim solution: #if 0 ... #endif around gettimeofday in main.c . Of course, I don't know yet if it'll link. Next problem: netbeans.c:204 storage size of 'server' isn't known . There are more errors, too; attempting disabling netbeans. Next problem: xxd still uses Make_cyg.mak, which in turn complains about -mno_cygwin. Next problem: lots of undefined references. I suspect this is a result of using the native Cygwin compiler with the MinGW Makefile. Chris -- 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: make -f make_cyg.mak with vim 7.3
On Fri, 27 Aug 2010, Charles E Campbell Jr wrote: gcc: The -mno_cygwin flag has been removed; use a mingw targeted cross-compiler. on the first file it tries to compile (blowfish.o), and, sad to say, no gvim.exe . I had to edit Make_cyg.mak to use gcc-3 instead of just gcc, plus add -L/lib/w32api to EXTRA_LIBS. I mentioned this on this list during the 7.3 development, and Bram added this to the commentary at the top of Make_cyg.mak. I had to tweak GvimExt/Make_ming.mak more extensively, which is called by Make_cyg.mak. As far as I can tell, Cygwin doesn't come with MinGW. It has some MinGW stuff, but I can't find an actual MinGW compiler. - 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
