forked from osmocom/wireshark
Remove a phrase which implies that tab widths other than 8 are OK.
svn path=/trunk/; revision=53030
This commit is contained in:
parent
02f2b76bdd
commit
2a69c2d05c
|
@ -687,7 +687,7 @@ trying to keep things consistent for other developers.
|
|||
|
||||
5. White space convention.
|
||||
|
||||
Avoid using tab expansions different from 8 column widths, as not all
|
||||
Please avoid using tab expansions different from 8 column widths, as not all
|
||||
text editors in use by the developers support this. For a detailed
|
||||
discussion of tabs, spaces, and indentation, see
|
||||
|
||||
|
@ -696,9 +696,9 @@ discussion of tabs, spaces, and indentation, see
|
|||
When creating a new file, you are free to choose an indentation logic.
|
||||
Most of the files in Wireshark tend to use 2-space or 4-space
|
||||
indentation. You are encouraged to write a short comment on the
|
||||
indentation logic at the beginning of this new file, especially if
|
||||
you're using non-mod-8 tabs. The tabs-vs-spaces document above provides
|
||||
examples of Emacs and vi modelines for this purpose.
|
||||
indentation logic at the beginning of this new files. The
|
||||
tabs-vs-spaces document above provides examples of Emacs and vi
|
||||
modelines for this purpose.
|
||||
|
||||
Please do not leave trailing whitespace (spaces/tabs) on lines.
|
||||
|
||||
|
|
Loading…
Reference in New Issue