emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Taru Karttunen <taruti@taruti.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: cannot edit two source code examples simultaneously
Date: Mon, 18 May 2009 09:27:26 +0300	[thread overview]
Message-ID: <1242627915-sup-1869@oz.taruti.net> (raw)
In-Reply-To: <871vqnj65s.fsf@stats.ox.ac.uk>

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

  reply	other threads:[~2009-05-18  6:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  5:38 cannot edit two source code examples simultaneously Hsiu-Khuern Tang
2009-05-16 17:39 ` Carsten Dominik
2009-05-17 17:28   ` Dan Davison
2009-05-18  5:38     ` Taru Karttunen
2009-05-18  6:07       ` Dan Davison
2009-05-18  6:27         ` Taru Karttunen [this message]
2009-05-18 10:12           ` Carsten Dominik
2009-05-18 15:23           ` Carsten Dominik
2009-05-18 17:40             ` Dan Davison
2009-05-18 10:48     ` Carsten Dominik
2009-05-19  0:32   ` Hsiu-Khuern Tang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1242627915-sup-1869@oz.taruti.net \
    --to=taruti@taruti.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).