maybe there could be an on-by-default variable called org-warn-when-editing-src-block-in-org-buffer, or make the text readonly, etc.
making this on-by-default would seem to create another discussion about things being on-by-default :) however, if fontification is on by default, then this should also be on by default, since fontification causes the mistaken in-org-buffer edits that Richard points out, which seems reasonable to want to prevent systematically. I've done this myself a few times. On Mon, Sep 6, 2010 at 12:59 PM, Richard Riley <rile...@gmail.com> wrote: > Eric S Fraga <ucec...@ucl.ac.uk> writes: > >> On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison <davi...@stats.ox.ac.uk> >> wrote: >>> >>> I've just pushed changes which mean that Org now fontifies code in code >>> blocks. Currently, this is turned on by default, so it would be helpful >>> if people could report any problems, and opinions as to whether it >>> should be on or off by default. >> >> [...] >> >> This is brilliant! Works very well on my notebook (with small code >> blocks as that's all I tend to have). Many thanks! > > Without wanting to rock the boat I think its safer to have this disabled > by default. I cant tell you how many times I thought I was in the LISP > buffer and ended up making a mess since this enhancement was added. I > realise I can configure it myself but possibly the more conservative > "stick with old default" is better? It IS a nice feature when in more > capable hands than mine ;) What next? nxhtml integration and live > editing inside the src blocks? > > > > > > _______________________________________________ > Emacs-orgmode mailing list > Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
