From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kai Grossjohann Newsgroups: gmane.emacs.devel Subject: Re: enriched-mode and switching major modes. Date: Thu, 16 Sep 2004 15:20:14 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: <86u0tyz6y9.fsf@ketchup.de.uu.net> References: <200409042358.i84Nwjt19152@raven.dms.auburn.edu> <87llfn5ihw.fsf@emacswiki.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1095340884 18474 80.91.229.6 (16 Sep 2004 13:21:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Sep 2004 13:21:24 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 16 15:21:12 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1C7wCF-0003uf-00 for ; Thu, 16 Sep 2004 15:21:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C7wHv-0005hD-B1 for ged-emacs-devel@m.gmane.org; Thu, 16 Sep 2004 09:27:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C7wHp-0005gy-0M for emacs-devel@gnu.org; Thu, 16 Sep 2004 09:26:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C7wHn-0005gm-HO for emacs-devel@gnu.org; Thu, 16 Sep 2004 09:26:56 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C7wHn-0005gj-FV for emacs-devel@gnu.org; Thu, 16 Sep 2004 09:26:55 -0400 Original-Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C7wBp-0007LT-47 for emacs-devel@gnu.org; Thu, 16 Sep 2004 09:20:45 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1C7wBo-0001TE-00 for ; Thu, 16 Sep 2004 15:20:44 +0200 Original-Received: from 139.4.37.213 ([139.4.37.213]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Sep 2004 15:20:44 +0200 Original-Received: from kai by 139.4.37.213 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Sep 2004 15:20:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 38 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 139.4.37.213 User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:ZpmcxvIvwBA245TjaahG+oA7atA= 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:27161 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:27161 Richard Stallman writes: > However, there are some details here that are nontrivial problems. > > 1. How to distinguish between two similar boxes with the same specs > and a single longer box. That's true. Perhaps one could have a block-begin text property and a block-end text property, both attached to the gap between two characters? > 2. How to represent line breaks. Saying "break one long line at > display time" would work ok for display, but all the commands that > operate on lines would see just one long line there. I think this is not too much of a problem. Kim has done a great job of changing the behavior of some Emacs commands to do cua-like things. I expect that a similar method would work to change the behavior of beginning-of-line, next-line and so on. > 3. How to represent indentation. If the indentation appears only > in redisplay, Lisp code that looks at the text will think it is not > indented at all. Here again, I think it is not a problem. Why does the Lisp code need to see the newline characters? Why does it need to see the leading whitespace? Imagine that you have a feature which wraps long lines at word boundaries at display time. Imagine that this feature was configured to wrap to the window width. Now imagine that you make the window narrower. This introduces more wrapping points. But which Lisp code needs to see more newlines? If we have source code, then we do need newline characters, but we're talking about editing text. Kai