all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Grant Rettke <gcr@wisdomandwonder.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: [babel] How to make source blocks immutable whil editing org files in Org mode in Emacs
Date: Mon, 24 Mar 2014 18:01:53 -0500	[thread overview]
Message-ID: <CAAjq1mdv8Fgp_1zUz2SicqOM5m3x2HOkiF-eTJwwLCGaamX+hg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Hi,

Context:

Just logged about 60 hours doing a literate programming project with
Org and elisp. Calling org-edit-special to break out into my customized
editing
environment has worked quite well. There, Smartparens (strict mode) or
Paredit keep parentheses
balanced. Sometimes I get lazy though and want to make a change to the
source
block and invariable screw up the parentheses and break my system.

Desire:

I would like to set a flag that disallows any editing of source blocks
whilst in org mode.
Obviously one could still see the code, just not modify it. Sure,
discipline would also be an
options but most bad edits seem like easy ones, but if it were easy you
wouldn't make it in the
first place.

Research:

Read http://orgmode.org/guide/Working-With-Source-Code.html and didn't find
that kind of feature.
Googled and didn't find a fix.

Question:

How have you folks dealt with this? Is there a solution out there? Would
you like such a thing?

Regards,

-- 
Grant Rettke | ACM, AMA, COG, IEEE
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates

[-- Attachment #2: Type: text/html, Size: 1713 bytes --]

                 reply	other threads:[~2014-03-24 23:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=CAAjq1mdv8Fgp_1zUz2SicqOM5m3x2HOkiF-eTJwwLCGaamX+hg@mail.gmail.com \
    --to=gcr@wisdomandwonder.com \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.