emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Noorul Islam <noorul@noorul.com>
Subject: Re: Why are src_perl{} immediately executed?
Date: Sun, 14 Nov 2010 21:46:22 +0200	[thread overview]
Message-ID: <AANLkTim8_cqWQVNsHGMCX=8rEhTV3_SFOBBC3OwAzOtQ@mail.gmail.com> (raw)
In-Reply-To: <877hgfzydk.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1777 bytes --]

Ok. Thanks for clarifying it. The documentation isn't clear on this issue.

Regards,
Dov

On Sun, Nov 14, 2010 at 18:03, Eric Schulte <schulte.eric@gmail.com> wrote:

> Hi Dov,
>
> That is correct, there is no method of highlighting inline code blocks,
> the begin_src constructs are just for evaluation of inline code.
>
> You can customized the `org-babel-default-inline-header-args' to inhibit
> the execution of inline code blocks on export.
>
> Best -- Eric
>
> Dov Grobgeld <dov.grobgeld@gmail.com> writes:
>
> > From the documentation I see now difference between inline and multi-line
> > behavior. Note that I did not wish to evaluate the code at all but just
> have
> > inline syntax highlighting in my html export. Is src_perl{foo()} for
> > evaluation only and not for source highlighting?
> >
> > Thanks,
> > Dov
> >
> > On Sun, Nov 14, 2010 at 04:49, Noorul Islam <noorul@noorul.com> wrote:
> >
> >> On Sun, Nov 14, 2010 at 3:34 AM, Dov Grobgeld <dov.grobgeld@gmail.com>
> >> wrote:
> >> > From the documentation it seems like a statement such as
> src_perl{foo()}
> >> are
> >> > inline version of the multi line:
> >> >
> >> > #+src_perl
> >> > foo();
> >> > #+end_src
> >> >
> >> > But when exporting the org file to html I get the question "Evaluate
> this
> >> > perl code on your system" for the inline version, but not for the
> >> multiline
> >> > version. Is this a bug or did I miss something?
> >> >
> >>
> >>
> >> You can customize this with the variable org-confirm-babel-evaluate
> >>
> >> Thanks and Regards
> >> Noorul
> >>
> > _______________________________________________
> > Emacs-orgmode mailing list
> > Please use `Reply All' to send replies to the list.
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 2814 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2010-11-14 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 22:04 Why are src_perl{} immediately executed? Dov Grobgeld
2010-11-14  2:49 ` Noorul Islam
2010-11-14  7:27   ` Dov Grobgeld
2010-11-14 16:03     ` Eric Schulte
2010-11-14 19:46       ` Dov Grobgeld [this message]

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='AANLkTim8_cqWQVNsHGMCX=8rEhTV3_SFOBBC3OwAzOtQ@mail.gmail.com' \
    --to=dov.grobgeld@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=noorul@noorul.com \
    --cc=schulte.eric@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).