From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Berman Newsgroups: gmane.emacs.devel Subject: auto-composition-mode and display properties Date: Thu, 21 Feb 2008 17:12:37 +0100 Message-ID: <878x1ee1ai.fsf@escher.local.home> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1203610395 31507 80.91.229.12 (21 Feb 2008 16:13:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Feb 2008 16:13:15 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 21 17:13:40 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 1JSE39-0005IQ-Bx for ged-emacs-devel@m.gmane.org; Thu, 21 Feb 2008 17:13:31 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JSE2e-00047b-2g for ged-emacs-devel@m.gmane.org; Thu, 21 Feb 2008 11:13:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JSE2a-00047K-RC for emacs-devel@gnu.org; Thu, 21 Feb 2008 11:12:56 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JSE2Z-00046u-9u for emacs-devel@gnu.org; Thu, 21 Feb 2008 11:12:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JSE2Z-00046r-3l for emacs-devel@gnu.org; Thu, 21 Feb 2008 11:12:55 -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 1JSE2Y-0006f6-Ph for emacs-devel@gnu.org; Thu, 21 Feb 2008 11:12:54 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JSE2S-00018F-7x for emacs-devel@gnu.org; Thu, 21 Feb 2008 16:12:48 +0000 Original-Received: from i5387dd23.versanet.de ([83.135.221.35]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Feb 2008 16:12:48 +0000 Original-Received: from Stephen.Berman by i5387dd23.versanet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Feb 2008 16:12:48 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: i5387dd23.versanet.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) 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:89834 Archived-At: Since the unicode merge, composite.el contains auto-composition-mode, which is enabled globally by default. This adds the auto-composed property to every character. The auto-composed property also gets added to display properties. For example: 1. emacs -Q 2. Type the string "ab". 3. Put the cursor after "b" and type `M-: (put-text-property (1- (point)) (point) 'display "test")'. Now the buffer display "atest". 4. Put the cursor after "a", i.e. on the first "t" and type `C-u C-x ='. The *Help* buffer says: There are text properties here: auto-composed t display [Show] By clicking on `[Show]' we get the value of the display property: #("test" 0 4 (auto-composed t)) I assume the display property is supposed to be like this, i.e. this is not a bug? I ask because it is wreaking havoc with isearch in a mode I have that uses display properties (e.g., isearch stops when it gets to the bottom of the window, even though there are further occurrences out of view, and the cursor cycles over lines above the last visible occurrence). There may be a bug in the mode that is triggered by isearch with auto-composition-mode enabled, but I don't know how to debug it: when I instrument isearch-mode for edebug and step through it, after isearch-update is called the focus for entering isearch strings becomes the buffer of isearch.el and switching back to the buffer with my mode interrupts isearch. So I cannot trigger the bug under edebug. All I know is that when I disable auto-composition-mode, isearch works fine in my mode (and it works fine in CVS Emacs prior to the unicode merge). So I would like to know, again, if auto-composition-mode is really supposed to add the auto-composed property to the display string. And does anyone have any suggestions for how I can debug isearch? Steve Berman