Mark Waggoner wrote: > > There are two critical factors that make vimscript solutions undesirable: > > 1. This is NOT for entering text - it is for viewing/editing text that > already exists. So any mapping solutions aren't really useful. > > 2. I do not want spaces added to the file to create the alignment. > The description of the AutoAlign method sounds really close to > "working" if, before re-saving, I were to replace all the "spaces > followed by a tab" with a tab, (and maybe it already does this > automatically - I haven't tried). However, if there were a place > where some text was SUPPOSED to have a space before a tab, it would go > away. > > I did just try installing AutoAlign - but I get errors such as: > > E486: Pattern not found: ^(t*)(.*) > > when I try to use \tab on a range of lines. No doubt I am missing > something, but I don't have time to debug it right now.
Did you also get an up-to-date Align/AlignMaps plugin? The new Align plugin processes the input arguments itself, rather than depending on <f-args> processing; the reason is that <f-args> converts \x to x unless x is a \, in which case \\ -> \\, thereby making <f-args> difficult to use with regexp patterns (I submitted a patch providing <p-args> which is well-suited for pattern handling, but Bram didn't appear to care for it). The "Pattern not found:..." message sounds like the old <f-args> trick of removing the backslashes, so \t -> t. I didn't put a au BufWritePre * if &ft == "eltab"|%s/ *\t */\t/ge|endif into eltab/eltab.vim, but obviously it'd be easy to do. I didn't do so because its also easy to do manually, and I'm not certain that I should force it on users. However, its a new addition to AutoAlign, and is in beta, so this could change depending on what folks indicate should be there. Regards, Chip Campbell --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
