X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.6 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
Message-ID:	<4AFD7BAB.2000007@cs.umass.edu>
Date:	Fri, 13 Nov 2009 10:30:51 -0500
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
User-Agent:	Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: emacs 23.1.1 macro behavior and name completion
References:	<3185EFAF9C8F7B4E9DBDF56829BF7C7807266E AT srv060ex01 DOT ssd DOT fsi DOT com> <4AFD790C DOT 2010009 AT cornell DOT edu>
In-Reply-To:	<4AFD790C.2010009@cornell.edu>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Ken Brown wrote:
> On 11/13/2009 9:57 AM, Rockefeller, Harry wrote:
>> Emacs 23.1.1 (Cygwin 1.7) stores spaces literally inside emacs macros
>> instead of using the space as a name completion command. In the
>> older emacs (Cygwin 1.5) this is not the case. The stored macro
>> behaved exactly like the keystrokes were originally typed
>> interactively. Is this a "feature" of the new emacs? Does this emacs
>> version do the same thing on a native Linux PC? i.e., does this have
>  > anything to do with Cygwin itself?
> 
> This almost certainly has nothing to do with cygwin.  There have been 
> many changes in emacs since version 21 (which you were using before), 
> including changes in how completion is done and changes involving 
> keyboard macros.  Use the help and info facilities within emacs, or 
> browse the NEWS files in /usr/share/emacs/23.1/etc/.  Further questions 
> on this should go to one of the emacs lists unless you find evidence 
> that the issue is related to cygwin.
> 
> Ken

However! Given the various issues people have seen around the
setting of LANG and the cygwin 1.7 changes in handling locale,
I would also recommend looking into that. Try setting LANG=C
and comparing with LANG=C.UTF-8 and LANG=en_US.UTF8 ...

Ken is probably right, but this is easy to check.

Regards -- Eliot Moss

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -