emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Grant Rettke <gcr@wisdomandwonder.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: How to collect multiple source blocks with the same name at the same level
Date: Wed, 5 Mar 2014 16:24:56 -0600	[thread overview]
Message-ID: <CAAjq1mcgTO_Etfk8L1EUkoU2KH2rSfGXpS92FK+fZiQpxu9ZpQ@mail.gmail.com> (raw)
In-Reply-To: <m2mwh4iauq.fsf@tsdye.com>

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

Exactly I'm doing a

#+BEGIN_SRC emacs-lisp :tangle .emacs.el :noweb tangle

What I'm aiming for is the case where you have lots of code blocks
interspersed
with written language... and want them to accumulate under a single
identifier. I will keep
digging.


On Wed, Mar 5, 2014 at 3:39 PM, Thomas S. Dye <tsd@tsdye.com> wrote:

> Aloha Grant,
>
> I'm not certain what you're after.
>
> From the Org mode manual:
>
>      * outline header
>        :PROPERTIES:
>        :header-args:    :cache yes
>        :END:
>
> Perhaps
>
>   :header-args: :tangle myfile.el
>
> All the best,
> Tom
>
> Grant Rettke <gcr@wisdomandwonder.com> writes:
>
> > Hi,
> >
> > My goal is to intersperse code blocks with comments about them like this:
> >
> > ==================================
> > Menu bars are not required [fn:38]
> > #+NAME: uxo-decision1
> > #+BEGIN_SRC emacs-lisp
> > (menu-bar-mode 0)
> > #+END_SRC
> >
> > Don't need auto-save
> > #+NAME: uxo-decision2
> > #+BEGIN_SRC emacs-lisp
> > (disable-auto-save)
> > #+END_SRC
> > ==================================
> > And replace it with something like this:
> > ==================================
> > *** Setup
> >   :PROPERTY:
> >   :name: uxo-decision
> >   :END
> >
> > Menu bars are not required [fn:38]
> > #+BEGIN_SRC emacs-lisp
> > (menu-bar-mode 0)
> > #+END_SRC
> >
> > Don't need auto-save
> > #+BEGIN_SRC emacs-lisp
> > (disable-auto-save)
> > #+END_SRC
> > ==================================
> >
> > Basically I'm going through a config file and want write a lot but to be
> > able to refer to all of the
> > snippets as a single ended and tangle them accordingly. What is the right
> > way to do this?
> >
> > My apologies for having to ask this; for some bizarre reason I am not
> > finding the example
> > to do this though I know I have read it.
> >
> > Regards,
> >
> > --
> > Grant Rettke | ACM, AMA, COG, IEEE
> > gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
> > “Wisdom begins in wonder.” --Socrates
> > ((λ (x) (x x)) (λ (x) (x x)))
> > “Life has become immeasurably better since I have been forced to stop
> > taking it seriously.” --Thompson
> > Hi,
> >
> > My goal is to intersperse code blocks with comments about them like
> > this:
> >
> > ==================================
> > Menu bars are not required [fn:38]
> > #+NAME: uxo-decision1
> > #+BEGIN_SRC emacs-lisp
> > (menu-bar-mode 0)
> > #+END_SRC
> >
> > Don't need auto-save
> > #+NAME: uxo-decision2
> > #+BEGIN_SRC emacs-lisp
> > (disable-auto-save)
> > #+END_SRC
> > ==================================
> > And replace it with something like this:
> > ==================================
> > *** Setup
> > :PROPERTY:
> > :name: uxo-decision
> > :END
> >
> > Menu bars are not required [fn:38]
> > #+BEGIN_SRC emacs-lisp
> > (menu-bar-mode 0)
> > #+END_SRC
> >
> > Don't need auto-save
> > #+BEGIN_SRC emacs-lisp
> > (disable-auto-save)
> > #+END_SRC
> > ==================================
> >
> > Basically I'm going through a config file and want write a lot but to
> > be able to refer to all of the
> > snippets as a single ended and tangle them accordingly. What is the
> > right way to do this?
> >
> > My apologies for having to ask this; for some bizarre reason I am not
> > finding the example
> > to do this though I know I have read it.
> >
> > Regards,
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>



-- 
Grant Rettke | ACM, AMA, COG, IEEE
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson

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

  reply	other threads:[~2014-03-05 22:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 21:14 How to collect multiple source blocks with the same name at the same level Grant Rettke
2014-03-05 21:35 ` Samuel Wales
2014-03-05 22:23   ` Grant Rettke
2014-03-05 21:39 ` Thomas S. Dye
2014-03-05 22:24   ` Grant Rettke [this message]
2014-03-05 22:30     ` Grant Rettke
2014-03-05 22:41 ` Aaron Ecay
2014-03-05 22:45   ` Aaron Ecay
2014-03-05 23:03   ` Grant Rettke

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=CAAjq1mcgTO_Etfk8L1EUkoU2KH2rSfGXpS92FK+fZiQpxu9ZpQ@mail.gmail.com \
    --to=gcr@wisdomandwonder.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \
    /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).