From: Joon Ro <joon.ro@outlook.com>
To: Xebar Saram <zeltakc@gmail.com>, org mode <emacs-orgmode@gnu.org>
Subject: Re: Can one tangle only the current blocks under header ?
Date: Sat, 30 Jul 2016 13:38:42 -0500 [thread overview]
Message-ID: <COL125-W526284B29B2899C2963957EB020@phx.gbl> (raw)
In-Reply-To: <CAOQHXPqZomWipdL3sWZaWLHkny8WZ_=aj1nWoTMMLNg13K=KmQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
can one tangle only the current blocks under header or can you only tangle the whole file?the issue is again for dotfiles managed by org that these files are not proper org babel languages and look like this:
#+BEGIN_SRC conf :mkdirp yes :tangle ~/.config/mpv/mpv.confsoftvol-max=600 #+END_SRC
the manual (http://orgmode.org/manual/Extracting-source-code.html) only shows how to tangle the whole file
any ideas?
If you read the help for org-babel-tangle:
With one universal prefix argument, only tangle the block at point.When two universal prefix arguments, only tangle blocks for thetangle file of the block at point.
So if you do c-u first before org-babel-tangle, it will only tangle the code block at point.I use this a lot so I have the following in my init file:
(defun org-babel-tangle-block() (interactive) (let ((current-prefix-arg '(4))) (call-interactively 'org-babel-tangle)))
(eval-after-load "org" '(progn (define-key org-mode-map (kbd "C-c b") 'org-babel-tangle-block)))
So I can just do C-c b and it will just tangle the code block at point.
And I agree with you I with the manual (http://orgmode.org/manual/Extracting-source-code.html) has this information.
Hope this helps,Joon
[-- Attachment #2: Type: text/html, Size: 4090 bytes --]
next prev parent reply other threads:[~2016-07-30 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 17:55 Can one tangle only the current blocks under header ? Xebar Saram
2016-07-30 18:38 ` Joon Ro [this message]
2016-07-31 14:34 ` Grant Rettke
2016-08-02 12:26 ` Xebar Saram
2016-08-02 15:05 ` Joon Ro
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=COL125-W526284B29B2899C2963957EB020@phx.gbl \
--to=joon.ro@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=zeltakc@gmail.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).