From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: Overlay arrow in *compilation* and *grep* buffers Date: Fri, 29 Apr 2005 20:52:55 +1200 Message-ID: <17009.62951.957607.360268@farnswood.snap.net.nz> References: <01c548ba$Blat.v2.4$e4827900@zahav.net.il> <01c54909$Blat.v2.4$070f3e60@zahav.net.il> <01c54c2b$Blat.v2.4$e15e8560@zahav.net.il> <17009.19855.763603.487800@farnswood.snap.net.nz> <01c54c8a$Blat.v2.4$6afa17e0@zahav.net.il> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1114764860 611 80.91.229.2 (29 Apr 2005 08:54:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 29 Apr 2005 08:54:20 +0000 (UTC) Cc: juri@jurta.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 29 10:54:17 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DRRFq-0008Ek-Rn for ged-emacs-devel@m.gmane.org; Fri, 29 Apr 2005 10:53:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DRRM8-0003yd-Gw for ged-emacs-devel@m.gmane.org; Fri, 29 Apr 2005 05:00:16 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DRRLP-0003yX-H6 for emacs-devel@gnu.org; Fri, 29 Apr 2005 04:59:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DRRLN-0003yL-Oz for emacs-devel@gnu.org; Fri, 29 Apr 2005 04:59:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DRRLN-0003pu-80 for emacs-devel@gnu.org; Fri, 29 Apr 2005 04:59:29 -0400 Original-Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DRRJO-00062H-62; Fri, 29 Apr 2005 04:57:26 -0400 Original-Received: from farnswood.snap.net.nz (p166-tnt1.snap.net.nz [202.124.110.166]) by viper.snap.net.nz (Postfix) with ESMTP id D7C8B4AFD1C; Fri, 29 Apr 2005 20:53:00 +1200 (NZST) Original-Received: by farnswood.snap.net.nz (Postfix, from userid 501) id CB52B62A99; Fri, 29 Apr 2005 09:52:56 +0100 (BST) Original-To: Eli Zaretskii In-Reply-To: <01c54c8a$Blat.v2.4$6afa17e0@zahav.net.il> X-Mailer: VM 7.19 under Emacs 22.0.50.26 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:36495 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:36495 > So, if the next-error-overlay-arrow-position's string doesn't affect > anything but compile.el, how come text terminals started to display > the arrow as result of a discussion about GUD and Edebug? What am I > missing? I might be losing your meaning, but the conflict was between GUD and next-error. Juri and I changed them to use their own overlay arrow. Juri then suggested that the default value for the property overlay-arrow-string should be changed to "=>" which was done by Kim (2005-04-08). Previously it was nil which meant that no arrow was displayed in a text terminal which was not by design, but might have been your preference. Currently simple.el has: (put 'next-error-overlay-arrow-position 'overlay-arrow-string "=>") but this could be removed as it is the default now anyway (I think Juri disappeared again before 2005-04-08). Alternatively, as suggested, it could be changed to: (put 'next-error-overlay-arrow-position 'overlay-arrow-string "") I don't think the condition (unless (display-graphic-p)... is necessary (or desirable). If there is a fringe, a bitmap is used and overlay-arrow-string is not used. If there is no fringe, then presumably you don't want "=>" overwriting text whether the terminal is text or graphic. I suggest this latter change until Juri (or maybe Stefan) comes up with a better solution that will work with "=>". Nick