>> 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
-~----------~----~----~----~------~----~------~--~---
