From: Jambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Composing letters using Org mode and the LaTeX isodoc class
Date: Wed, 08 Sep 2010 10:09:33 +0530 [thread overview]
Message-ID: <81lj7cyhkq.fsf@gmail.com> (raw)
In-Reply-To: <87iq2huk7u.fsf@gmail.com> (Eric Schulte's message of "Tue, 07 Sep 2010 18:56:05 -0600")
Eric
Thanks for the changes. I believe I need not work (or for all practical
purposes set aside) working on letter writing support.
Jambu>>> Btw, your approach set me thinking. I think there is a strong
Jambu>>> case for making headlines act as babel srcnames with their body
Jambu>>> providing content for noweb expansion [3]. This behaviour could
Jambu>>> be controlled by a buffer local variable.
Is this suggestion considered and set aside or overlooked? Read on down
below.
Jambu>>> Wondering how babel treats srcnames? Can there be spaces? Is
Jambu>>> upper and lower cases treated one and the same ...
Eric> Spaces are now allowed, I'm honestly not sure that it will
Eric> successfully distinguish between upper and lower cases in code
Eric> block names (all of mine are lower-case)
Good.
Honoring spaces would be a pre-requisite if one were to allow org's
headlines as implicit srcnames.
Question on case-handling was intended not as a feature request but more
on clarity of the behaviour.
Eric> I've just implemented export of org code blocks to ascii, latex or html,
Eric> so the following should now (if I understood) allow the tangling
Eric> behavior you've described
Eric>
Eric> ** tangle org-mode block
Eric> #+source: org-list
Eric> #+begin_src org :results latex
Eric> - one
Eric> - two
Eric> - three
Eric> #+end_src
Eric>
Eric> #+begin_src emacs-lisp :tangle yes :noweb yes
Eric> "
Eric> <<org-list()>>
Eric> "
Eric> #+end_src
Eric>
Eric> tangles to
Eric>
Eric>
Eric> "
Eric> \begin{itemize}
Eric> \item two
Eric> \item three
Eric> \end{itemize}
Eric>
Eric>
Eric> "
Eric>
Eric> note that the () on the end of the code block name in the noweb syntax
Eric> means to insert the results of evaluating the code block (in this case
Eric> latex) rather than the body of the code block itself.
If babel supports headlines as srcnames, without requiring additional
begin/end directives one could just write,
* org-list
- one
- two
- three
#+begin_src emacs-lisp :tangle yes :noweb yes
"
<<org-list(:fmt latex)>>
"
#+end_src
and achieve similar results.
Based on my earlier efforts at letter-writing, I have the following
observation.
Letters have a To address and they could be pulled from bbdb. So one
could say,
* To
[[a bbdb link]]
#+begin_src emacs-lisp :tangle yes :noweb yes
"
<<To(:fmt custom)>>
"
#+end_src
The string custom could be a elisp form or a function pointer that takes
the body of the headline as an argument and does the needful.
Specifically in the above example, 'custom' handler would visit the bbdb
record, fetch the address and return the formatted address (with line
breaks etc etc) as the noweb expansion. [Custom handler would be
implemented by the user himself]
Any thoughts on how this could be achieved ...
Jambunathan K.
next prev parent reply other threads:[~2010-09-08 4:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 11:36 Composing letters using Org mode and the LaTeX isodoc class Sébastien Vauban
2010-09-07 18:46 ` Jambunathan K
2010-09-07 19:45 ` Sébastien Vauban
2010-09-08 0:56 ` Eric Schulte
2010-09-08 1:52 ` Thomas S. Dye
2010-09-08 4:39 ` Jambunathan K [this message]
2010-09-08 11:48 ` Sébastien Vauban
2010-09-08 15:15 ` Eric Schulte
2010-09-08 16:22 ` [BABEL][PROPOSAL] headlines as executable srcnames Jambunathan K
2010-09-08 21:30 ` Sébastien Vauban
2010-09-09 15:38 ` Jambunathan K
2010-09-09 16:30 ` Jambunathan K
2010-09-10 4:51 ` Jambunathan K
2010-09-20 4:03 ` Eric Schulte
2010-09-20 7:39 ` Jambunathan K
2010-09-20 4:15 ` Eric Schulte
2010-09-08 11:45 ` Composing letters using Org mode and the LaTeX isodoc class Sébastien Vauban
2010-09-08 15:38 ` Eric Schulte
2010-09-08 21:26 ` Sébastien Vauban
2010-09-10 8:51 ` Eric S Fraga
2010-09-10 9:13 ` Sébastien Vauban
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=81lj7cyhkq.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.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).