emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Using orgmode to take "inline notes" for research
Date: Wed, 06 Apr 2011 10:42:14 -0600	[thread overview]
Message-ID: <871v1f1gd5.fsf@gmail.com> (raw)
In-Reply-To: <BANLkTinSBs1G22BMjgrZGVztnnzEgGieOA@mail.gmail.com> (John Hendy's message of "Wed, 6 Apr 2011 11:09:08 -0500")

>>
>> Using the following code, you can control whether notes enclosed in
>> "notes" blcks will be exported by changing the value of the
>> *export-my-notes* variable, when it is nil your notes will not be
>> exported, when t they will be exported as quoted text.
>>
>> #+begin_src emacs-lisp
>>  (defvar *export-my-notes* nil)
>>
>>  (defun org-exp-block-process-notes (body &rest headers)
>>    (if *export-my-notes*
>>        (format "\n#+begin_quote\n%s\n#+end_quote\n" body)
>>        ""))
>>
>>  (org-export-blocks-add-block '(notes org-exp-block-process-notes nil))
>> #+end_src
>
> So, do I put my notes between the end of the (defun org-exp...) and
> (org-export-blocks...)?
>

No,

sorry I should have been more clear, add the above elisp to your Emacs
initialization (or just evaluate it in your scratch buffer), and then
after doing so whenever you export a buffer containing a begin/end_notes
block, the block will be removed during export.  Then later if you want
to export the notes along with the article text, you can evaluate the
following elisp code to set *export-my-notes* to t, and re-export to
find the notes embedded in the exported document.

#+begin_src emacs-lisp
  (setq *export-my-notes* t)
#+end_src

Hope this clears things up -- Eric

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2011-04-06 16:42 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06  2:02 Using orgmode to take "inline notes" for research John Hendy
2011-04-06  3:21 ` Jeff Horn
2011-04-06 10:33   ` Sébastien Vauban
2011-04-06 16:33   ` John Hendy
2011-04-06 16:47     ` John Hendy
2011-04-06 17:27       ` Samuel Wales
2011-04-06 18:08         ` John Hendy
2011-04-06 18:16           ` Samuel Wales
2011-04-06 18:16             ` John Hendy
2011-04-06 19:11     ` Mark Elston
2011-04-07  4:19     ` Jeff Horn
2011-04-07  9:20       ` Sébastien Vauban
2011-04-07 15:26         ` John Hendy
2011-04-07 15:33           ` Jeff Horn
2011-04-07 15:48             ` John Hendy
2011-04-08 20:53               ` Sébastien Vauban
2011-04-12 16:30                 ` John Hendy
2011-04-12 16:39                   ` John Hendy
2011-04-12 17:57                     ` John Hendy
2011-04-25 19:51                       ` Sébastien Vauban
2011-04-26 13:07                         ` John Hendy
2011-04-12 18:20                   ` Eric S Fraga
2011-04-12 18:56                     ` John Hendy
2011-04-17 23:36                     ` Rasmus
2011-04-20 17:46                       ` Eric S Fraga
2011-04-16  7:24                   ` Nicolas Goaziou
2011-04-07 12:39       ` Nicolas Goaziou
2011-04-06  3:32 ` Eric Schulte
2011-04-06  4:10   ` Erik Iverson
2011-04-06  5:02     ` Eric Schulte
2011-04-06 16:16       ` John Hendy
2011-04-07  5:33         ` Eric S Fraga
2011-04-07 16:10           ` John Hendy
2011-04-08 18:18             ` Eric S Fraga
2011-04-08 20:08               ` John Hendy
2011-04-06 16:11     ` John Hendy
2011-04-06 16:09   ` John Hendy
2011-04-06 16:42     ` Eric Schulte [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-06  3:52 Rustom Mody

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=871v1f1gd5.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@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).