emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Noorul Islam <noorul@noorul.com>
To: Bill Harris <bill_harris@facilitatedsystems.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: File-level execute permissions?
Date: Sat, 25 Sep 2010 11:10:54 +0530	[thread overview]
Message-ID: <AANLkTimOkmeOuBarni_Qi7tkwBa+X6gMrVC7-XvbQKi0@mail.gmail.com> (raw)
In-Reply-To: <87zkv74778.fsf@moenchweiler.bach>

On Fri, Sep 24, 2010 at 6:41 PM, Bill Harris
<bill_harris@facilitatedsystems.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I understand at least the obvious risks in executing source code blocks
> inside an unknown org file, but, when I created the org file myself, it
> would be nice to be able to export the file without confirming execution
> 20+ times.
>
> Is there a header element I can set that asks one time for the entire
> file (or session, perhaps) for execute permission?  I think that would
> be safer than blindly turning on permission, for I'd at least get one
> opportunity to abort exporting if I was surprised by the existence of
> src blocks.
>

How about setting `org-confirm-babel-evaluate' to nil

Thanks and Regards
Noorul

  reply	other threads:[~2010-09-25  5:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 13:11 File-level execute permissions? Bill Harris
2010-09-25  5:40 ` Noorul Islam [this message]
2010-09-25 23:29   ` Bill Harris
2010-09-27 13:46     ` Eric Schulte
2010-09-28  1:08       ` Bill Harris
2010-09-28 17:40         ` Eric Schulte
2010-09-29  2:36           ` Bill Harris

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=AANLkTimOkmeOuBarni_Qi7tkwBa+X6gMrVC7-XvbQKi0@mail.gmail.com \
    --to=noorul@noorul.com \
    --cc=bill_harris@facilitatedsystems.com \
    --cc=emacs-orgmode@gnu.org \
    /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).