From: Avdi Grimm <groups@inbox.avdi.org>
To: Neeum Zawan <mailinglists@nawaz.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Literate Programming - Continue a Source Block?
Date: Fri, 10 Jun 2011 00:55:25 -0400 [thread overview]
Message-ID: <BANLkTin4CfKQJ_-hp5XenPssp5660_DkLQ@mail.gmail.com> (raw)
In-Reply-To: <877h8wj9za.fsf@fester.com>
On Wed, Jun 8, 2011 at 5:20 PM, Neeum Zawan <mailinglists@nawaz.org> wrote:
> n this case, yes. In a real programming project, it could be a number
> of them. For example, I may have a code block dedicated to
> imports/includes which I want to be on the top of the file - and I may
> have to append to that when adding a new feature.
Ooh! Ooh! Me too!
I was just wanting this the other day. I wanted to be able to do:
#+srcname: requires
#+begin_src ruby
require 'library_a'
#+end_src
...
#+srcname: requires
#+begin_src ruby
require 'library_b'
#+end_src
And then tie it all together with:
#+begin_src ruby :tangle foo.rb
<<requires>>
#+end
But no such luck. <<requires>> just picked up the most recent block
with that srcname, IIRC.
--
Avdi Grimm
http://avdi.org
next prev parent reply other threads:[~2011-06-10 4:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 5:47 Literate Programming - Continue a Source Block? Neeum Zawan
2011-06-08 7:34 ` Sebastien Vauban
2011-06-08 15:20 ` Neeum Zawan
2011-06-08 19:40 ` Eric Schulte
2011-06-08 21:20 ` Neeum Zawan
2011-06-10 4:55 ` Avdi Grimm [this message]
2011-06-10 19:09 ` Eric Schulte
2011-06-10 19:27 ` Achim Gratz
2011-06-10 20:00 ` Eric Schulte
2011-06-12 8:32 ` Achim Gratz
2011-06-13 22:04 ` Eric Schulte
2011-06-14 20:48 ` Achim Gratz
2011-06-15 17:23 ` Eric Schulte
2011-06-15 21:19 ` Achim Gratz
2011-06-16 4:54 ` Eric Schulte
2011-06-16 2:35 ` Neeum Zawan
2011-06-11 1:02 ` Neeum Zawan
2011-06-11 0:44 ` Neeum Zawan
2011-06-11 20:08 ` Eric Schulte
2011-06-12 5:36 ` Neeum Zawan
2011-06-13 21:57 ` Eric Schulte
2011-06-15 5:17 ` Neeum Zawan
2011-06-15 17:27 ` Eric Schulte
2011-06-15 19:37 ` Neeum Zawan
2011-06-16 2:26 ` Eric Schulte
2011-06-17 4:30 ` Neeum Zawan
2011-06-17 4:39 ` Eric Schulte
2011-06-17 7:00 ` Sebastien Vauban
2011-06-19 23:38 ` Neeum Zawan
2011-06-16 10:14 ` Olaf.Hamann
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=BANLkTin4CfKQJ_-hp5XenPssp5660_DkLQ@mail.gmail.com \
--to=groups@inbox.avdi.org \
--cc=avdi@avdi.org \
--cc=emacs-orgmode@gnu.org \
--cc=mailinglists@nawaz.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).