From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: removing white space highlight Date: Mon, 29 Feb 2016 01:52:11 +0100 Message-ID: <871t7wnxs4.fsf@debian.uxu> References: <877fhph7vu.fsf@debian.uxu> <87povgvh8v.fsf@robertthorpeconsulting.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1456707170 14272 80.91.229.3 (29 Feb 2016 00:52:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Feb 2016 00:52: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 Mon Feb 29 01:52:41 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 1aaC4n-0002ot-3m for geh-help-gnu-emacs@m.gmane.org; Mon, 29 Feb 2016 01:52:41 +0100 Original-Received: from localhost ([::1]:33158 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaC4m-0003Gg-I2 for geh-help-gnu-emacs@m.gmane.org; Sun, 28 Feb 2016 19:52:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaC4X-0003G6-8B for help-gnu-emacs@gnu.org; Sun, 28 Feb 2016 19:52:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaC4R-0000aL-OR for help-gnu-emacs@gnu.org; Sun, 28 Feb 2016 19:52:25 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:53649) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaC4R-0000Zk-HG for help-gnu-emacs@gnu.org; Sun, 28 Feb 2016 19:52:19 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aaC4P-0002fe-Uw for help-gnu-emacs@gnu.org; Mon, 29 Feb 2016 01:52:17 +0100 Original-Received: from nl106-137-54.student.uu.se ([130.243.137.54]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Feb 2016 01:52:17 +0100 Original-Received: from embe8573 by nl106-137-54.student.uu.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Feb 2016 01:52:17 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Original-Lines: 55 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: nl106-137-54.student.uu.se Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Cancel-Lock: sha1:RrAUOJTXI2EEenbdOXWPdg877q4= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:109361 Archived-At: Robert Thorpe writes: > Every line that has whitespace removed is flagged as > modified. It's added to the repository with my name, > date and a new revision number. So, the problem I've > described still occurs. The improvement is that the code gets cleaned up. Which has to be done once, then invisible-to-everyone automatization makes sure no more trailing whitespace can ever be added. > After a long time (maybe a decade), the vast > majority of lines in all the files would have been > changed. After that the problem wouldn't arise > again, but it's a very high price to pay. This is completely free of charge with no penalty to it whatsoever. Today, if done to the entire project, the code will look better. Tomorrow, if automatization is added, the problem will be gone forever and can by definition not re-enter the project nor any other projects with the same technology at work. > In a large project, are you going to tell people > that they can't use front-ends to version-control? > > Let's say, for example, that Vim doesn't support > those switches. Are you going to say "I'm sorry Vim > users, you have to use command line svn." It shouldn't be put on the level of the "client"/editor/singular user. It should be put on the "server" or most centralized level which holds the answer to the question "what are the current files for project P version XYZ?". Before anything enters there, cleaning is automatically done, but not logged (well, not logged as normal edits are anyway) - then, when people get the most recent files (i.e., the files that are exactly P:XYZ), people always get clean files. And they can't mess them up even if they try because such edits are silently ignored and discarded... The theoretical reason why this is possible and easy is that nobody (human nor machine) has any interest in or benefits from trailing whitespace. It is just a matter of automatically dealing with a bunch of data, a transformation from one state to another, where everything is very straightforward. -- underground experts united http://user.it.uu.se/~embe8573