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: visual-line-mode and line wrapping Date: Mon, 24 May 2010 22:33:14 +0200 Message-ID: References: <87typxp055.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1274735426 8173 80.91.229.12 (24 May 2010 21:10:26 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 24 May 2010 21:10:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: Leo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 24 23:10:25 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 1OGeul-0002UM-WE for ged-emacs-devel@m.gmane.org; Mon, 24 May 2010 23:10:24 +0200 Original-Received: from localhost ([127.0.0.1]:40440 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGeul-0003Et-7p for ged-emacs-devel@m.gmane.org; Mon, 24 May 2010 17:10:23 -0400 Original-Received: from [140.186.70.92] (port=45156 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGeLN-0006hz-Rj for emacs-devel@gnu.org; Mon, 24 May 2010 16:33:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OGeLC-0002jy-2X for emacs-devel@gnu.org; Mon, 24 May 2010 16:33:43 -0400 Original-Received: from mail-yw0-f194.google.com ([209.85.211.194]:33812) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OGeLB-0002js-92 for emacs-devel@gnu.org; Mon, 24 May 2010 16:33:37 -0400 Original-Received: by ywh32 with SMTP id 32so2578094ywh.5 for ; Mon, 24 May 2010 13:33:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=0QeX7TripuAEpBlt0VkLtKXXFSf5fAovXpnGZka4DZM=; b=LhfpEFwAy/CrMEfl8ky6rV1XO/FLRXNg8gEoF9e9ZCneNpp4kqluiSU37Jn3CRVTG4 2pow+cJXaU8fckOALBb10Wm03F9S3g2wKfVfmB5+BYfIEE35rmITffeWxyrdwNce2A+/ GonPtGoL+XCR34zo6ECYmF3qmkgPWp3afHq+s= 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:content-transfer-encoding; b=myTn/aaGXTTJzPp746M2CSTy3COpXtRN2V6F8dFOirJVsby+wcisFxTSJWPM9An7Tc wVpcDOB1fPdbxini1kK6ODx5wRdNz/uk2U7701qxPP4FhIk9dqYhiRnpqr8SOMDlx87o pBlddaR7e2bh3JayW6KeSn0jIqZeqbxCaYRnw= Original-Received: by 10.101.202.2 with SMTP id e2mr6584189anq.269.1274733215761; Mon, 24 May 2010 13:33:35 -0700 (PDT) Original-Received: by 10.100.177.20 with HTTP; Mon, 24 May 2010 13:33:14 -0700 (PDT) In-Reply-To: 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:125212 Archived-At: On Mon, May 24, 2010 at 9:53 PM, Leo wrote: > On 2010-05-24 20:31 +0100, Chong Yidong wrote: >>> Using fringes or margins (now that I have tried it and I can imagine ho= w >>> Lennart implement his mode) are all workarounds and they are not much >>> different than opening up a frame with the desired width but then it is >>> a waste of screen estate and it has impact on productivity. >> >> Implementing a wrap margin creates exactly the same waste of screen >> estate. =C2=A0Functionally, the two are equivalent. > > It might be the case for that buffer alone but the experience would be > different if you consider other activities while editing that buffer ie > switching to buffers, splitting windows etc. See this screenshot: > http://imagebin.org/98184. Basically I want to be able to put a cap on > the line length so that it won't go insanely long and make reading > painful. It seems like you think you are missing something in my implementation, but I found it hard to understand exactly what you are missing. Could you perhaps explain?