From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Emacs's handling of line numbers [from bug#5042] Date: Sun, 18 Apr 2010 19:03:43 +0200 Message-ID: References: <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=UTF-8 X-Trace: dough.gmane.org 1271610258 23678 80.91.229.12 (18 Apr 2010 17:04:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 18 Apr 2010 17:04:18 +0000 (UTC) Cc: Juri Linkov , Eli Zaretskii , monnier@iro.umontreal.ca, mark.lillibridge@hp.com, emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 18 19:04:16 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 1O3Xun-00055g-MG for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 19:04:13 +0200 Original-Received: from localhost ([127.0.0.1]:50935 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Xun-0003io-7w for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 13:04:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3Xui-0003iN-5z for emacs-devel@gnu.org; Sun, 18 Apr 2010 13:04:08 -0400 Original-Received: from [140.186.70.92] (port=56302 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Xug-0003hq-To for emacs-devel@gnu.org; Sun, 18 Apr 2010 13:04:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3Xuf-0005Oj-C6 for emacs-devel@gnu.org; Sun, 18 Apr 2010 13:04:06 -0400 Original-Received: from mail-bw0-f225.google.com ([209.85.218.225]:52746) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3Xuf-0005OV-5G; Sun, 18 Apr 2010 13:04:05 -0400 Original-Received: by bwz25 with SMTP id 25so3955087bwz.8 for ; Sun, 18 Apr 2010 10:04:03 -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; bh=G+0bxxtrLk4vWtdwoiL0paDvIDBLVRBcLarv8J2v0D4=; b=mq/1HgOG8FJrLqPX7BaTjlwADZ8nXjhim7bE3LV4K/bIledolrBtURLoCLO6ZeLWQl +so8W/MVDjq5L8A0vt7ikgB3PowQYfZrJumK3Bu9PH2itTKSn9zKQCzHAfmsP0TiejwG eBhMFv5eIGXShuro593UxRZX1p0kpUb5C4HXo= 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; b=u0bEZPS/R7ErIYBt2Ex2LtN4WWJjFS1wiYPjOttOskYEtmDiDLnkyI2IeuqM1+X2sL HIxtMYq22bC3p3q6x9+kvZi9BoMVK9hCg9zs34S7zFUv/BBiG2gt2+Dpgw7LKiqSwa1l kQG9c71TSQkmhlu+KE3wzqA5u9IaA6eYutqbM= Original-Received: by 10.204.81.29 with HTTP; Sun, 18 Apr 2010 10:03:43 -0700 (PDT) In-Reply-To: Original-Received: by 10.204.73.143 with SMTP id q15mr3784776bkj.184.1271610243137; Sun, 18 Apr 2010 10:04:03 -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:123846 Archived-At: On Sun, Apr 18, 2010 at 18:41, Drew Adams wrote: > My post replied not to your proposal but to Juri's statement I know. And Juri was commenting on mine. > He said that users should not be able to use a command to widen or narrow the > buffer outside of the current node. Not exactly. He said "user commands (with the prefix map `C-x n')". I don't know whether he was against defining other user commands, menu options or other ways to do that. I would be *for* defining them. Just not as general user commands. > IMO Juri did, by saying that user narrowing and widening commands should not go > beyond the current Info node. Again, user commands in the C-x n prefix map. And I would agree with that. Even if it is sometimes (how often?) useful to be able to widen the restriction in an Info buffer, that restriction is a programming convenience for Info-mode (that it uses narrowing is an implementation detail), so Info-mode should offer the way to deactivate it. Juanma