From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Different (buffer-file-)coding-systems for different regions of one buffer? (for Rmail MIME) Date: Fri, 23 May 2003 08:03:52 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200305211953.h4LJr9Iq000699@rum.cs.yale.edu> <200305212229.h4LMTFKo001277@rum.cs.yale.edu> <878yszvean.fsf@tleepslib.sk.tsukuba.ac.jp> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1053691818 9317 80.91.224.249 (23 May 2003 12:10:18 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 23 May 2003 12:10:18 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri May 23 14:10:03 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19JBJ7-00023Z-00 for ; Fri, 23 May 2003 14:05:57 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19JBUr-0001Sh-00 for ; Fri, 23 May 2003 14:18:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19JBKQ-0003X0-Uu for emacs-devel@quimby.gnus.org; Fri, 23 May 2003 08:07:18 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19JBHp-00028M-Su for emacs-devel@gnu.org; Fri, 23 May 2003 08:04:37 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19JBHj-00021q-2h for emacs-devel@gnu.org; Fri, 23 May 2003 08:04:31 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19JBH6-0001ZC-9R for emacs-devel@gnu.org; Fri, 23 May 2003 08:03:52 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.20) id 19JBH6-0006HV-2D; Fri, 23 May 2003 08:03:52 -0400 Original-To: "Stephen J. Turnbull" In-reply-to: <878yszvean.fsf@tleepslib.sk.tsukuba.ac.jp> (stephen@xemacs.org) Original-cc: stktrc@yahoo.com X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:14125 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:14125 Otherwise, there are at least two radically different views of many files, and there must be a buffer (in the generic sense of a separate region of memory) for presentation, and one for the much more restricted changes you wish propagated back to the file (setting flags). I see no good reason why the region of memory used for presentation shouldn't "waste" a few score bytes and be promoted to an Emacs buffer. It pretty much has to be an Emacs buffer, or part of one. There is no other natural or easy way to implement it in the context of Emacs. The question would be, is it a separate buffer, or a part of another buffer, or what? In Rmail currently it is possible to type e and edit a message. Right now we do this through editing the buffer of the RMAIL file. With better MIME support, this may have to be implemented differently, but I hope we can keep it working somehow. If we copy the message into another buffer for viewing, that tends to lead to complications of the situation, because there are multiple buffers instead of just one. We could try adding features to hide that, or we could expose it and not hide anything.