From mboxrd@z Thu Jan 1 00:00:00 1970 From: Taru Karttunen Subject: Re: cannot edit two source code examples simultaneously Date: Mon, 18 May 2009 09:27:26 +0300 Message-ID: <1242627915-sup-1869@oz.taruti.net> References: <20090515053802.GE13183@hplhtang1> <4FBDF50D-609C-4816-952C-54A83854F528@gmail.com> <87hbzjmyfy.fsf@stats.ox.ac.uk> <1242625016-sup-9305@oz.taruti.net> <871vqnj65s.fsf@stats.ox.ac.uk> Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M5wJz-0001oS-0r for emacs-orgmode@gnu.org; Mon, 18 May 2009 02:27:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M5wJu-0001kV-9z for emacs-orgmode@gnu.org; Mon, 18 May 2009 02:27:34 -0400 Received: from [199.232.76.173] (port=59771 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5wJt-0001kK-SH for emacs-orgmode@gnu.org; Mon, 18 May 2009 02:27:29 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:58449 helo=mail.cs.helsinki.fi) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M5wJt-00089J-Fa for emacs-orgmode@gnu.org; Mon, 18 May 2009 02:27:29 -0400 In-Reply-To: <871vqnj65s.fsf@stats.ox.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Excerpts from Dan Davison's message of Mon May 18 09:07:11 +0300 2009: > I think it's more complicated than that: source code loss is also the > motivation for doing something like this. If you are editing the code in > the *Org Edit Src* buffer, and get distracted, you may return to the org > buffer and mistakenly decide that it contains the latest content. I've > done that two or three times in the last couple of days, resulting in > lost work. That mistake cannot be made so easily when there is only ever > one current copy of the code. If you close emacs without C-c ', or your > laptop power runs out, then I agree that is bad, but I thought perhaps > there might be a good solution along these lines. Maybe an alternative > would be to maintain a work-in-progress message along with the > out-of-date code? How about this - set the source code with a special overlay/property when editing it. The property could turn the code into a link to the buffer and set it read-only. - Taru Karttunen