> $ only denotes end-of-line if used....

I tested that macro and it seems to work as expected
I also tested taking out the $ and that works too
I agree that the $ should not be in there

> Why should Vim keep spaces in otherwise empty lines on indenting? Should
> it also *add* spaces in such lines if the preceding is shifted to the
> right?

I see now that it isn't an issue with the core of Vim itself.  The
tabbing would be dependent on the language (not to mention the
programmer's preferences).  So perhaps it is possible to edit the
indent/php.vim to get the behavior I want.


> I can conceive of no advantage to adding these extra bytes to the
> file.  It's not uncommon for large projects to have coding guidelines
> that mandate that there be no trailing spaces whatsoever.  What
> advantage would the extra spaces give?  Why do you want them?

When I first started coding with Vim, I found it annoying that on one
of these lines with no tabs on it, I would have to go into insert mode
and then tab over then start editing.  That is, until I found that I
could hit S to begin editing and it would do the tabbing for me and I
could start editing right away.  So now I don't mind that there are no
tabs on those lines.

The problem is that I'm not the only one editing our files, but I'm
the only one using Vim.  So everyone else has to add tabs to the lines
to start editing them.  So it is to be a convenience to the others
editing these files with Eclipse, Xcode, Notepad++, etc...



Last note: I do appreciate the input and help here.  Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to