From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: compilation-forget-errors still used by tex-mode.el Date: 01 Apr 2004 15:13:58 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040331135707.514e5cbe.occitan@esperanto.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1080830213 22566 80.91.224.253 (1 Apr 2004 14:36:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 1 Apr 2004 14:36:53 +0000 (UTC) Cc: Markus Rost , Stefan Monnier , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Apr 01 16:36:44 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1B93JE-00036L-00 for ; Thu, 01 Apr 2004 16:36:44 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B93JE-00014e-00 for ; Thu, 01 Apr 2004 16:36:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B92Xo-0007OJ-03 for emacs-devel@quimby.gnus.org; Thu, 01 Apr 2004 08:47:44 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B92WJ-000728-MD for emacs-devel@gnu.org; Thu, 01 Apr 2004 08:46:11 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B92Pd-00063H-K2 for emacs-devel@gnu.org; Thu, 01 Apr 2004 08:39:48 -0500 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.30) id 1B915Q-000663-Uf for emacs-devel@gnu.org; Thu, 01 Apr 2004 07:14:21 -0500 Original-Received: (qmail 62046 invoked from network); 1 Apr 2004 12:14:17 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 1 Apr 2004 12:14:17 -0000 Original-To: Daniel Pfeiffer In-Reply-To: <20040331135707.514e5cbe.occitan@esperanto.org> Original-Lines: 53 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:21159 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21159 dapfy@t-online.de (Daniel Pfeiffer) writes: > Saluton, >=20 > Stefan Monnier skribis: >=20 > > >> We should maybe just introduce a new `compilation-current-error' mar= ker > >=20 > > > And add compilation-current-error to overlay-arrow-variable-list :-) > >=20 > > Now there's an idea. >=20 > overlay-arrow-variable-list seems to be a very embryonic feature. While = you > can put more than one variable into it, only the first occurence in the b= uffer > actually gets a little arrow in the fringe.=20=20 In a compile buffer, I would think that one current error marker is enough. Why do you need more than that?! > And even though there is a s= tring > to > use instead on non-window frames, the feature is not even present on a > text-terminal.=20=20 It is supposed to work, so if not, that's a bug. > And it only works at BOL, whereas error-messages are now > recognized anywhere on a line, even one behind another. Yes, ok, but you can still use it to point out the line as such. >=20 > So I'll have to use my own overlay. I'm wondering if flashing this for h= alf a > second, like the jumped to position, is useful. While that is more of a = toy, > since the cursor lands there anyways, highlighting the message seems to b= e an > essential feature for some people. If you get distracted after Cx- ` you= can > easily miss this within half a second =E2=80=94 especially if it takes a = second to > fetch a remote file first. If you decide to use your own overlay, I suggest that you keep the highlight on the error message. I don't see a need to just highlight it briefly. In any case, the highlight will disappear when you have reached past the last error. >=20 > Maybe I should combine half a second with a pre command hook? Or leave it > until another message gets located? Leave it. --=20 Kim F. Storm http://www.cua.dk