From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: cannot edit two source code examples simultaneously Date: Mon, 18 May 2009 12:12:55 +0200 Message-ID: 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> <1242627915-sup-1869@oz.taruti.net> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M5zqC-000354-2D for emacs-orgmode@gnu.org; Mon, 18 May 2009 06:13:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M5zq7-00032q-96 for emacs-orgmode@gnu.org; Mon, 18 May 2009 06:13:03 -0400 Received: from [199.232.76.173] (port=33538 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5zq7-00032g-45 for emacs-orgmode@gnu.org; Mon, 18 May 2009 06:12:59 -0400 Received: from mail-ew0-f162.google.com ([209.85.219.162]:60490) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M5zq6-00068O-NH for emacs-orgmode@gnu.org; Mon, 18 May 2009 06:12:58 -0400 Received: by ewy6 with SMTP id 6so4028291ewy.42 for ; Mon, 18 May 2009 03:12:58 -0700 (PDT) In-Reply-To: <1242627915-sup-1869@oz.taruti.net> 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: Taru Karttunen Cc: emacs-orgmode On May 18, 2009, at 8:27 AM, Taru Karttunen wrote: > 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. This sounds like a good idea. However, it seems that putting a read- only property using an overlay does not work - does anyone know why? I'd prefer an overlay over text properties here.... - Carsten