From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Davison Subject: Re: cannot edit two source code examples simultaneously Date: Mon, 18 May 2009 13:40:39 -0400 Message-ID: <87octqtilk.fsf@stats.ox.ac.uk> 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> <1B7DED06-CFA7-481D-982A-B077A642205D@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M66pX-0008Ml-2a for emacs-orgmode@gnu.org; Mon, 18 May 2009 13:40:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M66pR-0008JN-NB for emacs-orgmode@gnu.org; Mon, 18 May 2009 13:40:50 -0400 Received: from [199.232.76.173] (port=46268 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M66pR-0008JB-Gk for emacs-orgmode@gnu.org; Mon, 18 May 2009 13:40:45 -0400 Received: from markov.stats.ox.ac.uk ([163.1.210.1]:38419) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M66pQ-0001QA-W7 for emacs-orgmode@gnu.org; Mon, 18 May 2009 13:40:45 -0400 In-Reply-To: <1B7DED06-CFA7-481D-982A-B077A642205D@gmail.com> (Carsten Dominik's message of "Mon, 18 May 2009 17:23:48 +0200") 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: Carsten Dominik Cc: emacs-orgmode Org-Mode Carsten Dominik writes: > 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. > > OK, the source code in the Org buffer is now highlighted while > being edited, and you can click on it to go back to the > editing buffer. I hope that does solve you problems, Dan? Hi Carsten, I've given it a quick go and it seems like a very nice solution. Thanks a lot. Dan > > It is not yet read-only, but this feels like an Emacs bug, because I > do set read-only in the overlay. > >> >> - Taru Karttunen >> >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode