From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: line-line-move-visual: was line motion problem Date: Fri, 18 Jul 2008 08:30:17 -0700 Message-ID: <200807181530.m6IFUHVp029662@sallyv1.ics.uci.edu> References: <18557.63556.231489.523637@gargle.gargle.HOWL> <5F62534C-D5CE-4364-8F73-E1AE0D61B4E2@gmail.com> <87abghlqs2.fsf@stupidchicken.com> <87hcap3ct7.fsf@stupidchicken.com> <87mykg84aj.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1216395209 15619 80.91.229.12 (18 Jul 2008 15:33:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 18 Jul 2008 15:33:29 +0000 (UTC) Cc: Miles Bader , David Reitter , Chong Yidong , emacs-devel@gnu.org, raman@users.sourceforge.net To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 18 17:34:17 2008 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.50) id 1KJryE-0006Et-7i for ged-emacs-devel@m.gmane.org; Fri, 18 Jul 2008 17:34:10 +0200 Original-Received: from localhost ([127.0.0.1]:42215 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KJrxL-0003RX-Fn for ged-emacs-devel@m.gmane.org; Fri, 18 Jul 2008 11:33:15 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KJrx5-0003M1-Sv for emacs-devel@gnu.org; Fri, 18 Jul 2008 11:32:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KJrx3-0003LC-KS for emacs-devel@gnu.org; Fri, 18 Jul 2008 11:32:59 -0400 Original-Received: from [199.232.76.173] (port=60837 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KJrx3-0003L7-FF for emacs-devel@gnu.org; Fri, 18 Jul 2008 11:32:57 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]:39892) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1KJrwk-0003tU-4N; Fri, 18 Jul 2008 11:32:49 -0400 X-ICS-MailScanner-Watermark: 1216999818.7453@naNMeHmdztkotReNRHSeqA Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m6IFUHVp029662; Fri, 18 Jul 2008 08:30:17 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Fri, 18 Jul 2008 11:21:55 -0400") Original-Lines: 33 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) 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:100945 Archived-At: Stefan Monnier writes: > >> I don't know how many people actually want them in visual-line-mode > >> (I'd like a fringe item at a hard newline, but until this is > >> implemented the next best thing is a display-table element for \n). > > > We could leave the continuation glyphs, but make them less conspicuous. > > For a mode that expects most lines to be wrapped, I see not point in > leaving continuation marks. > > > To mark hard newlines, try the code below. I suggest to include this. > > > ;; 2230 = \x8B6 > > (defvar show-newlines-newline-code (vector (make-glyph-code 2230 > > blank-newline) 10)) > > [ Too long a line, huh? ] > > My font doesn't seem to know the char 2230, and UnicodeData.txt doesn't > seem to know that char either. So we should probably use something else. > > > (if show-newlines-mode > > (aset buffer-display-table 10 show-newlines-newline-code) > > (aset buffer-display-table 10 nil))) > > Better write it as: > > (aset buffer-display-table 10 > (if show-newlines-mode show-newlines-newline-code)) whitespace.el already has many many ways of dealing with whitespaces, wouldn't this mode be a better fit in whitespace.el?