From: Paul Burkander <paul@burkander.com>
To: Ista Zahn <istazahn@gmail.com>
Cc: Paul <paulburk314@gmail.com>, Emacs-orgmode@gnu.org
Subject: Re: export literal examples font-lock: ess-mode
Date: Fri, 17 Aug 2012 11:33:03 -0400 [thread overview]
Message-ID: <CAMO4H7F=TbONy6mpJQsUSjverYKnGNY62mvb8+wy3Zm=Dbih_g@mail.gmail.com> (raw)
In-Reply-To: <CA+vqiLGBQ0i2rt4suX3MFLq1v8XJu_QPHGxZm_L6u7B8R29U_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
ah! for some reason capitalizing BEGIN_SRC seems to have been causing
problems.
Thanks for your help!
On Fri, Aug 17, 2012 at 11:12 AM, Ista Zahn <istazahn@gmail.com> wrote:
> On Fri, Aug 17, 2012 at 9:23 AM, Paul <paulburk314@gmail.com> wrote:
> > I write do-files for Stata code in emacs using ESS, which marks up my
> > code and sends it to a comint-mode buffer for evaluation. I'd like to
> > include some source code in an org file, as in the below examle:
> >
> > #+begin_src -n
> > foreach var of varlist _all{
> > rename `var' new_`var'
> > }
> > #+end_src
> >
> > I have a couple of questions:
> > How can I use ess fontification in this snippet
>
> #+begin_src stata
> foreach var of varlist _all{
> rename `var' new_`var'
> }
> #+end_src
>
> works for me.
>
> and in the file to
> > which I export?
>
> I think this depends on your export target. It should "just work" for
> html, but pdf will be more work.
>
> The manual says I "need to specify the name of the
> > major mode," however including "#+begin_src ess -n" results in the
> > following error "org-edit-src-code: No such language mode: nil-mode."
> > I've tried using ess-mode, and anything else I can think of, to no
> > avail. What should I include?
>
> I think "#+begin_src stata" is correct.
>
> >
> > Also, assuming I'm able to get the fontification to work, is there a
> > way to customize it for exporting?
> >
> > Finally, org-babel looks tremendously useful. Is there a way to
> > harness it's capabilities for an unsupported language like Stata's?
>
> C-c ' will open a temporary buffer in ess mode so you can edit and run
> the code using ess, and tangling will work as expected. The only thing
> you need babel support for is actually running the code in org-mode
> and inserting the results block.
>
> I've made weak attempts to add stata support to babel, but my
> elisp-foo is not strong enough.
>
> >
> > Thanks to everyone who read this through, and in particular to anyone
> > who can help!
> > Paul
> >
>
[-- Attachment #2: Type: text/html, Size: 2835 bytes --]
next prev parent reply other threads:[~2012-08-17 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 13:23 export literal examples font-lock: ess-mode Paul
2012-08-17 15:12 ` Ista Zahn
2012-08-17 15:33 ` Paul Burkander [this message]
2012-08-19 6:28 ` Bastien
2012-08-19 17:11 ` Paul Burkander
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='CAMO4H7F=TbONy6mpJQsUSjverYKnGNY62mvb8+wy3Zm=Dbih_g@mail.gmail.com' \
--to=paul@burkander.com \
--cc=Emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
--cc=paulburk314@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).