Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added support for exporting comments inside code blocks.
- Loading branch information
Showing
6 changed files
with
90 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
<h1 class="title">Code Comment</h1> | ||
<p>I need to be able to export things that look like org-mode comments inside of code blocks, like this:</p> | ||
<pre> | ||
|
||
#+TITLE: orgmode_parser.org | ||
#+AUTHOR: | ||
#+EMAIL: brian@BRIAN-DESK | ||
#+DATE: 2009-12-29 Tue | ||
#+DESCRIPTION: | ||
#+KEYWORDS: | ||
#+LANGUAGE: en | ||
#+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t | ||
#+OPTIONS: TeX:t LaTeX:nil skip:nil d:nil todo:t pri:nil tags:not-in-toc | ||
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js | ||
#+EXPORT_SELECT_TAGS: export | ||
#+EXPORT_EXCLUDE_TAGS: noexport | ||
#+LINK_UP: | ||
#+LINK_HOME: | ||
</pre> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
* Code Comment | ||
|
||
I need to be able to export things that look like org-mode comments | ||
inside of code blocks, like this: | ||
|
||
#+BEGIN_EXAMPLE | ||
#+TITLE: orgmode_parser.org | ||
#+AUTHOR: | ||
#+EMAIL: brian@BRIAN-DESK | ||
#+DATE: 2009-12-29 Tue | ||
#+DESCRIPTION: | ||
#+KEYWORDS: | ||
#+LANGUAGE: en | ||
#+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t | ||
#+OPTIONS: TeX:t LaTeX:nil skip:nil d:nil todo:t pri:nil tags:not-in-toc | ||
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js | ||
#+EXPORT_SELECT_TAGS: export | ||
#+EXPORT_EXCLUDE_TAGS: noexport | ||
#+LINK_UP: | ||
#+LINK_HOME: | ||
#+END_EXAMPLE | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
* Metadata, etc. | ||
|
||
I normally filter out things that look like metadata. Can't do it any | ||
more. I need to see all of the following: | ||
|
||
#+BEGIN_EXAMPLE | ||
* DONE Handle inline formatting | ||
CLOSED: [2009-12-26 Sat 21:41] | ||
:PROPERTIES: | ||
:ARCHIVE_TIME: 2009-12-26 Sat 22:16 | ||
:ARCHIVE_FILE: ~/brians-brain/content/projects/orgmode_parser.org | ||
:ARCHIVE_OLPATH: <%= @page.title %>/Future Development | ||
:ARCHIVE_CATEGORY: orgmode_parser | ||
:ARCHIVE_TODO: DONE | ||
:END: | ||
|
||
I still need to handle: | ||
|
||
- [ ] =Inline code= | ||
|
||
How does the =emacs= HTML parser handle *inline* formatting? Ah, | ||
it looks like it defines everything in =org-emphasis-alist= (line | ||
2855 of =org.el=). | ||
|
||
And then look at =org-emphasis-regexp-components=, line 2828 of | ||
=org.el=. It looks like they just use a crazy regexp for inline | ||
formatting. Which is good, because it means I can copy! | ||
|
||
|
||
#+END_EXAMPLE |