emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: edit-src on read-only files
Date: Sat, 09 Feb 2013 13:58:50 +0100	[thread overview]
Message-ID: <87bobtabjp.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87a9refjuc.fsf@ucl.ac.uk

Hi all,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Greg Minshall <minshall@umich.edu> writes:
>
>> hi.  i use RCS on my .org files.  it's happened to me more than once (>1
>> ==> "shame on me") that i've entered "C-c '" on a read-only .org file,
>> spent some time editing the source code fragment, then done "C-c '",
>> only to lose my edits, as the original buffer was read-only.
>
> Yes, I share your shame... this has happened to me more than once as
> well.  Thank you for the simple solution which I have installed!
>

I have installed that as well.  Very nice thanks.

> But you are correct that org should check for this case.  Or at least
> provide a mechanism for saving the source code block elsewhere...

Seconded.

On a related note:  I'd also love to see the changes in the
source code buffers be autosaved in the org file.  I've lost some big
edits already due to power loss on my (old) laptop.

Cheers,
Andreas

  reply	other threads:[~2013-02-09 12:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 14:52 edit-src on read-only files Greg Minshall
2013-02-08 23:48 ` Eric S Fraga
2013-02-09 12:58   ` Andreas Leha [this message]
2013-02-16 10:36     ` Bastien
2013-02-27 20:40       ` Andreas Leha
2013-03-02 15:11         ` Bastien
2013-03-18 20:36           ` Andreas Leha
2013-03-18 22:22           ` Andreas Leha
2013-02-11 15:22 ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2013-02-12  0:17 Greg Minshall

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=87bobtabjp.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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).