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 16:03:29 +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 1271599511 21853 80.91.229.12 (18 Apr 2010 14:05:11 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 18 Apr 2010 14:05:11 +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 16:05:09 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 1O3V7V-0007jn-2W for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 16:05:09 +0200 Original-Received: from localhost ([127.0.0.1]:57409 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3V7U-0007EW-JU for ged-emacs-devel@m.gmane.org; Sun, 18 Apr 2010 10:05:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O3V6I-0006pn-7E for emacs-devel@gnu.org; Sun, 18 Apr 2010 10:03:54 -0400 Original-Received: from [140.186.70.92] (port=45917 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O3V6G-0006pK-Sk for emacs-devel@gnu.org; Sun, 18 Apr 2010 10:03:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O3V6F-0005w3-6X for emacs-devel@gnu.org; Sun, 18 Apr 2010 10:03:52 -0400 Original-Received: from mail-bw0-f225.google.com ([209.85.218.225]:34411) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O3V6F-0005vY-1f; Sun, 18 Apr 2010 10:03:51 -0400 Original-Received: by bwz25 with SMTP id 25so3865795bwz.8 for ; Sun, 18 Apr 2010 07:03:49 -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=Hy/S6qCTQ8BczMkd5rVWMy7RrB0MIq0Ae4s3Td7sigk=; b=FCDD069Uv2++L37O1Vu+BJRcQHWwU7o7TUCuWXKCi5OAim0UNmyRVcQNkzojn7sZDX jmhiBCYaRON8tan1i6raRA3yQlEo/9cpiS5jcMWB4Z6YfP4ZRfFffKQNSTNXTJGFvz4E Ys8XRZgBnmSg3JEpTMdo5sZanheCLj2Nww4Zg= 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=vQQtUlSzfgcAchAk8ckElGRM3F6dorzZxaKzmrTMG2AQ8R6rPxR2i2IVarSdQfkw73 uOBpPqq+hU8P2HpKVknp+83Pif9B5UqBRuiXEjpUxtsFuY5WlLNnRHQwzy7oDrfqXrzX 4P4mHg0EuFw0lP63p1uX5nIIzSpgHlkRiLe84= Original-Received: by 10.204.81.29 with HTTP; Sun, 18 Apr 2010 07:03:29 -0700 (PDT) In-Reply-To: Original-Received: by 10.204.161.211 with SMTP id s19mr3667909bkx.129.1271599429563; Sun, 18 Apr 2010 07:03:49 -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:123841 Archived-At: On Sun, Apr 18, 2010 at 15:44, Drew Adams wrote: > 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. What I proposed is not removing that possibility, just making user n/w and program n/w two different facilities; one is a user commodity, and the other is (low or medium)-level infrastructure for elisp libraries. That the two are conflated is the result of library auhors not having other equally easy way to show selected parts of a buffer, I guess. > 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. No one has been proposing less user control. Juanma