vim_use [email protected] http://groups.google.com/group/vim_use?hl=en
Today's most active topics: * i think this is a little bug of Vim - 8 new http://groups.google.com/group/vim_use/t/a5f794b837db92f1?hl=en * Using one buffer as "information screen" - 6 new http://groups.google.com/group/vim_use/t/f82c7aa2924749be?hl=en * Get grep results like ctrl-] - 3 new http://groups.google.com/group/vim_use/t/a58312edc529c2c0?hl=en * Syntax Highlighting for eZ Publish - 2 new http://groups.google.com/group/vim_use/t/b8e69e81848ad5ce?hl=en * errorformat help for compiler output - 2 new http://groups.google.com/group/vim_use/t/0e09fe5f72b17d40?hl=en Active Topics ------------- Using one buffer as "information screen" - 6 new ------------------------------------------------ I would like to set up my Vim so that I have two buffers visible, and as I am typing in one buffer the other buffer is showing information about the first buffer. What I specifically want to do is that each time I press Enter, the second buffer is updated to show all lines from the first buffer that matches ( in some way) the line I just - Sat, Nov 22 2008 2:00 am 6 messages , 5 authors http://groups.google.com/group/vim_use/t/f82c7aa2924749be?hl=en Get grep results like ctrl-] - 3 new ------------------------------------ Hi Vim users, I'm looking for a way to grep from inside vim. I'm aware of : grep command but I'm not satisfied with the way the results are handled: they are all loaded as "errors" like if I used a compiler. I would like the grep result to be displayed the same way as when I do Ctrl-], then I type the number of the hit, and it opens as a new buffer. - Sat, Nov 22 2008 3:52 am 3 messages , 3 authors http://groups.google.com/group/vim_use/t/a58312edc529c2c0?hl=en Syntax Highlighting for eZ Publish - 2 new ------------------------------------------ ...And nearby sections and hotlink destinations. And there are dozens of examples in the Vim runtime files. Ben. - Sat, Nov 22 2008 4:12 am 2 messages , 2 authors http://groups.google.com/group/vim_use/t/b8e69e81848ad5ce?hl=en CSApprox issue - 1 new ---------------------- Ok, I solved the problem. I remembered that yesterday I used Gnome for a while with a test user. So synaptic downloaded a lot of updates and there was also an update for rxvt-unicode. My rxvt was compiled from source, to support 256 colors, so I think this messed up everything. Now I removed rxvt-unicode and recompiled. Everything works. - Sat, Nov 22 2008 4:21 am 1 message, 1 author http://groups.google.com/group/vim_use/t/3ebe2562a1a9a664?hl=en how to sign the unmatched bracket? - 1 new ------------------------------------------ hi all. maybe you had notice that, if you write ")()" in your vimrc, you will find the first bracket turn to red to notice it's unmatched. it's made like this: syn region vimOperParen oneline matchgroup=vimOper start="(" end=")" contai...@vimopergroup syn match vimOperError ")" so, if you write )(), Vim will notice you the ')' is not matched. but - Sat, Nov 22 2008 8:11 am 1 message, 1 author http://groups.google.com/group/vim_use/t/37af55cae8580113?hl=en i think this is a little bug of Vim - 8 new ------------------------------------------- just open your Vim, input "asdf", press <ESC> return to normal mode, then, press'a' into insert mode and input "zxcv", then press Ctrl+W, you will find only "zxcv" are deleted, not include "asdf", i think it's a bug, because the doc of Vim said "See the section "word motions", for the definition of a word. ", it didn't mention "only - Sat, Nov 22 2008 11:09 am 8 messages , 4 authors http://groups.google.com/group/vim_use/t/a5f794b837db92f1?hl=en errorformat help for compiler output - 2 new -------------------------------------------- ...Yes, I had that originally but I didn't like how it did not encompass the entire message. Sorry, I should have mentioned that. Thank you for the response. Dave - Sat, Nov 22 2008 12:46 pm 2 messages , 1 author http://groups.google.com/group/vim_use/t/0e09fe5f72b17d40?hl=en Cursor become invisible. - 1 new -------------------------------- ...I have seen this problem, but have not yet reported it as a bug because I haven't got much information to go on. At work on my Fedora 7 machine with a self-compiled Vim 7.2.25, I see this problem when I run ``gvim -u NONE``, then set guifont to some font (it doesn't seem to matter which one), then create and immediately close a vertical split window (CTRL-W - Sat, Nov 22 2008 6:07 pm 1 message, 1 author http://groups.google.com/group/vim_use/t/3a735a0e2c526c6b?hl=en netrw cuts off first letter(s) of file - 1 new ---------------------------------------------- I am using Gvim version 7.2 on windows and have an occasional problem with Netrw. When I do :e . the output is sometimes missing the first letter of the file. Any ideas why or what to check? Kevin - Sat, Nov 22 2008 6:29 pm 1 message, 1 author http://groups.google.com/group/vim_use/t/2fe91677ce6233db?hl=en How to do this? - 1 new ----------------------- ...While regular expressions can do wonders, here is yet another way to solve your problem using VimL: let line = 1 while line < line('$') let fline = split( getline(line))[:2] let logfile = fnamemodify(fline[1], ":t:r") call setline( line, join(fline)) call setline((line + 1), 'logfile=./'.logfile.'.log '. getline((line + 1))) - Sun, Nov 23 2008 1:33 am 1 message, 1 author http://groups.google.com/group/vim_use/t/742d164c364f1d96?hl=en ============================================================================== You received this message because you are subscribed to the Google Groups "vim_use" group. To post to this group, send email to [email protected] or visit http://groups.google.com/group/vim_use?hl=en To unsubscribe from this group, send email to [email protected] To change the way you get mail from this group, visit: http://groups.google.com/group/vim_use/subscribe?hl=en To report abuse, send email explaining the problem to [email protected] ============================================================================== Google Groups: http://groups.google.com/?hl=en --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
