From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Composing letters using Org mode and the LaTeX isodoc class
Date: Tue, 07 Sep 2010 18:56:05 -0600 [thread overview]
Message-ID: <87iq2huk7u.fsf@gmail.com> (raw)
In-Reply-To: <87r5h5gwxo.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Tue, 07 Sep 2010 21:45:07 +0200")
Hi,
I'll try to answer some of the Babel related portions of this discussion
below.
I look forward to any potential org->letter export this line of
investigation yields.
Best -- Eric
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Jambunathan,
>
> Jambunathan K wrote:
[...]
>> I would like to hear why you chose to go down the tangling path.
>
> For two reasons:
>
> - because I had not the hope of being able to configure the LaTeX export class
> and/or code in the right way,
>
Hmm, I don't know how complex isodoc is to configure, but I'd think that
defining a custom latex class would be simpler than tangling out LaTeX
code blocks, however maybe this will change once I've looked at and
understood an example application.
>
> - because, in a way, that's quite logical. Here and there, you define
> stuff. At the end, you just arrange them all in a way that fits well
> the LaTeX class demands.
>
> Though, it's not just copying, the way Babel actually does with snippets of
> code "à la Noweb". Hence, I really need at least the body to be in real Org
> plain code, and be automatically converted to LaTeX, so that I can make use of
> the tables, and all the Org markup.
>
> I'm sure Babel is able of that, mixing raw code with convertable code. Just
> needs more thinking.
>
I've just implemented export of org code blocks to ascii, latex or html,
so the following should now (if I understood) allow the tangling
behavior you've described
--8<---------------cut here---------------start------------->8---
** tangle org-mode block
#+source: org-list
#+begin_src org :results latex
- one
- two
- three
#+end_src
#+begin_src emacs-lisp :tangle yes :noweb yes
"
<<org-list()>>
"
#+end_src
--8<---------------cut here---------------end--------------->8---
tangles to
--8<---------------cut here---------------start------------->8---
"
\begin{itemize}
\item two
\item three
\end{itemize}
"
--8<---------------cut here---------------end--------------->8---
note that the () on the end of the code block name in the noweb syntax
means to insert the results of evaluating the code block (in this case
latex) rather than the body of the code block itself.
>
>
>> Personally I feel any sort of markup (this includes babel directives)
>> distracting.
>
> They're much less distracting as soon as they're properly highlighted.
> Question of color-theme. I can provide you (all) with mine, if you're
> interested.
>
>
>> Btw, your approach set me thinking. I think there is a strong case for
>> making headlines act as babel srcnames with their body providing content for
>> noweb expansion [3]. This behaviour could be controlled by a buffer local
>> variable.
>
> That would definitely make sense to me, at least for this particular need.
> But, maybe, there is already a parallel way to do such a thing...
>
>
>> Wondering how babel treats srcnames? Can there be spaces? Is upper and lower
>> cases treated one and the same ...
>
Spaces are now allowed, I'm honestly not sure that it will successfully
distinguish between upper and lower cases in code block names (all of
mine are lower-case), but either way I'd say it's poor style to rely on
case to distinguish between different code blocks.
Best -- Eric
>
> Being a (tiny) part-time Babel user, I wish I could easily answer such
> questions. But, as I always try to take as less risks as possible, these are
> things I never really looked at.
>
>
>> Footnotes:
>> [3] It is likely the body of the headline might be run through a custom
>> renderer (say latex, html or even emac's own comment-region) before
>> finding it's way in to the document generated by tangle.
>>
>> Thanks once again for referring me to isodoc.
>
> "When someone shares something of value with you and you benefit from it, you
> have a moral obligation to share it with others." -- Chinese proverb
>
> I've been as well referred to this excellent package by a friend. Hence, I do
> what I have to do...
>
> I now would be pleased to hear what others think, and eventually can do along
> this line!
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-09-08 0:56 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 [this message]
2010-09-08 1:52 ` Thomas S. Dye
2010-09-08 4:39 ` Jambunathan K
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=87iq2huk7u.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).