How would you export one headline every time that you tangle the file?

How would you export one headline every time that you tangle the file?

[Grant Rettke]

Good afternoon,

I've got an org file. It has a bunch of headlines. There is on
headline names README.

I want to do something every time I tangle the file. I want to:

- Go to that headline
- Select set the region to the contents of that headline (org-mark-subtree)
- Export the contents using the Github Flavored Markup to the file README.md.

I figured that I would figure out how to do all of this using Elisp,
write a function, and add that function
to the org-babel-post-tangle hook. I feel OK about that.

I haven't started yet because I started to wonder if doing this sort of thing
is just "built into" Org-Mode and coding it up would be a poor use of time. This
seems like something that I can't be the first one to be doing this.

So, I wondered, how would you do that? I don't want to recode
something that Org-Mode
already does just because I don't know all of Org-Mode.

Sincerely,

Grant Rettke
--
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
“All creativity is an extended form of a joke.” --Kay
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson

Re: How would you export one headline every time that you tangle the file?

[Charles C. Berry]

On Wed, 12 Aug 2015, Grant Rettke wrote:

> Good afternoon,
>
> I've got an org file. It has a bunch of headlines. There is on
> headline names README.
>
> I want to do something every time I tangle the file. I want to:
>
> - Go to that headline
> - Select set the region to the contents of that headline (org-mark-subtree)
> - Export the contents using the Github Flavored Markup to the file README.md.
>

If this is a one-off, I'd write a babel block like this and put it under 
the headline of that subtree:

#+NAME: tangle-and-export-readme
#+BEGIN_SRC emacs-lisp :tangle no :exports none
(org-babel-tangle)
(require 'ox-gfm)
(org-export-to-file 'gfm "README.md" nil t)
#+END_SRC


Then when you want to tangle,

C-c C-v g tangle-and-export-readme RET C-c C-c y

will do it. (Assuming contrib is on the load path, of course.)

You can use TAB completion with `C-c C-v g'.

HTH,

Chuck

Re: How would you export one headline every time that you tangle the file?

[John Kitchin]

I also do something like this for scientific manuscripts, but I usually put it in a heading at the
end and tag the heading :noexport:. that gives me some more flexibility
to have multiple steps, some notes, etc...

e.g.

* build  :noexport:

#+BEGIN_SRC emacs-lisp :tangle no :exports none
(org-babel-tangle)
(require 'ox-gfm)
(org-export-to-file 'gfm "README.md" nil t)
#+END_SRC

Charles C. Berry writes:

> On Wed, 12 Aug 2015, Grant Rettke wrote:
>
>> Good afternoon,
>>
>> I've got an org file. It has a bunch of headlines. There is on
>> headline names README.
>>
>> I want to do something every time I tangle the file. I want to:
>>
>> - Go to that headline
>> - Select set the region to the contents of that headline (org-mark-subtree)
>> - Export the contents using the Github Flavored Markup to the file README.md.
>>
>
> If this is a one-off, I'd write a babel block like this and put it under
> the headline of that subtree:
>
> #+NAME: tangle-and-export-readme
> #+BEGIN_SRC emacs-lisp :tangle no :exports none
> (org-babel-tangle)
> (require 'ox-gfm)
> (org-export-to-file 'gfm "README.md" nil t)
> #+END_SRC
>
>
> Then when you want to tangle,
>
> C-c C-v g tangle-and-export-readme RET C-c C-c y
>
> will do it. (Assuming contrib is on the load path, of course.)
>
> You can use TAB completion with `C-c C-v g'.
>
> HTH,
>
> Chuck

--
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