Hi Eric,
Eric Schulte writes:
> Would that feel cleaner to you?
I "feel" so. Please let me think more about it, and
thanks to be open to this possibility. I'm confident
we can keep a good balance between conveniency (when
editing various ob* files) and maintainability (which
should be judged
Bastien writes:
> Eric Schulte writes:
>
>> This patch is still broken
>
> (I don't know why ~$ git format-patch master did not produce an
> applicable patch.)
>
> These three ones are applicable against master/68d4de2.
>
> Bare in mind this is just meant as a proof it "works", we can
> rework t
Bastien writes:
> Eric Schulte writes:
>
>> This patch doesn't apply for me with "git am" to the HEAD of the repo so
>> I can't test it directly
>
> Please try this new one against current db51b8 commit in master.
>
This patch is still broken
org-mode$ git checkout db51b8 -b crude
Swit
Bastien writes:
> Hi Eric,
>
> Eric Schulte writes:
>
>> If you can find a cleaner alternative I'll be happy to help you
>> apply it.
>
> Here is a very crude patch for paving the way to a better solution.
>
This patch doesn't apply for me with "git am" to the HEAD of the repo so
I can't test i
Bastien writes:
> Unless you find a bug in the dependencies and/or find a bug in the way
> dependancies are handled,
(I meant: "unless you find a bug and/or strongly dislike this solution")
--
Bastien
Bastien writes:
> Eric Schulte writes:
>
>> In the absence of better ideas, I'm going to go ahead with this
>> refactoring.
>
> Okay, go ahead. But be warned that ob-core.el is not my friend :)
>
:)
> I'll see how we can get rid of it.
If you can find a cleaner alternative I'll be happy to h
Eric Schulte writes:
> In the absence of better ideas, I'm going to go ahead with this
> refactoring.
Okay, go ahead. But be warned that ob-core.el is not my friend :)
I'll see how we can get rid of it.
--
Bastien
Bastien writes:
> Achim Gratz writes:
>> I hope you are not suggesting to put all of ob into a single file…
>
> Actually that's a good idea!
Uh-oh… I'm not sure why you like that, but you'd then have the same
problem inside that single file. It's solveable, but it means you'd
need to put in lots
Bastien writes:
> Achim Gratz writes:
>
>> I hope you are not suggesting to put all of ob into a single file…
>
> Actually that's a good idea!
>
> It should be ~170ko, quite manageable (similar to org-export.el.)
>
> In terms of features, is any of ob-{keys/tangle/table/etc.}
> useful by itself
Achim Gratz writes:
> I hope you are not suggesting to put all of ob into a single file…
Actually that's a good idea!
It should be ~170ko, quite manageable (similar to org-export.el.)
In terms of features, is any of ob-{keys/tangle/table/etc.}
useful by itself, outside ob?
How would you feel
Bastien writes:
> If i read the graph correctly, merging ob.el ob-eval.el and
> ob-core.el will not create circular requires -- am I right?
Any attempt to merge ob.el and ob-core.el will result in circular
requires or (the status quo) incomplete requires. I hope you are not
suggesting to put all
Bastien writes:
> Eric Schulte writes:
>
>> Here's what the require structure of the core ob files will
>> look like after this change.
>
> If i read the graph correctly, merging ob.el ob-eval.el and
> ob-core.el will not create circular requires -- am I right?
Not correct. The result of such
Eric Schulte writes:
> Here's what the require structure of the core ob files will
> look like after this change.
If i read the graph correctly, merging ob.el ob-eval.el and
ob-core.el will not create circular requires -- am I right?
--
Bastien
Bastien writes:
> I can't reproduce this.
You most likely can if you just customize org-babel-load-languages.
> I have a ~/emacs.el file containing
>
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '((perl . t)))
>
> then ~$ emacs -Q -l ~/emacs.el loads correc
Hi Eric,
Eric Schulte writes:
> This is refactoring not bug fixing. The most important impact is that
> this will provide for simpler requires by the files implementing support
> for particular languages. Rather than having to do piecemeal requires
> of those portions of the Babel infrastructu
Bastien writes:
> Hi Eric,
>
> Eric Schulte writes:
>
>> Please let me know if I can explain anything, or if you'd like to see
>> the patches before the hit the master branch.
>
> I've read the thread carefully and I cannot clearly see what problem
> we are trying to fix. I acknowledge things c
Hi Achim,
Achim Gratz writes:
> Eric Schulte writes:
>> See http://orgmode.org/manual/Languages.html for the documentation on
>> how to activate and disable org-babel languages.
>
> That actually produces the error:
>
> File mode specification error: (void-variable org-babel-tangle-lang-exts)
>
Hi Eric,
Eric Schulte writes:
> Please let me know if I can explain anything, or if you'd like to see
> the patches before the hit the master branch.
I've read the thread carefully and I cannot clearly see what problem
we are trying to fix. I acknowledge things can be cleaned up somehow,
but
Eric Schulte gmail.com> writes:
> I will make this change (in fact I had done this originally, but then
> didn't want to send too many patches so I compressed the commit
> history).
It just occurs to me that it would be even better if you copied the file
verbatim instead of renaming it as the ver
Ok,
I have deleted some files on my system.
I have mis install org (twice in 2 path, bla bla) and I seem to work better.
Thanks a lot for help
And excuse me
2012/12/11 Eric Schulte
> flav writes:
>
> > Le 10/12/2012 18:24, Eric Schulte a écrit :
> >> 1. make sure you're using a recent version
Bastien writes:
> Hi Eric,
>
> Eric Schulte writes:
>
>> I'm attaching two patches which implement this new require structure.
>> They move ob.el -> ob-core.el. The new ob.el (which is now loaded by
>> every file which requires 'ob) does two things.
>
> I'm slowly catching up, fixing issues and
Hi Eric,
Eric Schulte writes:
> I'm attaching two patches which implement this new require structure.
> They move ob.el -> ob-core.el. The new ob.el (which is now loaded by
> every file which requires 'ob) does two things.
I'm slowly catching up, fixing issues and reading the mailing list.
Ca
Eric Schulte writes:
> I'm attaching two patches which implement this new require structure.
> They move ob.el -> ob-core.el. The new ob.el (which is now loaded by
> every file which requires 'ob) does two things.
That looks OK so far, just one nit: it would be much cleaner from the
perspective o
Eric Schulte writes:
>> Org-mode version 7.9.2 (7.9.2-dist @ /usr/share/emacs/site-lisp/org/)
>> GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.6)
>> of 2012-09-21 on allspice, modified by Debian
>>
>> Thanks for help.
>
> I don't see how this is possible.
He's using Org from a Debian p
Le 11/12/2012 14:45, Eric Schulte a écrit :
flav writes:
Le 10/12/2012 18:24, Eric Schulte a écrit :
1. make sure you're using a recent version of Org-mode, either the
latest release or from git, see
http://orgmode.org/worg/org-faq.html#Keeping-current
2. start Emacs with the -Q fl
flav writes:
> Le 10/12/2012 18:24, Eric Schulte a écrit :
>> 1. make sure you're using a recent version of Org-mode, either the
>> latest release or from git, see
>> http://orgmode.org/worg/org-faq.html#Keeping-current
>>
>> 2. start Emacs with the -Q flag (to ensure there is no problem
Le 10/12/2012 18:24, Eric Schulte a écrit :
1. make sure you're using a recent version of Org-mode, either the
latest release or from git, see
http://orgmode.org/worg/org-faq.html#Keeping-current
2. start Emacs with the -Q flag (to ensure there is no problem caused by
the rest of you
Eric Schulte writes:
> So, you're suggesting moving all ob-* defcustoms into ob.el or possibly
> into org.el? That seems reasonable to me, although I'm hesitant to add
> that much code to org.el w/o a go-ahead from Bastien or a more core
> maintainer than myself.
That would be a possibility, but
Achim Gratz writes:
> Eric Schulte writes:
>> Using this method of requiring languages,
>>
>> ;; emacs-lisp
>> (org-babel-do-load-languages
>> 'org-babel-load-languages
>> '((perl . t)))
>>
>> Works for me without issue when called from a fresh emacs (-Q). This is
>> the reco
flav writes:
> I am sorry for my misunderstood but
> I put (require 'org) in my .emacs and there is no change.
May I suggest you use the ELPA package?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Strome
Eric Schulte writes:
> Using this method of requiring languages,
>
> ;; emacs-lisp
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '((perl . t)))
>
> Works for me without issue when called from a fresh emacs (-Q). This is
> the recommended way of adding support for
1. make sure you're using a recent version of Org-mode, either the
latest release or from git, see
http://orgmode.org/worg/org-faq.html#Keeping-current
2. start Emacs with the -Q flag (to ensure there is no problem caused by
the rest of your config)
3. evaluate the Babel config
(re
I am sorry for my misunderstood but
I put (require 'org) in my .emacs and there is no change.
2012/12/10 Eric Schulte
> As I mentioned in my previous message you have to require Org-mode
> before executing the following snippet. Try
>
> (require 'org)
> (org-babel-do-load-languages
>
As I mentioned in my previous message you have to require Org-mode
before executing the following snippet. Try
(require 'org)
(org-babel-do-load-languages
'org-babel-load-languages
'((perl . t)))
flav writes:
> still an issue :
>
>
> Debugger entered--Lisp error: (v
still an issue :
Debugger entered--Lisp error: (void-function org-babel-do-load-languages)
(org-babel-do-load-languages (quote org-babel-load-languages) (quote
(...)))
eval-buffer(# nil "/home/flav/.emacs" nil t) ; Reading
at bu$
load-with-code-conversion("/home/flav/.emacs" "/home/flav/.e
Achim Gratz writes:
> Eric Schulte writes:
>> See http://orgmode.org/manual/Languages.html for the documentation on
>> how to activate and disable org-babel languages.
>
> That actually produces the error:
>
> File mode specification error: (void-variable org-babel-tangle-lang-exts)
>
> as the OP
flav writes:
> I put (require 'ob-tangle) in my .emacs
> I am sorry but now
>
> Symbol's function definition is void: org-not-nil
> when I do C-c C-o in a perl block
>
put the following in your .emacs, possibly following a (require 'org)
(org-babel-do-load-languages 'org-babel-load-languages
I put (require 'ob-tangle) in my .emacs
I am sorry but now
Symbol's function definition is void: org-not-nil
when I do C-c C-o in a perl block
2012/12/10 flav
> I put (require 'ob-tangle) in my .emacs
> I am sorry but now
>
> Symbol's function definition is void: org-not-nil
>
>
> 2012/12/9 A
I put (require 'ob-tangle) in my .emacs
I am sorry but now
Symbol's function definition is void: org-not-nil
2012/12/9 ASSI
> require 'ob-tangle
--
flav
Eric Schulte writes:
> See http://orgmode.org/manual/Languages.html for the documentation on
> how to activate and disable org-babel languages.
That actually produces the error:
File mode specification error: (void-variable org-babel-tangle-lang-exts)
as the OP has found out (and I can reproduce
Achim Gratz writes:
> flav writes:
>> In my .emacs :
>> (setq org-src-lang-modes (quote (("ocaml" . tuareg) ("elisp" .
>> emacs-lisp) ("ditaa" . artist) ("asymptote" . asy) ("dot" .
>> fundamental) ("sqlite" . sql) ("calc" . fundamental) ("C" . c) ("cpp" .
>> c++) ("screen" . shell-script) ("per
flav writes:
> In my .emacs :
> (setq org-src-lang-modes (quote (("ocaml" . tuareg) ("elisp" .
> emacs-lisp) ("ditaa" . artist) ("asymptote" . asy) ("dot" .
> fundamental) ("sqlite" . sql) ("calc" . fundamental) ("C" . c) ("cpp" .
> c++) ("screen" . shell-script) ("perl" . perl
Scratch that.
Hello,
I am trying to use babel and I don't manage :
#+begin_src
perl
print
"toto\n";
#+end_src
When I do C-c C-o : No org-babel-execute function for perl!
In my .emacs :
(setq org-src-lang-modes (quote (("ocaml" . tuareg) ("elisp" . emacs-lisp)
("ditaa" . artist) ("asymptote" . asy) ("dot"
43 matches
Mail list logo
