From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.help Subject: Re: removing white space highlight Date: Sun, 21 Feb 2016 12:48:46 +0100 Message-ID: <20160221114846.GA9348@tuxteam.de> References: <87egc6ltog.fsf@debian.uxu> <87vb5izqst.fsf@robertthorpeconsulting.com> <8760xiloy2.fsf@debian.uxu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed X-Trace: ger.gmane.org 1456057430 14621 80.91.229.3 (21 Feb 2016 12:23:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 21 Feb 2016 12:23:50 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Feb 21 13:23:49 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aXT3F-0002Wz-6k for geh-help-gnu-emacs@m.gmane.org; Sun, 21 Feb 2016 13:23:49 +0100 Original-Received: from localhost ([::1]:40465 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXT3E-0003Qf-Je for geh-help-gnu-emacs@m.gmane.org; Sun, 21 Feb 2016 07:23:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52371) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXT32-0003QT-Ll for help-gnu-emacs@gnu.org; Sun, 21 Feb 2016 07:23:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXT2z-0006sb-Fd for help-gnu-emacs@gnu.org; Sun, 21 Feb 2016 07:23:36 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]:41209 helo=tomasium.tuxteam.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXT2z-0006s1-9X for help-gnu-emacs@gnu.org; Sun, 21 Feb 2016 07:23:33 -0500 Original-Received: from tomas by tomasium.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1aXSVK-0002Vh-U3 for help-gnu-emacs@gnu.org; Sun, 21 Feb 2016 12:48:46 +0100 In-Reply-To: <8760xiloy2.fsf@debian.uxu> User-Agent: Mutt/1.5.21 (2010-09-15) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 5.199.139.25 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:109243 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Feb 21, 2016 at 04:31:01AM +0100, Emanuel Berg wrote: [...] > Yes, so why not have it automatized once and for all > and then never have to think about it? Because it's a very rude thing to do when working with others? If a (biggish) project has "whitespace issues", the sensible way of doing it is: - agree that it's an issue. Otherwise *do nothing*. Introducing whitespace diffs at this stage "because I thing it's the right thing, dammit" is arrogant and unpolite -- and might result on being scolded. Rightfully so. - agree on a strategy. It could be "whenever a file is touched for whatever reason (a) or in a orchestrated series of commits (b) - in case (a) it's still meaningful to dedicate one commit to the whitespace change itself - in case (b) it'd make sense to agree on some time frame. Of course, this wouldn't apply on a "clean" slate, where such tools are definitely a plus. Still I'd prefer an indication to a silent fix -- when fixing whitespaces in other's code, I'd *always* ask first. Working with others has its price. - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlbJpB4ACgkQBcgs9XrR2kaBKgCdEaQSE3VEzPr2c2IZV0ilA2pj +IoAn1NhPsvuKKR6GIWTLJ3obYUYLWwT =RiPF -----END PGP SIGNATURE-----