From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: When was a change installed? Date: Wed, 19 Aug 2015 14:18:07 -0400 Message-ID: References: <87lhd79a21.fsf@fencepost.gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: plane.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: ger.gmane.org 1440008379 19889 80.91.229.3 (19 Aug 2015 18:19:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Aug 2015 18:19:39 +0000 (UTC) Cc: schwab@suse.de, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 19 20:19:24 2015 Return-path: Envelope-to: ged-emacs-devel@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 1ZS7xL-0005pU-9L for ged-emacs-devel@m.gmane.org; Wed, 19 Aug 2015 20:19:23 +0200 Original-Received: from localhost ([::1]:59715 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZS7xK-0005rh-EU for ged-emacs-devel@m.gmane.org; Wed, 19 Aug 2015 14:19:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48545) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZS7wB-00057A-Ps for emacs-devel@gnu.org; Wed, 19 Aug 2015 14:18:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZS7wA-0000BT-Vo for emacs-devel@gnu.org; Wed, 19 Aug 2015 14:18:11 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32872) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZS7w8-0000Av-S0; Wed, 19 Aug 2015 14:18:08 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1ZS7w7-00020K-3D; Wed, 19 Aug 2015 14:18:07 -0400 In-reply-to: <87lhd79a21.fsf@fencepost.gnu.org> (message from David Kastrup on Wed, 19 Aug 2015 06:28:06 +0200) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:188966 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] I finally succeeded in running an Emacs from July 2014. (Work was required to make it run.) I was flabbergasted to find that it DID do the lax whitespace search. Has the feature been active for 3 years and I never noticed until now? It looks that way. I tried various cases and learned something that might explain why I didn't notice it. It seems that the feature applies only to SPC. Entering C-j matches only newline. That seems to explain why my searches for C-j C-j always worked as intended. Given that in lax matching SPC matches any sequence of whitespace, there is no sense in a lax SPC preceded or followed by another whitespace character. Thus I propose that SPC adjacent to some other whitespace character should match only a single space. In particular C-j SPC should match only newline space, and SPC SPC should match only space space. What do people think of that? Meanwhile, how about colorizing a space in the echo area when it is being searched for laxly? That should help users understand what is happening. -- Dr Richard Stallman President, Free Software Foundation (gnu.org, fsf.org) Internet Hall-of-Famer (internethalloffame.org) Skype: No way! See stallman.org/skype.html.