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 15:50:45 +0200 Message-ID: References: <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=UTF-8 X-Trace: dough.gmane.org 1271598681 19571 80.91.229.12 (18 Apr 2010 13:51:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 18 Apr 2010 13:51:21 +0000 (UTC) Cc: Juanma Barranquero , mark.lillibridge@hp.com, emacs-devel@gnu.org, Juri Linkov , monnier@iro.umontreal.ca, Eli Zaretskii To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 18 15:51:18 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 1O3Uu5-0001nk-Ql for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 15:51:18 +0200 Original-Received: from localhost ([127.0.0.1]:47360 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Uu5-00030m-72 for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 09:51:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3Uty-00030U-It for emacs-devel@gnu.org; Sun, 18 Apr 2010 09:51:10 -0400 Original-Received: from [140.186.70.92] (port=47745 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3Utw-00030I-RM for emacs-devel@gnu.org; Sun, 18 Apr 2010 09:51:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3Utv-00036p-JB for emacs-devel@gnu.org; Sun, 18 Apr 2010 09:51:08 -0400 Original-Received: from fg-out-1718.google.com ([72.14.220.154]:44157) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3Utv-00036M-5H; Sun, 18 Apr 2010 09:51:07 -0400 Original-Received: by fg-out-1718.google.com with SMTP id e21so1346207fga.12 for ; Sun, 18 Apr 2010 06:51:05 -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=AT3CROx60GoDQn/YjsTl7wb3Y2TV3ze7yMuqgLI+E7s=; b=ud+CeHbCVgLUGB4pyeRPoAKsiaVgi/xR01FrDFLHTOb5JrcXTtoqcUUVvpG+MilZv2 IItQhJTHZUtMDGrtwmJD0mS+aH9FvUI0L+irfjQImci06pRhAw6WXxGOznYM8+gm5ZqC dzGoSYrQ+tZXXVy0mf5JQnEZtR/fxV+UcSIR8= 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=KmbvVJR6WinHiz1622fNlHTO/+/v58pF7jZjUWa92fC9zd7eQQmCERWpoNefeABAz+ AzaAuEQRrAMg91bpUP9vl4+cBPaRt9G5QjaSxMeU/8XX2Zxh1KHSKjv+LqssCqNS5LGt 6fquS6F88IPrqU7eBO8gpky/ixoXY3t/F2Xyk= Original-Received: by 10.239.169.18 with HTTP; Sun, 18 Apr 2010 06:50:45 -0700 (PDT) In-Reply-To: Original-Received: by 10.239.161.84 with SMTP id g20mr344206hbd.200.1271598665209; Sun, 18 Apr 2010 06:51:05 -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:123840 Archived-At: On Sun, Apr 18, 2010 at 3:44 PM, Drew Adams wrote: >> > 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. I think Juri sugggested that there should not be an interactive command for doing that. Would not low level elisp functions be enough for the purpose of widening Info buffers?