From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: saving buffer with text properties Date: Sun, 3 Jun 2007 10:15:11 -0700 Message-ID: References: <87bqfxq87l.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1180890991 6323 80.91.229.12 (3 Jun 2007 17:16:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 3 Jun 2007 17:16:31 +0000 (UTC) To: "Emacs-Devel" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 03 19:16:29 2007 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 1Hutgn-0006f2-Kv for ged-emacs-devel@m.gmane.org; Sun, 03 Jun 2007 19:16:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hutgn-0008RI-5C for ged-emacs-devel@m.gmane.org; Sun, 03 Jun 2007 13:16:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hutgk-0008RD-1n for emacs-devel@gnu.org; Sun, 03 Jun 2007 13:16:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hutgi-0008Qx-Hd for emacs-devel@gnu.org; Sun, 03 Jun 2007 13:16:20 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hutgi-0008Qs-BX for emacs-devel@gnu.org; Sun, 03 Jun 2007 13:16:20 -0400 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Hutgi-0005TS-0d for emacs-devel@gnu.org; Sun, 03 Jun 2007 13:16:20 -0400 Original-Received: from rgmgw3.us.oracle.com (rgmgw3.us.oracle.com [138.1.186.112]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l53HGHDg017322 for ; Sun, 3 Jun 2007 12:16:17 -0500 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by rgmgw3.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l53HGGfX003380 for ; Sun, 3 Jun 2007 11:16:16 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-81-137.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 2796146421180890924; Sun, 03 Jun 2007 10:15:24 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <87bqfxq87l.fsf@stupidchicken.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: Linux 2.4-2.6 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:72124 Archived-At: > > But the per-file information about applied text properties > > needs to be saved with the file, no? > > That would interfere with third-party programs, such as other text > editors, that want to edit the file. Perhaps you're right about that. I don't know much about this stuff. We already provide metadata in the form of local-variable declarations in comments, but I recognize that this should also be applicable to files that aren't necessarily code and don't necessarily have a comment syntax. (Besides, trying to record this stuff in comments would likely be a nightmare, if not also problematic.) > > Or did you mean that desktop would save a list of files and their text > > properties (including property values and locations)? > > Basically. Desktop should provide hooks that other packages (such as > major modes) can use, i.e. a major mode should be able to tell desktop > "save the following data when closing this file, then run this > function with that data when the file is reopened". That sounds reasonable to me, from the little I know of this. As I mentioned to Thi, this is not something that I expect to work on, so I'll generally bow out of trying to design and implement this. I was really just trying to find out if something already existed, or was planned, which I might be able to take advantage of for my highlighting code.