From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: a couple tangle questions (tangle a single block, comment syntax)
Date: Thu, 11 Oct 2018 08:06:38 -0400 [thread overview]
Message-ID: <CAJ51ETozYj_TBFQXBxdPve9RTcCVKq5ZhsZgk0SDOCwOKVYYpw@mail.gmail.com> (raw)
In-Reply-To: <m2h8htc5qb.fsf@charm.irisa.fr>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
Do you mean interactively? With org-babel-tangle you can:
With one universal prefix argument, only tangle the block at point.
When two universal prefix arguments, only tangle blocks for the
tangle file of the block at point.
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Thu, Oct 11, 2018 at 3:18 AM Alan Schmitt <alan.schmitt@polytechnique.org>
wrote:
> Hello,
>
> I'm moving my configuration files to an org file to be tangled, and I
> have a couple questions.
>
> First, is there a command to tangle a single block, or blocks in a
> subtree?
>
> Second, I like to have the :comments link option in my tangled files (to
> reference where they were tangled from), but some files do not have an
> emacs mode, so I use a "config" source block. For these files, org does
> not know the syntax of comments, so it asks me for it. Can I specify the
> syntax for comments in the header of the source block?
>
> Thanks a lot,
>
> Alan
>
> --
> OpenPGP Key ID : 040D0A3B4ED2E5C7
> Monthly Athmospheric CO₂, Mauna Loa Obs. 2018-09: 405.51, 2017-09: 403.37
>
[-- Attachment #2: Type: text/html, Size: 1928 bytes --]
next prev parent reply other threads:[~2018-10-11 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 7:17 a couple tangle questions (tangle a single block, comment syntax) Alan Schmitt
2018-10-11 12:06 ` John Kitchin [this message]
2018-10-11 14:12 ` Alan Schmitt
2018-10-11 14:30 ` Alan Schmitt
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=CAJ51ETozYj_TBFQXBxdPve9RTcCVKq5ZhsZgk0SDOCwOKVYYpw@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=alan.schmitt@polytechnique.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).