From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: William Xu Newsgroups: gmane.emacs.devel Subject: Re: 23.0.50; C-M-p is missing (carbon emacs) Date: Wed, 23 Jan 2008 15:23:47 +0900 Organization: the Church of Emacs Message-ID: References: <863aspfv5y.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1201069471 16849 80.91.229.12 (23 Jan 2008 06:24:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 23 Jan 2008 06:24:31 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 23 07:24:51 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JHZ2Y-0003tr-9K for ged-emacs-devel@m.gmane.org; Wed, 23 Jan 2008 07:24:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JHZ28-0006ga-Cf for ged-emacs-devel@m.gmane.org; Wed, 23 Jan 2008 01:24:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JHZ24-0006gV-Hv for emacs-devel@gnu.org; Wed, 23 Jan 2008 01:24:20 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JHZ22-0006e4-KV for emacs-devel@gnu.org; Wed, 23 Jan 2008 01:24:19 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JHZ22-0006dv-C3 for emacs-devel@gnu.org; Wed, 23 Jan 2008 01:24:18 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JHZ22-0001hD-44 for emacs-devel@gnu.org; Wed, 23 Jan 2008 01:24:18 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JHZ1y-00053D-RH for emacs-devel@gnu.org; Wed, 23 Jan 2008 06:24:14 +0000 Original-Received: from gw.community-engine.co.jp ([210.255.51.230]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 06:24:14 +0000 Original-Received: from william.xwl by gw.community-engine.co.jp with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 06:24:14 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 40 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: gw.community-engine.co.jp User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (darwin) Cancel-Lock: sha1:UlgjpQZxVl+lwYnYoQdI8DRTBK0= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:87358 Archived-At: Ted Zlatanov writes: > You can find what's using a key with `C-h k'; for me C-M-p is bound to > backward-list which is the default. What does it say for you? Nothing. I found the cause. It's out of Emacs. Some system wide keymapping doesn't generate C-M-p key at all... > There is no Cocoa Emacs. Use Emacs.App for a Cocoa port, it's not We actually referred to the same thing. The binary result of Cocoa port is also Emacs.app. So calling the nextstep/cocoa port Emacs.app is rather confusing. Maybe a better naming is Nextstep Emacs, or Cocoa Emacs(not quite appropriate, but help people understand, i'd say). > exactly in sync with CVS but it's OK and supported. If you followed their mailing lists, you must know that I had reported my failing attempts of either running the pre-compiled binary or building from sources. And witnessed a similar failing attempt days ago. No solutions yet. [...] > I'm pretty sure that the Carbon port will > remain unsupported, regardless of its performance, because there's no > maintainer and (IIRC) it was decided to wait until after the next Emacs > release to decide what to do with MacOS X support. Unsupported though, it's still runable & pretty stable, unlike Nextstep Emacs. -- William http://williamxu.net9.org