From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Emacs's handling of line numbers [from bug#5042] Date: Sun, 18 Apr 2010 11:05:52 +0300 Organization: JURTA Message-ID: <87aat1b2sr.fsf@mail.jurta.org> References: <837ho6czb6.fsf@gnu.org> <8339yucbsg.fsf@gnu.org> <83wrw5bxkc.fsf@gnu.org> <83tyr9bgid.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1271578837 30661 80.91.229.12 (18 Apr 2010 08:20:37 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 18 Apr 2010 08:20:37 +0000 (UTC) Cc: Eli Zaretskii , monnier@iro.umontreal.ca, mark.lillibridge@hp.com, emacs-devel@gnu.org To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 18 10:20:35 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 1O3Pk3-0007ma-59 for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 10:20:35 +0200 Original-Received: from localhost ([127.0.0.1]:43036 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Pk2-0008HL-In for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 04:20:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3Phu-0007LC-Jw for emacs-devel@gnu.org; Sun, 18 Apr 2010 04:18:22 -0400 Original-Received: from [140.186.70.92] (port=47121 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Php-0007Jv-QN for emacs-devel@gnu.org; Sun, 18 Apr 2010 04:18:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3Pho-0007xQ-6F for emacs-devel@gnu.org; Sun, 18 Apr 2010 04:18:17 -0400 Original-Received: from smtp-out2.starman.ee ([85.253.0.4]:39653 helo=mx2.starman.ee) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3Phl-0007wC-8Z; Sun, 18 Apr 2010 04:18:13 -0400 X-Virus-Scanned: by Amavisd-New at mx2.starman.ee Original-Received: from mail.starman.ee (82.131.96.36.cable.starman.ee [82.131.96.36]) by mx2.starman.ee (Postfix) with ESMTP id BA32C3F4118; Sun, 18 Apr 2010 11:18:07 +0300 (EEST) In-Reply-To: (Juanma Barranquero's message of "Sun, 18 Apr 2010 05:49:54 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (x86_64-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/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:123834 Archived-At: > For the same reason that the narrowing stack that Drew proposes could > be useful: if I'm reading an Info node, my narrowing/widening > shouldn't interfere with the use of narrowing by Info-mode, because > that's just an artifact of its implementation. Being able to do M-x > widen in an Info node and seeing the whole buffer is IMO a "bug" > because it destroys the abstraction. I agree that user commands (with the prefix map `C-x n') should not widen or narrow the Info buffer outside of the current Info node. Only some low-level functions should be allowed to do this. -- Juri Linkov http://www.jurta.org/emacs/