Remove the comments setting emands and vim tab width and expansion variables.

Remove the comments setting emands and vim tab width and expansion variables.

These were added in r28089 (http://codereview.chromium.org/256059) but
are unnecessary bloat for everyone to carry around, even those that don't
use emacs or vim.

In an earlier change, I added editor config files in src/tools/emacs/
and src/tools/vim/ so users of the appropriate editor can source those
instead.

BUG=none
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=92046

[tony, 2011-07-06 23:40:14]

I'm in no hurry to land this, so if you're on vacation, I can wait.

This is basically reverting http://codereview.chromium.org/256059.  To make the
transition easier, I added emacs and vim settings files in
src/tools/{emacs,vim}.

[Mark Mentovai, 2011-07-10 15:55:25]

http://codereview.chromium.org/7310019/diff/1/base/base.gyp
File base/base.gyp (right):

http://codereview.chromium.org/7310019/diff/1/base/base.gyp#newcode398
base/base.gyp:398: 
If you’re going to get rid of the trailing matter, you should get rid of the
blank line at the end of each file that currently precedes it too.

[sgk, 2011-07-11 15:47:09]

lgtm

[tony, 2011-07-11 18:16:20]

Take another look?

http://codereview.chromium.org/7310019/diff/1/base/base.gyp
File base/base.gyp (right):

http://codereview.chromium.org/7310019/diff/1/base/base.gyp#newcode398
base/base.gyp:398: 
On 2011/07/10 15:55:26, Mark Mentovai wrote:
> If you’re going to get rid of the trailing matter, you should get rid of the
> blank line at the end of each file that currently precedes it too.

Done.

[Mark Mentovai, 2011-07-11 18:17:20]

LGTM

[darin (slow to review), 2011-07-17 19:35:51]

> In an earlier change, I added editor config files in src/tools/emacs/ 
> and src/tools/vim/ so users of the appropriate editor can source those 
> instead.

The old system worked without me having to do anything.  The new system requires
me to know about those editor files.  How would I ever discover those?

[tony, 2011-07-18 16:07:32]

On 2011/07/17 19:35:51, darin wrote:
> > In an earlier change, I added editor config files in src/tools/emacs/ 
> > and src/tools/vim/ so users of the appropriate editor can source those 
> > instead.
> 
> The old system worked without me having to do anything.  The new system
requires
> me to know about those editor files.  How would I ever discover those?

The old system had the cost of confusing people during code reviews.
https://bugs.webkit.org/show_bug.cgi?id=62399#c9
https://bugs.webkit.org/show_bug.cgi?id=62399#c15

This seems to be more like how we handle configuration for other tools (like the
http://www.chromium.org/developers/how-tos/visualstudio-tricks page or tools/gdb
or tools/git).