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: Fri, 19 Feb 2016 21:43:51 +0100 Message-ID: <87vb5ke8hk.fsf@debian.uxu> References: <22213.39605.290751.139619@mail.eng.it> <20160218103019.GA5354@tuxteam.de> <20160218131722.GA10679@tuxteam.de> <20160218141544.GB11934@tuxteam.de> <87vb5lzgx3.fsf@debian.uxu> <878u2gwuvh.fsf@mbork.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1455914680 15353 80.91.229.3 (19 Feb 2016 20:44:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Feb 2016 20:44:40 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Feb 19 21:44:31 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 1aWrug-0006yD-3Q for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Feb 2016 21:44:30 +0100 Original-Received: from localhost ([::1]:55233 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWruf-0004fF-Hs for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Feb 2016 15:44:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47053) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWruF-0004Zb-Kv for help-gnu-emacs@gnu.org; Fri, 19 Feb 2016 15:44:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aWruC-0000O4-CZ for help-gnu-emacs@gnu.org; Fri, 19 Feb 2016 15:44:03 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:37056) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWruC-0000N0-6V for help-gnu-emacs@gnu.org; Fri, 19 Feb 2016 15:44:00 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aWru9-0006WA-I5 for help-gnu-emacs@gnu.org; Fri, 19 Feb 2016 21:43:57 +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 ; Fri, 19 Feb 2016 21:43:57 +0100 Original-Received: from embe8573 by nl106-137-54.student.uu.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 19 Feb 2016 21:43:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Original-Lines: 53 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:gAWJnFHaYzNpj+8kxHyxm1uP9mE= 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:109220 Archived-At: Marcin Borkowski writes: > Or do it automatically. Here, we only consider serious suggestions :) About 'binary search' being "sluggish", the algorithm itself isn't sluggish. Actually it is great when the outcome (the test or the search) is almost instantly extractable from any "length" of the material, *and* when the material is possible to divide arbitrarily. Here, the test is the existence of unwanted behavior and the material is Elisp code, so this is so, or almost so, because you can't cut the code in half entirely anywhere you want (e.g., it is not possible in the middle of a defun), but mostly, it should be possible to divide fairly freely as the code is probably either written "in sequence" (e.g., as single .emacs file) *or* if it is modular (e.g., the .emacs file is a bunch of `loads' of other files). Once again modular code makes life easier. Start Emacs with '-Q', confirm the unwanted isn't there, then bring up the "load" .emacs file: (load-file "file.elc-1") (load-file "file.elc-2") ... (load-file "file.elc-n") This makes it much easier to comment out and in code. Either do that the binary way (for a lot of files) or just evaluate file after file until the problem arises. What is "sluggish" about it is rather that you don't even attempt to make an educated guess where the problem is. But if you have absolutely no "education" to your guess, isn't that the right thing to do - not to do it? Well, yes and no. In isolation, it makes sense not doing something that isn't there. In the long run tho, making educated guesses is a skill just as any I'd say. Probably the sooner you start doing them, the better they get. -- underground experts united http://user.it.uu.se/~embe8573