Hi Carsten,
Carsten Dominik writes:
> Hi Eric, thanks for this.
>
> I would actually like to have a variable that will exclude evaluation
> from being added to the C-c C-c hook. I think users will understand
> better how to use this, and customizing it will work for sure.
> Explicitly removing
Hi Eric,
thanks, I think we have a good solution, at least for the time being.
I have started the security section in the manual, please feel free to
add to it.
- Carsten
On Jul 1, 2010, at 4:55 PM, Eric Schulte wrote:
Hi,
Thanks for finding such a good compromises solution. This new pl
Hi Eric, thanks for this.
I would actually like to have a variable that will exclude evaluation
from being added to the C-c C-c hook. I think users will understand
better
how to use this, and customizing it will work for sure. Explicitly
removing it from the hook will only work after load ti
Sébastien Vauban wrote:
> Nick Dokos wrote:
> > Carsten Dominik wrote:
> >>
> >> :-) Actually, in this specific area I had been thinking to removing or at
> >> least deprecating shell and elisp links, because the Org-babel way is much
> >> better and clearer to have that code in a block, rather
Hi,
Thanks for getting the safety catch on fast. And thanks to Matt Lundin
and Carsten Dominik for raising the concerns that were mounting in my
mind as I caught up with the powers Org-Babel have placed at my
fingertips. I love knowing it's there, but until I learn to use it, I
just want to k
Hi,
Pursuant to the below, I've created a new "babel-safety" branch of the
repository. It includes two new commits, the first of which implements
confirmation before *any* code block evaluation, adds the keybinds for
code block evaluation, and adds a documentation for disassociating code
block ev
Hi Nick,
Nick Dokos wrote:
> Carsten Dominik wrote:
>>
>> :-) Actually, in this specific area I had been thinking to removing or at
>> least deprecating shell and elisp links, because the Org-babel way is much
>> better and clearer to have that code in a block, rather than hiding it in
>> the in
Carsten Dominik wrote:
>
> :-) Actually, in this specific area I had been thinking to
> removing or at least deprecating shell and elisp links,
> because the Org-babel way is much better and clearer to have
> that code in a block, rather than hiding it in the invisible
> part of of a link.
>
Hi,
Thanks for finding such a good compromises solution. This new plan
looks great to me, specifics below
Carsten Dominik writes:
> Hi everyone,
>
> first of all, I think it is clear that I may have overreacted
> with the "6 point plan". But it is good that we are having
> this discussion.
>
Hi everyone,
first of all, I think it is clear that I may have overreacted
with the "6 point plan". But it is good that we are having
this discussion.
On Jun 30, 2010, at 6:25 PM, Eric Schulte wrote:
Hi Carsten, Matt, Scott,
Carsten Dominik writes:
Hi Matt, hi Eric,
Matt, thanks a lot fo
On Jun 30, 2010, at 7:01 PM, Dan Davison wrote:
"Eric Schulte" writes:
Hi Carsten, Matt, Scott,
Carsten Dominik writes:
Hi Matt, hi Eric,
Matt, thanks a lot for bringing this up. This is indeed a very
important and serious issue. We need to address it. We need to
step back and recons
Dan Davison writes:
> "Eric Schulte" writes:
>
>> Carsten Dominik writes:
>>
>>> You main proposal was to make Org Babel an optional module.
>>> This will not solve the problem fully, I think, because we also
>>> don't want that people who turn it on automatically commit
>>> to potentially dang
Hi,
just to throw yet another idea into the discussion:
Execute source blocks only after the user confirmed it ("Do you know
what you are doing (Type y, n, !, or SPC)?"). ! and SPC will add the
current org file to the variables org-babel-trusted-files and
org-babel-trusted-permanently-files (al
"Eric Schulte" writes:
> Matt Lundin writes:
>
> [...]
>>
>> When I run make clean && make && make install I find that the language
>> directory is not installed. Does the langs directory require a manual
>> installation?
>>
>> Also, with make install, the ob-* files are installed on the same le
Hi,
To add some concreteness to my suggestions I'm attaching to possible
patches.
The first introduces a global `org-confirm-babel-evaluate' variable
which defaults to t, meaning all code block evaluations will require
explicit confirmation from the user.
The second patch adds an `org-babel-disa
Matt Lundin writes:
[...]
>
> When I run make clean && make && make install I find that the language
> directory is not installed. Does the langs directory require a manual
> installation?
>
> Also, with make install, the ob-* files are installed on the same level
> as the org-files, yet lines 10
Dan Davison writes:
> "Eric Schulte" writes:
>
>> Hi Carsten, Matt, Scott,
>>
>> Carsten Dominik writes:
>>
[...]
>>> 1. A new variable org-turn-on-babel. We can discuss the default.
>>>If it is nil, org-babel should not be loaded.
>>>A default of t would be fine with me if we implemen
"Eric Schulte" writes:
> Hi Carsten, Matt, Scott,
>
> Carsten Dominik writes:
>
>> Hi Matt, hi Eric,
>>
>> Matt, thanks a lot for bringing this up. This is indeed a very
>> important and serious issue. We need to address it. We need to
>> step back and reconsider this carefully.
>>
>> Don't g
Hi Carsten, Matt, Scott,
Carsten Dominik writes:
> Hi Matt, hi Eric,
>
> Matt, thanks a lot for bringing this up. This is indeed a very
> important and serious issue. We need to address it. We need to
> step back and reconsider this carefully.
>
> Don't get me wrong, I absolutely think that O
On Jun 30, 2010, at 2:53 PM, Matthew Lundin wrote:
Hi Carsten,
Thanks so much both for thinking this through. And thanks again, Eric,
for your work in integrating org-babel into org-mode---including
taking
into account a humble user's concerns! :)
Carsten Dominik writes:
Here is what I p
Hi Carsten,
Thanks so much both for thinking this through. And thanks again, Eric,
for your work in integrating org-babel into org-mode---including taking
into account a humble user's concerns! :)
Carsten Dominik writes:
> Here is what I propose (several items are similar to what Eric proposes)
Hi Eric,
Thanks so much for taking these observations into account.
"Eric Schulte" writes:
> Thanks for raising the point about potentially dangerous code blocks.
>
> Matt Lundin writes:
>
>> Hi Eric,
>>
>> Thanks again for all the work that you, Dan, and Tom have put into
>> org-babel. I'm gl
On Tue, Jun 29, 2010 at 11:03 PM, Eric Schulte wrote:
> > - Org-babel adds rather specific and complex functionality to org-mode
> > that those who use it as a simple outliner and todo manager do not
> > require. (In other words, an option to turn it off might be nice for
> > those w
Hi Matt, hi Eric,
Matt, thanks a lot for bringing this up. This is indeed a very
important and serious issue. We need to address it. We need to
step back and reconsider this carefully.
Don't get me wrong, I absolutely think that Org Babel should give
you enough rope to hang yourself. But we
non-empty attachment
diff --git a/Makefile b/Makefile
index d4da79d..f6538ce 100644
--- a/Makefile
+++ b/Makefile
@@ -17,7 +17,9 @@ EMACS=emacs
prefix=/usr/local
# Where local lisp files go.
-lispdir = $(prefix)/share/emacs/site-lisp
+lispdir = $(prefix)/share/emacs/site-lisp
+lispbdir = $(
Nick Dokos writes:
> Eric Schulte wrote:
>
>> --=-=-=
>>
>> with attachment ;)
>>
>> >
>> > I hardly believe this worked since it is the product of naive Makefile
>> > pattern matching (which has never worked for me in the past), however it
>> > appears to be compiling on my system.
>> >
>> >
Eric Schulte wrote:
> --=-=-=
>
> with attachment ;)
>
> >
> > I hardly believe this worked since it is the product of naive Makefile
> > pattern matching (which has never worked for me in the past), however it
> > appears to be compiling on my system.
> >
> > If someone who actually uses "make
with attachment ;)
>From 24f99a2ebd3de464fdb60902f003b828c2f71003 Mon Sep 17 00:00:00 2001
From: Eric Schulte
Date: Tue, 29 Jun 2010 15:53:15 -0700
Subject: [PATCH] update Makefile for correct instillation of Babel files
---
Makefile | 157 --
Hi all,
"Eric Schulte" writes:
> Hi Matt,
>
> Thanks for raising the point about potentially dangerous code blocks.
>
> Matt Lundin writes:
[...]
>>
>> Also, with make install, the ob-* files are installed on the same
>> level as the org-files, yet lines 108-114 in org.el indicate that they
>
Matt Lundin wrote:
> >
> >> When I run make clean && make && make install I find that the language
> >> directory is not installed. Does the langs directory require a manual
> >> installation?
> >>
> >
> > It's part of the git repository, so it should be present after you do a
> > git pull.
>
>
Hi Matt,
Thanks for raising the point about potentially dangerous code blocks.
Matt Lundin writes:
> Hi Eric,
>
> Thanks again for all the work that you, Dan, and Tom have put into
> org-babel. I'm glad to see it become part of org-mode!
>
> "Eric Schulte" writes:
>
>> 2) Babel will now be loa
Matt Lundin writes:
> This section of the lisp file flattens out the lisp/babel hierarchy in
> the repo when copying to the target directory:
The above should read: "This section of the Makefile..."
>
> install-lisp: $(LISPFILES) $(ELCFILES)
> if [ ! -d $(lispdir) ]; then $(MKDIR) $(lispdir
Hi Nick,
Nick Dokos writes:
> Matt Lundin wrote:
>
>
>> When I run make clean && make && make install I find that the language
>> directory is not installed. Does the langs directory require a manual
>> installation?
>>
>
> It's part of the git repository, so it should be present after you do
Matt Lundin wrote:
> When I run make clean && make && make install I find that the language
> directory is not installed. Does the langs directory require a manual
> installation?
>
It's part of the git repository, so it should be present after you do a
git pull.
> Also, with make install, th
Hi Eric,
Thanks again for all the work that you, Dan, and Tom have put into
org-babel. I'm glad to see it become part of org-mode!
"Eric Schulte" writes:
> 2) Babel will now be loaded by default along with the rest of Org-mode.
>This means that *everyone* currently using babel will need to
On Mon, Jun 28, 2010 at 6:03 PM, Eric Schulte wrote:
> Hi Rainer,
>
> I'm happy this was useful
>
> Rainer M Krug writes:
>
> > On Fri, Jun 25, 2010 at 5:37 PM, Eric Schulte >wrote:
>
> [...]
> >> >
> >> > *** Start babel
> >> > #+begin_src emacs-lisp
> >> > (org-babel-load-library-of-babel)
>
Hi Rainer,
I'm happy this was useful
Rainer M Krug writes:
> On Fri, Jun 25, 2010 at 5:37 PM, Eric Schulte wrote:
[...]
>> >
>> > *** Start babel
>> > #+begin_src emacs-lisp
>> > (org-babel-load-library-of-babel)
>> > #+end_src
>>
>> the above becomes
>>
>> #+begin_src emacs-lisp
>> (org-ba
2010/6/28 Bernt Hansen
> Rainer M Krug writes:
>
> > I updated my org-mode directory with the following script:
> >
> > rk...@ecolmod:~/.emacs.d$ cat update_org-mode-git
> > #!/bin/sh
> > cd ./org-mode-git
> > cd org-mode
> >
> > # git clone git://repo.or.cz/org-mode.git
> > git pull
> > git gc
Rainer M Krug writes:
> I updated my org-mode directory with the following script:
>
> rk...@ecolmod:~/.emacs.d$ cat update_org-mode-git
> #!/bin/sh
> cd ./org-mode-git
> cd org-mode
>
> # git clone git://repo.or.cz/org-mode.git
> git pull
> git gc
>
> make clean
> make
> make doc
>
> after addi
2010/6/28 Bernt Hansen
> Rainer M Krug writes:
>
> > On Mon, Jun 28, 2010 at 1:53 PM, Štěpán Němec wrote:
> >
> > Rainer M Krug writes:
> >
> > > Just one additional question: When I go on the menu to Org --
> Documentation
> > > -- Info Documentation, I still get the info help fr
Rainer M Krug writes:
> On Mon, Jun 28, 2010 at 1:53 PM, Štěpán Němec wrote:
>
> Rainer M Krug writes:
>
> > Just one additional question: When I go on the menu to Org --
> Documentation
> > -- Info Documentation, I still get the info help from version 6.21b,
> > although
On Mon, Jun 28, 2010 at 1:53 PM, Štěpán Němec wrote:
> Rainer M Krug writes:
>
> > Just one additional question: When I go on the menu to Org --
> Documentation
> > -- Info Documentation, I still get the info help from version 6.21b,
> > although I installed the version from git, and under Org
Rainer M Krug writes:
> Just one additional question: When I go on the menu to Org -- Documentation
> -- Info Documentation, I still get the info help from version 6.21b,
> although I installed the version from git, and under Org -- Documentation --
> Show Version it gives me "Org-mode version 6
On Fri, Jun 25, 2010 at 5:37 PM, Eric Schulte wrote:
> Hi Rainer,
>
Hi Eric
>
> First I'll give some expanded instructions in the hopes of helping out
> anyone else affected by my lack of good instructions in the announcement
> email. Then I'll provide a re-write of your config below as an exa
Carsten Dominik writes:
> On Jun 26, 2010, at 6:30 PM, Štěpán Němec wrote:
>
>> "Eric Schulte" writes:
>>
>>> Štěpán Němec writes:
>>>
>>> [...]
How come some of your rewrites above still use the `org-babel-'
prefix?
(As a side note, I don't see what Emacs guidelines sugges
On Jun 26, 2010, at 6:30 PM, Štěpán Němec wrote:
"Eric Schulte" writes:
Štěpán Němec writes:
[...]
How come some of your rewrites above still use the `org-babel-'
prefix?
(As a side note, I don't see what Emacs guidelines suggest `ob-'
is more
appropriate than `org-babel-', and I wou
Also sprach Eric Schulte:
Štěpán Němec writes:
"Eric Schulte" writes:
Štěpán Němec writes:
[...]
How come some of your rewrites above still use the `org-babel-' prefix?
(As a side note, I don't see what Emacs guidelines suggest `ob-' is more
appropriate than `org-babel-', and I would
Štěpán Němec writes:
> "Eric Schulte" writes:
>
>> Štěpán Němec writes:
>>
>> [...]
>>>
>>> How come some of your rewrites above still use the `org-babel-' prefix?
>>> (As a side note, I don't see what Emacs guidelines suggest `ob-' is more
>>> appropriate than `org-babel-', and I would persona
"Eric Schulte" writes:
> Štěpán Němec writes:
>
> [...]
>>
>> How come some of your rewrites above still use the `org-babel-' prefix?
>> (As a side note, I don't see what Emacs guidelines suggest `ob-' is more
>> appropriate than `org-babel-', and I would personally prefer to retain
>> the latte
Štěpán Němec writes:
[...]
>
> How come some of your rewrites above still use the `org-babel-' prefix?
> (As a side note, I don't see what Emacs guidelines suggest `ob-' is more
> appropriate than `org-babel-', and I would personally prefer to retain
> the latter -- it's much more descriptive.)
>
"Eric Schulte" writes:
> Hi Rainer,
>
> First I'll give some expanded instructions in the hopes of helping out
> anyone else affected by my lack of good instructions in the announcement
> email. Then I'll provide a re-write of your config below as an example.
>
> Babel took the integration into
Hi
First of all thanks for integrating Org-babel into Org-mode.
But for the less fluent elisp and org-mode users, I am slightly confused in
the changes necessary on my side.
I have the following in my emacs.org file:
#+begin_src emacs-lisp
(require 'org-babel-R) ;; requires R and ess
Hi Rainer,
First I'll give some expanded instructions in the hopes of helping out
anyone else affected by my lack of good instructions in the announcement
email. Then I'll provide a re-write of your config below as an example.
Babel took the integration into Org-mode as an opportunity to do some
Hi Sébastien,
Sébastien Vauban writes:
[...]
>
> For my own understanding, what's the status of `Org-babel-screen', for which
> I've never been able to understand completely all the differences with `sh' in
> `Org-babel'?
>
I believe screen has more of a focus on sustained interaction with an
i
Hi Eric,
> I've just merged the babel branch into the main branch of Org-mode.
>
> [...]
>
> 2) Babel will now be loaded by default along with the rest of Org-mode. This
>means that *everyone* currently using babel will need to change their
>Emacs config and remove the (require 'org-babel-
Hi Nathan,
Nathan Neff writes:
> I checked out the latest org mode, and I'm getting "Symbol's function
> definition is void: second"
>
> I ran git-bisect, and the error was introduced with the merge of
> org-babel into the main
> branch.
>
Part of merging into Org-mode (and meeting the Emacs co
I checked out the latest org mode, and I'm getting "Symbol's function
definition is void: second"
I ran git-bisect, and the error was introduced with the merge of
org-babel into the main
branch.
The code that's causing the error is here:
#+tblname:shortcut-definition-list
| Something | a
Bernt Hansen writes:
>
> The documentation still has (require 'org-babel-identifier) and should
> probably be updated.
>
updated, Thanks -- Eric
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
h
"Eric Schulte" writes:
>Support for evaluating emacs-lisp code blocks is loaded by default.
>All other languages will need to be required explicitly. To conform
>to Emacs filename specifications all language require lines have been
>shortened from e.g.
>
>(require 'org-ba
59 matches
Mail list logo
