From: Greg Minshall <minshall@umich.edu>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How do you name your code blocks?
Date: Tue, 16 Feb 2021 07:53:12 +0300 [thread overview]
Message-ID: <1417212.1613451192@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Mon, 15 Feb 2021 14:18:17 -0500." <87wnv9b0na.fsf@gmail.com>
Rodrigo,
i guess part of the answer depends on why you are naming your code
blocks. for me, the main reason is for <<noweb>>. another is so that
when org-mode asks me if it should run a block, it has a name to tell me
to help in my decision-making.
for <<noweb>>, there is noweb-ref header argument (see manual). i don't
know if that might be of help. it allows you to name a group of source
blocks, intended to be treated as a group.
using noweb-ref, one can also name a bunch of to-be-concatenated code
blocks as a property of a (super-) node in the tree:
----
:PROPERTIES:
:header-args+: :tangle build/package/covid.19.data/R/aggregate.R
:header-args+: :noweb-ref aggregates
:END:
----
(that sets all otherwise-un-attributed code blocks in that node, or any
sub-node, in the tree to tangle to the .R file, and to be "embeddable"
in other code via, e.g., things like this:
----
<<coplot>>
<<colean>>
<<duration>>
<<aggregates>>
<<dailies>>
----
)
hope that helps.
cheers, Greg
next prev parent reply other threads:[~2021-02-16 4:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 19:18 Rodrigo Morales
2021-02-16 4:53 ` Greg Minshall [this message]
2021-02-17 1:21 ` Rodrigo Morales
2021-02-16 12:03 ` Eric S Fraga
2021-02-17 1:27 ` Rodrigo Morales
2021-02-17 6:56 ` Greg Minshall
2021-02-17 20:31 ` Rodrigo Morales
2021-02-17 1:58 ` Kevin M. Stout
2021-02-17 9:57 ` Eric S Fraga
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=1417212.1613451192@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@gnu.org \
--cc=moralesrodrigo1100@gmail.com \
--subject='Re: How do you name your code blocks?' \
/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
Code repositories for project(s) associated with this 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).