From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Emacs's handling of line numbers [from bug#5042] Date: Sun, 18 Apr 2010 20:11:16 +0200 Message-ID: References: <837ho6czb6.fsf@gnu.org> <8339yucbsg.fsf@gnu.org> <83wrw5bxkc.fsf@gnu.org> <83tyr9bgid.fsf@gnu.org> <83r5mcbqzo.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1271614314 6474 80.91.229.12 (18 Apr 2010 18:11:54 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 18 Apr 2010 18:11:54 +0000 (UTC) Cc: lekktu@gmail.com, monnier@iro.umontreal.ca, mark.lillibridge@hp.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 18 20:11:51 2010 connect(): No such file or directory 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.69) (envelope-from ) id 1O3YyC-0008Ty-8d for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 20:11:48 +0200 Original-Received: from localhost ([127.0.0.1]:42986 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3YyA-0001T4-LS for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 14:11:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3Yy5-0001Sz-VV for emacs-devel@gnu.org; Sun, 18 Apr 2010 14:11:42 -0400 Original-Received: from [140.186.70.92] (port=41747 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Yy3-0001Sn-Ak for emacs-devel@gnu.org; Sun, 18 Apr 2010 14:11:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3Yy1-0007i2-Kf for emacs-devel@gnu.org; Sun, 18 Apr 2010 14:11:39 -0400 Original-Received: from mail-bw0-f225.google.com ([209.85.218.225]:33036) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3Yy1-0007hw-EQ; Sun, 18 Apr 2010 14:11:37 -0400 Original-Received: by bwz25 with SMTP id 25so3993521bwz.8 for ; Sun, 18 Apr 2010 11:11:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=4ZYne4HisFJ2FFznMY7dtkbwko3qXZhPNMYoVdfFuBo=; b=apP0rVROdTjH5ioDvKeg/O/gkaw9Sy+UtJ9wQc8UVfcWeKS1IgM2TAQyF0RfJtjrRq Q9aopsHAJo8L0OvYygS5KKHFuEQhT7M6TI2xP8p7ODdlUo4vRoOVQtZw6LnKN6jMXRHY xHA77OoMpzyDVP79TLmJfREiJed8+wTC0xtac= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=aUbAzfasqYVuUX7+E9AlBzZY/bWXAjFSHLbDZpvFVpGojjE+CHlOkx717CnrXbZ1iD ljUSFt8IuakNguiNS5KycKP/e6kiDgqaZQAr5o2absP3saMmfCezH3/Q9KzhHowviVj7 KM+Va28IBh8LdQprYIlabHIJi6xw+l7Vqge6E= Original-Received: by 10.239.169.18 with HTTP; Sun, 18 Apr 2010 11:11:16 -0700 (PDT) In-Reply-To: <83r5mcbqzo.fsf@gnu.org> Original-Received: by 10.239.134.80 with SMTP id 16mr322225hby.117.1271614296166; Sun, 18 Apr 2010 11:11:36 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:123851 Archived-At: On Sun, Apr 18, 2010 at 7:38 PM, Eli Zaretskii wrote: >> Date: Sun, 18 Apr 2010 10:00:45 -0700 >> From: Mark Lillibridge >> CC: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org >> >> =C2=A0 =C2=A0 The issue is that font-lock mode, goto-line, linum mode, a= nd perhaps >> other features need to treat them differently. =C2=A0These features want= to >> widen to the "application" restriction when processing the current >> buffer, ignoring any temporary restriction. > ... > IOW, by introducing 2 kinds of restriction, you don't solve the > problem, you just push it a bit farther. When it comes to things that needs to do some parsing (font-lock, indentation, completion etc) I am not sure widening is always the right mechanism. At least for multiple major modes in a buffer I think something like "show me all characters that belongs to this major mode" would fit better. And that of course requires very low level changes to Emacs.