emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Josh Berry <taeric@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: Bastien <bzg@gnu.org>, Aaron Ecay <aaronecay@gmail.com>,
	emacs-orgmode@gnu.org
Subject: Re: Writing .el files for org in org?
Date: Thu, 22 May 2014 11:44:15 -0400	[thread overview]
Message-ID: <CAG9v9NmvDmavH=cA504-u0VMQnJa+g+RJUSuodhmQErV0R2R+A@mail.gmail.com> (raw)
In-Reply-To: <m2iooy2l5g.fsf@krugs.de>

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

On Thu, May 22, 2014 at 5:54 AM, Rainer M Krug <Rainer@krugs.de> wrote:

> 4) and if it is working, detangled into ob-....org
>

Apologies for jumping in as a lurker.  When you say "detangled", is there a
process for doing this?  I know that working with cweb files the tangled
output included some markers to indicate where the sections came from.
Having something like that here would be great.  I have not extensively
used this workflow for writing code, but I know I have had times where I
found it easy to try out a few small (or sometimes largish) changes in the
tangled output directly.  Having a procedure to "detangle" would be very
nice.

Thanks!

-josh

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

  parent reply	other threads:[~2014-05-22 15:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 20:21 Writing .el files for org in org? Rainer M Krug
2014-05-21 23:25 ` Aaron Ecay
2014-05-22  8:12   ` Rainer M Krug
2014-05-22  8:56   ` Bastien
2014-05-22  9:25     ` Rainer M Krug
2014-05-22  9:29       ` Bastien
2014-05-22  9:54         ` Rainer M Krug
2014-05-22 11:04           ` Bastien
2014-05-22 11:42             ` Rainer M Krug
2014-05-22 15:10               ` Bastien
2014-05-23  7:29                 ` Rainer M Krug
2014-06-02 11:22             ` John Kitchin
2014-06-02 14:00               ` Rainer M Krug
2014-07-27 21:50                 ` Bastien
2014-07-30  2:04                   ` John Kitchin
2014-05-22 15:44           ` Josh Berry [this message]
2014-05-22 18:49             ` Rainer M Krug
2014-05-22  0:30 ` Grant Rettke
2014-05-22  8:30   ` Rainer M Krug
2014-05-22 23:34     ` Grant Rettke
2014-05-27  8:45 ` Thorsten Jolitz
2014-05-27  9:07   ` Rainer M Krug

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='CAG9v9NmvDmavH=cA504-u0VMQnJa+g+RJUSuodhmQErV0R2R+A@mail.gmail.com' \
    --to=taeric@gmail.com \
    --cc=Rainer@krugs.de \
    --cc=aaronecay@gmail.com \
    --cc=bzg@gnu.org \
    --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).