Re: use the position of a word as an argument in SR
Hi, Jeri Raye wrote: Can you use the position of a word in a search and replace as an argument For example if the line has the word INPUT in it, then the last word should have () around it So: start: INPUT s1 , s2 INPUT s3 , s4 must become start: INPUT s1 , (s2) INPUT s3 , (s4) g/\INPUT\/s/\(.*\)\(\\w\+\\)/\1(\2)/ or g/\INPUT\/s/.*\zs\(\\w\+\\)/(\1)/ do this. The :global-command restricts the following substitution to lines containing the word INPUT. The :substitute-commands first try to match as many characters as possible in a line, but then they backtrack to be able to match the right-most single word. The first command then replaces everything that was matched with the part before the word and the word itself in parentheses. The second command uses \zs to reset the start of the match and replaces only the word with itself in parentheses. Regards, Jürgen -- Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. (Calvin) --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: :global problem [bug confirmed?]
Anybody have anything more on this? Bram? Is it really a bug? On Sun, Jul 5, 2009 at 5:14 PM, Efraim Yawitz efraim.yaw...@gmail.comwrote: A little debugging revealed that this behavior is according to design (but not as described in the help). In ex_cmds.h the :insert command is configured as: EX(CMD_insert,insert,ex_append, BANG|RANGE|TRLBAR|CMDWIN|MODIFY), without the EXTRA bit set which is defined as: #define EXTRA0x004/* allow extra args after command name */ :insert (and :append) do not allow any arguments. The only question is, was this always this way, and what is the correct behavior? --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: vim folding for xml brackets
On Jul 4, 2:46 pm, Russell Urquhart russurquha...@verizon.net wrote: I think i figured this out. The xfa command assumes the closing '' is across a line boundary. As i am on an opening '' the closing one is within the same line, so nothing happens. So, i guess my question then would be, is there a way to collapse xml elements at a certain level, e.g. all siblings within a given element? Thanks, Russ On Sat, Jul 04, 2009 at 12:08:01PM -0500, Russell Urquhart wrote: Hi again, Thanks for the help on the selecting the contents of an xml element! One more question. In the Vim recipes book, it alludes to a xfa B command (where B is the bracket of choice) to control folding within the document. I'm pretty sure i have folding supported, as it works on selected text, but i can't seem to get this command to work, or find much info on it. Am i doing something wrong? Thanks, Russ- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: :global problem [bug confirmed?]
This works for me: :g/abc/inser...@line1\^@Line2 where ^@ is one character inserted with CTRL-V_CTRL-J or CTRL-K_N_U etc. Right, that works fine, but is that what the help means? The help _does_ seem to suggest that one can type 1) colon 2) g 3) slash 4) regexp 5) slash 6) i[nsert] 7) backslash 8) enter (instead of CTRL-V_CTRL-J or CTRL-K_N_U) 9) (continue adding your text to insert) However step #8 errors out in the way mentioned by the OP before it allows you to finish the insertion command. The unintuitive solution would be to change the help to detail Andy's findings. However, I think a better solution would involve making the terminal-backslash treat the newline as the null character and continue accepting input as the :insert command normally does. This would align with how I read the help and be more intuitive. Separate lines with a NL escaped with a backslash Confusion is compounded in the help by the use of the text NL which can ambiguously be expanded as either New-line (ASCII 0x0a) or Null (ASCII 0x00). Both :help NL and :help c_nl take you to places where enter is being hit, not the null ^@ internal EOL character is documented (:help NL-used-for-Nul). Just MHO. -tim --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: :global problem [bug confirmed?]
Efraim Yawitz schrieb: On Mon, Jul 6, 2009 at 5:46 PM, Andy Wokula anw...@yahoo.de wrote: This works for me: :g/abc/inser...@line1\^@Line2 where ^@ is one character inserted with CTRL-V_CTRL-J or CTRL-K_N_U etc. Right, that works fine, but is that what the help means? I'm not sure, but it looks like a bug -- the NL is confusing and readability is gone. see also Tim's post ... And to make it work within a script, a different notation is required: :exec g/abc/insert\\\nLine1\\\nLine2 Anyway: :insert is an old Vi thing -- as help states, it can also confuse :if statements etc, so I'd only use it in very simple situations. -- Andy --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
Saluton r...@verizon.net :) r...@verizon.net dixit: My xml files are of a form: userDoc GenSection ... /GenSection /userDoc When i did the syntax folding on a sample, albeit large (1.8 Mb) xml file, the closing /userDoc tag seems to be folded in the GenSection fold. Everything, however, works when i try this on a smaller sample file. Is there something about the xml syntax file that might explain this? Blind shot, from :help syntax: :syntax sync fromstart :syntax syng minlines=number big enough The second line may result in very slow redrawing and highlighting, I haven't tested it. I swear I saw once an option to fix this kind of things, but I cannot remember. Looks like Charles Campbell has updated the conversation while I was replying, so he may be of help. -- Raúl DervishD Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
Raúl Núñez de Arenas Coronado wrote: Saluton r...@verizon.net :) r...@verizon.net dixit: My xml files are of a form: userDoc GenSection ... /GenSection /userDoc When i did the syntax folding on a sample, albeit large (1.8 Mb) xml file, the closing /userDoc tag seems to be folded in the GenSection fold. Everything, however, works when i try this on a smaller sample file. Is there something about the xml syntax file that might explain this? Blind shot, from :help syntax: :syntax sync fromstart :syntax syng minlines=number big enough The second line may result in very slow redrawing and highlighting, I haven't tested it. I swear I saw once an option to fix this kind of things, but I cannot remember. Looks like Charles Campbell has updated the conversation while I was replying, so he may be of help. Hello! Essentially Raúl Núñez de Arenas Coronado's help is referring to the same solution as my succinct one (although that syn syng... was also meant to be syn sync ...). Both of these solutions are slower than the default synchronization; syn sync fromstart will likely always be the slowest or, at best, equal to the other. The simple reason: it causes syntax checking for all lines. This method yields the most correct synchronization at the price of a certain lack of speed. Regards, Chip Campbell --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Re: Problem with xml syntax folding?
Looking at this, and trying both :syntax sync fromstart and:syntax sync minilines=61000(the number of lines in the file. That should be enough, right?)No change? After i did these commands, i did a :e to get the syntax folding restarted. (That was the right thing to do, right?)Thanks,RussJul 6, 2009 05:59:25 PM, vim_use@googlegroups.com wrote:Saluton r...@verizon.net :)r...@verizon.net dixit: My xml files are of a form: ... When i did the syntax folding on a sample, albeit large (1.8 Mb) xml file, the closing tag seems to be folded in the fold. Everything, however, works when i try this on a smaller sample file. Is there something about the xml syntax file that might explain this?Blind shot, from ":help syntax"::syntax sync fromstart:syntax syng minlines=The second line may result in very slow redrawing and highlighting, Ihaven't tested it.I swear I saw once an option to fix this kind of things, but I cannotremember. Looks like Charles Campbell has updated the conversation whileI was replying, so he may be of help.-- Raúl "DervishD" Núñez de Arenas CoronadoLinux Registered User 88736 | http://www.dervishd.netIt's my PC and I'll cry if I want to... RAmen! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: How to make SR not report an error when search item isn't found
map F4 :%s/\RET\/RETURN/gCR \:%s/\RETI\/RETURNI/gCR \:%s/\ADDC\/ADDCY/gCR \:%s/\SUBC\/SUBCY/gCR It does several SR. But when it doesn't find something it gives an E486: Pattern not found. Why? How can I make it so that it doesn't give an error when it doens't find one of the given search items? Just add the e flag to the replacement: %s/foo/bar/ge as detailed on :help :s_flags -tim --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: How to make SR not report an error when search item isn't found
Hi Jeri! On Mo, 06 Jul 2009, Jeri Raye wrote: map F4 :%s/\RET\/RETURN/gCR \:%s/\RETI\/RETURNI/gCR \:%s/\ADDC\/ADDCY/gCR \:%s/\SUBC\/SUBCY/gCR […] How can I make it so that it doesn't give an error when it doens't find one of the given search items? Add the e flag (see :h :s_flags) to each s-command. regards, Christian -- :wq! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
Saluton Charles :) Charles Campbell c...@nasa.gov dixit: Raúl Núñez de Arenas Coronado wrote: Blind shot, from :help syntax: :syntax sync fromstart :syntax syng minlines=number big enough Essentially Raúl Núñez de Arenas Coronado's Not even I would wrote my full name, way too tiring for the fingers XD help is referring to the same solution as my succinct one (although that syn syng... was also meant to be syn sync ...). Oops! Thanks for pointing :))) Both of these solutions are slower than the default synchronization; syn sync fromstart will likely always be the slowest or, at best, equal to the other. The simple reason: it causes syntax checking for all lines. This method yields the most correct synchronization at the price of a certain lack of speed. The problem I see with :syn sync minlines is that with very big files (and the OP was talking about a file that was almost 2MB) is very difficult to find the correct value for minlines. If one has to work a lot on that file, probably finding a proper value for minlines is worth the effort. Otherwise I would use fromstart, although it is kind of an exaggeration. On the other hand, knowing the number of lines in the file is more or less easy to make an educated guess about the proper value for minlines, which is going to be better in performance terms. -- Raúl DervishD Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Re: Problem with xml syntax folding?
Saluton r...@verizon.net :) r...@verizon.net dixit: Looking at this, and trying both :syntax sync fromstart and :syntax sync minilines=61000 (the number of lines in the file. That should be enough, right?) No change? Then I'm lost, sorry O:) -- Raúl DervishD Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
Hi Raúl! On Mo, 06 Jul 2009, Raúl Núñez de Arenas Coronado wrote: I swear I saw once an option to fix this kind of things, but I cannot remember. Looks like Charles Campbell has updated the conversation while I was replying, so he may be of help. :h 'synmaxcol' regards, Christian -- :wq! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Howto run gcc and have vim re-edit buff and show errs by line
Ben Fritz wrote: :help quickfix Read the whole help file, but specifically, within this file: :help :make :help :copen :help :cnext --- That was it! Thanks! linda --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Re: Problem with xml syntax folding?
That did it! I set synmaxcol=0 and now everything seems to work properly.I was thinking there might be an issue as in several LONG lines of a Code element, the syntax coloring was getting confused.Thanks againRussJul 6, 2009 07:14:01 PM, vim_use@googlegroups.com wrote:Hi Raúl!On Mo, 06 Jul 2009, Raúl Núñez de Arenas Coronado wrote: I swear I saw once an option to fix this kind of things, but I cannot remember. Looks like Charles Campbell has updated the conversation while I was replying, so he may be of help.:h 'synmaxcol'regards,Christian-- :wq! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
Raúl Núñez de Arenas Coronado wrote: Saluton Charles :) Charles Campbell c...@nasa.gov dixit: Raúl Núñez de Arenas Coronado wrote: Blind shot, from :help syntax: :syntax sync fromstart :syntax syng minlines=number big enough Essentially Raúl Núñez de Arenas Coronado's Not even I would wrote my full name, way too tiring for the fingers XD Saluton! :) Actually, I used the mouse. Also, not being familiar with all the cultures represented here, I figure its safer just to re-use someone's name as they themselves have used it, especially if I can just lift the name via the mouse. I think I forgot some accent once and that changed the gender associated with the name, and got someone slightly upset with me. Best wishes, Chip Campbell --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
On Jul 6, 2:32 pm, russurquha...@verizon.net wrote: That did it! I set synmaxcol=0 and now everything seems to work properly. I was thinking there might be an issue as in several LONG lines of a Code element, the syntax coloring was getting confused. Thanks again I'm glad we were able to help you, Russ. In the future, please bottom-post, and use plaintext rather than html in your email format, according to list guidelines: http://groups.google.com/group/vim_use/web/vim-information --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: FW: Compiling 7.2 on Solaris 10
On 02/07/09 21:34, David Lehmann wrote: Hello, After untarring the vim7.2 package and running configure, I get the following error on Solaris 10. Can anyone help? Thanks. % make CC=gcc -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/openwin/include -I/usr/sfw/include -I/usr/sfw/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/openwin/include srcdir=. sh ./osdef.sh gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/openwin/include -I/usr/sfw/include -I/usr/sfw/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -I/usr/openwin/include -o objects/buffer.o buffer.c In file included from buffer.c:28: vim.h:41: error: syntax error before ':' token make: *** [objects/buffer.o] Error 1 -- *David * vim.h line 41 is the last line but one of the following: /* the header file puzzle (ca. 50-100 pieces) = */ #ifdef HAVE_CONFIG_H /* GNU autoconf (or something else) was here */ # include auto/config.h # define HAVE_PATHDEF /* * Check if configure correctly managed to find sizeof(int). If this failed, * it becomes zero. This is likely a problem of not being able to run the * test program. Other items from configure may also be wrong then! */ # if (SIZEOF_INT == 0) Error: configure did not run properly. Check auto/config.log. # endif So I recommend that you: 1) check my HowTo page, http://users.skynet.be/antoine.mechelynck/vim/compunix.htm 2) make sure that you have all required development packages for any libraries that your Vim will use 3) set your configure arguments as the values of _environment variables_ as shown in the above-mentioned HowTo 4) run make reconfig (or, maybe better, make reconfig 21 |tee reconfig.log) in the top-level directory (the vim72 directory containing src/ runtime/ etc.). This way, even if make runs configure again (it may happens, especially if there are patches for the makefile dependencies, in which case make will rebuild its makefiles then restart) your configure settings won't get lost. If it goes wrong again, check the output of the configure phase, which comes before what you quoted. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 64. The remote to the T.V. is missing...and you don't even care. --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: File info disappears in vim status line after startup from command line
On 03/07/09 08:11, bgold12 wrote: I've found that when I type gvim a from the command line, I get a message in the status line after gvim has started up that gives some info about the file a. For example, if the file doesn't exist, it says a [New File]; if the file does exist but is empty, it says a 0L, 0C. This is a very nice feature, but it doesn't seem to work with vim (as opposed to gvim). From what I can tell, the message IS displayed with vim, but it disappears after a fraction of a second. I know I can get similar info by typing CTRL-G, but obviously it would be better if I didn't have to do that every time I open a file. So, is this a bug in vim, or a problem with my settings, and if the latter, how can I fix this? If it's important, I'm running Windows XP, vim 7.2, and I'm using cygwin (bash) as my command line. Thanks, Ben As you remarked, the message appears, but it gets overwritten. However, you can get it back by means of the |:messages| command. One possible way to make messages stay longer at the bottom of the Vim screen is to add the following snippet to your vimrc: if cmdheight 2 set cmdheight=2 endif This will make sure that you have at least one extra line for messages at the bottom. It may not always work, but you still have :messages available if Vim talks too fast. Note that Vim-for-Windows is a Windows-like (or Dos-like) program, while bash is a Unix-like program. If you run them together, you can run into problems if the differences between them (path notation, for instance) make them run at cross-purposes. I recommend using [g]vim for Windows from desktop icons or from the cmd.exe shell (the Dos Box), or Console Vim for Cygwin from Cygwin bash, thus keeping Dos with Dos and Cygwin with Cygwin. I don't recommend using gvim for Cygwin at all, unless you want to take the trouble of running a Cygwin X server. Best regards, Tony. -- It's lucky you're going so slowly, because you're going in the wrong direction. --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: File info disappears in vim status line after startup from command line
On Thu, Jul 2, 2009 at 11:11 PM, bgold12 bgol...@gmail.com wrote: I've found that when I type gvim a from the command line, I get a message in the status line after gvim has started up that gives some info about the file a. For example, if the file doesn't exist, it says a [New File]; if the file does exist but is empty, it says a 0L, 0C. This is a very nice feature, but it doesn't seem to work with vim (as opposed to gvim). From what I can tell, the message IS displayed with vim, but it disappears after a fraction of a second. Try adding set laststatus=2 to your _vimrc file. This will force display of the status line in every window. You might also want to check help on 'statusline'. There are LOTS more things that can be displayed at the bottom of each window. -- Jay --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: .vimrc for Solaris 10 and vim 7.2
On 04/07/09 22:17, Matt Wozniski wrote: [...] I believe this is the first time you mentioned that you were using the console, and not a GUI. :) But, that said - note that the console is still considered a terminal emulator; pretty much anything but a *real* vt220 teletype is. Many have never seen a non-emulated terminal except in pictures, myself included. [...] What about the console used at boot time to pass parameters to the kernel? Its only drivers are in ROM, and it's always in QWERTY, which is annoying if (like mine) your keyboard has its keys labeled differently (mine is AZERTY but I shudder when thinking of Dvorak). The console used by Ms-Dos wasn't much emulated except that it usually did have a software keyboard driver. And then there was the tty35 on the mainframe of my first job (1970) which was definitely unemulated (and could type exactly 64 different characters including the space). But I didn't own it of course, the company did (or was that computer leased? I never knew the details.). Best regards, Tony. -- A consultant is a person who borrows your watch, tells you what time it is, pockets the watch, and sends you a bill for it. --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Problem with xml syntax folding?
Saluton Christian :) Christian Brabandt c...@256bit.org dixit: On Mo, 06 Jul 2009, Raúl Núñez de Arenas Coronado wrote: I swear I saw once an option to fix this kind of things, but I cannot remember. Looks like Charles Campbell has updated the conversation while I was replying, so he may be of help. :h 'synmaxcol' That is! Thanks a lot for pointing it :) -- Raúl DervishD Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~-~--~~~---~--~~ You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
