Hi,
I noticed while editing gcc files, that there are a lot of *useless*
whitespaces at the end of lines or within empty lines, which are getting
automatic removed by some *smarter* editors as I am common to use *sigh*.
This leads to huge diff files and the real change is getting veiled. I
Kai Tietz wrote:
Hi,
I noticed while editing gcc files, that there are a lot of *useless*
whitespaces at the end of lines or within empty lines, which are getting
automatic removed by some *smarter* editors as I am common to use *sigh*.
This leads to huge diff files and the real change is
I noticed while editing gcc files, that there are a lot of *useless*
whitespaces at the end of lines or within empty lines, which are getting
automatic removed by some *smarter* editors as I am common to use *sigh*.
This leads to huge diff files and the real change is getting veiled. I
It also forbids embedded horizontal tabs for similar reasons (avoiding
junk difs).
That would be a problem with GCC, due to emacs being so heavily used,
but a similar convention *requiring* horizontal tabs would solve the
issue in question.
Thanks, that is what I want to hear. May it would be good point to run
over the source to be as the GNAT standard demands ?
Regards,
i.A. Kai Tietz
[EMAIL PROTECTED] (Richard Kenner) writes:
It also forbids embedded horizontal tabs for similar reasons (avoiding
junk difs).
That would be a problem with GCC, due to emacs being so heavily used,
but a similar convention *requiring* horizontal tabs would solve the
issue in question.
Emacs
Sergei Organov wrote:
Emacs could be configured either way:
(setq-default indent-tabs-mode nil)
If that is to become a policy, simply append:
// Local Variables:
// whitespace-global-mode
// indent-tabs-mode:t
// tab-width:8
// c-basic-offset:4
// End:
At the end of each file. This way,
more potential conflicts between the trunk and the branch and makes
^^ branches