From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: Jason Rumney <jasonr@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Carbon port emacs-unicode-2 build problem under MacOSX
Date: Tue, 06 Nov 2007 12:34:54 +0000
Message-ID: <47305F6E.2030204@gnu.org>
References: <m21wb3vayb.fsf@news.cyberhut.org>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: ger.gmane.org 1194352513 13234 80.91.229.12 (6 Nov 2007 12:35:13 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Tue, 6 Nov 2007 12:35:13 +0000 (UTC)
Cc: emacs-devel@gnu.org
To: CHENG Gao <chenggao@gmail.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 06 13:35:16 2007
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
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 1IpNeG-0000M0-5x
	for ged-emacs-devel@m.gmane.org; Tue, 06 Nov 2007 13:35:16 +0100
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1IpNe5-00066n-AT
	for ged-emacs-devel@m.gmane.org; Tue, 06 Nov 2007 07:35:05 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IpNe2-00066X-4e
	for emacs-devel@gnu.org; Tue, 06 Nov 2007 07:35:02 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IpNdy-00060f-4f
	for emacs-devel@gnu.org; Tue, 06 Nov 2007 07:35:01 -0500
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IpNdx-00060H-VD
	for emacs-devel@gnu.org; Tue, 06 Nov 2007 07:34:57 -0500
Original-Received: from outmail1.freedom2surf.net ([194.106.33.237])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <jasonr@gnu.org>) id 1IpNdx-00024c-ME
	for emacs-devel@gnu.org; Tue, 06 Nov 2007 07:34:57 -0500
Original-Received: from [127.0.0.1] (i-83-67-23-108.freedom2surf.net [83.67.23.108])
	by outmail1.freedom2surf.net (Postfix) with ESMTP
	id E44FC512CF; Tue,  6 Nov 2007 12:34:56 +0000 (GMT)
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
In-Reply-To: <m21wb3vayb.fsf@news.cyberhut.org>
X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=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:82657
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/82657>

CHENG Gao wrote:
> Emacs running from terminal works ok. But Emacs.app (running from
> Finder) is not usable. For every keystroke (keyboard input or mouse
> click) I have to wait for several minutes. I think it's owing to my
> brutal revert of mac_set_unicode_keystrok_event which makes
> do_keystrokes dysfunction.
> Another possibility is workaround of "export LIBS=-lresolv". I have no
> idea. Or owing to merge of multi-tty code?
>   
Definitely the merge of multi-tty code, the same problem has been
reported in the trunk multiple times.
macterm.c is missing a call to add_keyboard_wait_descriptor (see xterm.c
and w32term.c), which was necessary to get input working at all on
Windows after the multi-tty merge. Despite this being pointed out
several times, noone who is using a Mac has tried adding this call and
reported back whether it solves the problem.

I think reverting the change is correct, as the old mule based utf
codings are no longer used internally, but it might be a good idea to
find what the change was in the trunk that caused this code to be
merged, as there may be something there that should be changed in the
unicode branch as well.