From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Emacs's handling of line numbers [from bug#5042] Date: Sun, 18 Apr 2010 06:44:17 -0700 Message-ID: References: <837ho6czb6.fsf@gnu.org> <8339yucbsg.fsf@gnu.org> <83wrw5bxkc.fsf@gnu.org><83tyr9bgid.fsf@gnu.org> <87aat1b2sr.fsf@mail.jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1271598293 18417 80.91.229.12 (18 Apr 2010 13:44:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 18 Apr 2010 13:44:53 +0000 (UTC) Cc: 'Eli Zaretskii' , monnier@iro.umontreal.ca, mark.lillibridge@hp.com, emacs-devel@gnu.org To: "'Juri Linkov'" , "'Juanma Barranquero'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 18 15:44: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 1O3Unq-0007UP-UE for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 15:44:51 +0200 Original-Received: from localhost ([127.0.0.1]:41406 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Unq-000875-AK for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 09:44:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3Unk-00086A-C7 for emacs-devel@gnu.org; Sun, 18 Apr 2010 09:44:44 -0400 Original-Received: from [140.186.70.92] (port=37694 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Unj-00085P-4I for emacs-devel@gnu.org; Sun, 18 Apr 2010 09:44:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3Unh-00023G-Mj for emacs-devel@gnu.org; Sun, 18 Apr 2010 09:44:43 -0400 Original-Received: from rcsinet10.oracle.com ([148.87.113.121]:19852) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3Unh-000230-DS; Sun, 18 Apr 2010 09:44:41 -0400 Original-Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o3IDib0u004600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 18 Apr 2010 13:44:38 GMT Original-Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o3IDiZBM010849; Sun, 18 Apr 2010 13:44:36 GMT Original-Received: from abhmt007.oracle.com by acsmt354.oracle.com with ESMTP id 185355931271598243; Sun, 18 Apr 2010 06:44:03 -0700 Original-Received: from dradamslap1 (/10.175.221.180) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 18 Apr 2010 06:44:03 -0700 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: Acre0AYTw5LGouXiTX6Hdk+lZ0kPDQAK4+Ag In-Reply-To: <87aat1b2sr.fsf@mail.jurta.org> X-Auth-Type: Internal IP X-Source-IP: acsinet15.oracle.com [141.146.126.227] X-CT-RefId: str=0001.0A090201.4BCB0CC7.004F:SCFMA922111,ss=1,fgs=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:123838 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. That's going too far, IMO. As Eli will perhaps point out (see bug #5839), there are reasons that some users will want to widen Info buffers. More generally, we should not remove `widen' as a command, even if in only some contexts. Likewise, `narrow'. What we should do is provide more user control (not less), possibly by creating a `widen-one-level' command as I suggested earlier. As I suggested in the thread for bug #5839, one way to at least not encourage user narrowing when that might get users (especially newbies) into trouble, would be to inhibit the activation of the `Narrow' lighter in the mode line (the lighter would still be shown but would not act as a widening button).