On Sunday, January 6, 2013, Eric Schulte wrote:
Tom Davey tda...@gmail.com javascript:; writes:
Hi folks,
This is a very interesting discussion. I too have run into this issue,
and addressed it in a different way.
My init.el contains only a defun and an add-hook. The defun is
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
I hope that a later version of Emacs (not the upcoming 24.3, though)
will properly move the bundled Org into a package. That's been talked
about for a while, but has not happened since it will likely require a
few more tweaks to the way
Bastien writes:
I hope that a later version of Emacs (not the upcoming 24.3, though)
will properly move the bundled Org into a package. That's been talked
about for a while, but has not happened since it will likely require a
few more tweaks to the way package manager works.
Please don't
Achim Gratz strom...@nexgo.de writes:
I think you are misunderstanding what packetizing Emacs' builtin
packages means. Stefan Monnier has already said that he intends to have
Org (and other packages that are maintained outside Emacs) as built-in
packages within Emacs so that they become
Bastien writes:
For the current meaning of an Emacs package, it means moving
Org outside of Emacs' core.
Org is already shown as a built-in package in recent Emacs if you care
to look in package manager. I don't understand what you think Emacs'
core is, but to me anything that is released and
Achim Gratz strom...@nexgo.de writes:
Org is already shown as a built-in package in recent Emacs if you care
to look in package manager. I don't understand what you think Emacs'
core is, but to me anything that is released and installed together
with Emacs is core, no matter how it gets into
Bastien b...@altern.org writes:
I also wish Emacs can read an ~/.emacs.org init file.
That is what the starterkit for emacs 24 is attempting to do. It's got
a ~/init.el that is just
#+begin_src emacs-lisp
(setq starter-kit-dir
(file-name-directory (or load-file-name
Robert Horn writes:
All of my problems seem to arise from the bad interactions between
starting with the built-in package version of org that is used by the
org-babel-load-file, and then transitioning part way through its
execution of the starter-kit.org to the elpa updated version of org.
After reading the first post in this thread, it seems that the problem
is likely caused by this commit [1], which changes the syntax of valid
code blocks. This means that an Org-mode file with certain types of
code blocks may either be valid before the commit, or valid after the
commit, but not
Eric Schulte writes:
The starter kit does not run through the Org files each time, rather
it tangles the .org files to .el files, and then on all subsequent loads
it loads directly from the .el files (unless the .org file is newer).
So why does it need to load Org before activating the
Achim Gratz strom...@nexgo.de writes:
Eric Schulte writes:
The starter kit does not run through the Org files each time, rather
it tangles the .org files to .el files, and then on all subsequent loads
it loads directly from the .el files (unless the .org file is newer).
So why does it need
Eric Schulte writes:
Because the above sequence of loading .el files and possibly falling
back to .org files is all performed by the `org-babel-load-file'
function, which is not defined until org has been required.
Which confirms it runs through the Org files each time as I had
assumed
Eric Schulte schulte.e...@gmail.com writes:
That sounds like it should work, although I would go with the more
complete but possibly overkill
;; emacs-lisp
(package-initialize)
(require 'org)
(org-reload)
Let me know if either of the above is sufficient to solve your
Hi folks,
This is a very interesting discussion. I too have run into this issue,
and addressed it in a different way.
My init.el contains only a defun and an add-hook. The defun is simple.
It adds a few miscellaneous directories to load-path and then makes
the call to Eric's starter kit via
Achim Gratz strom...@nexgo.de writes:
Eric Schulte writes:
Because the above sequence of loading .el files and possibly falling
back to .org files is all performed by the `org-babel-load-file'
function, which is not defined until org has been required.
Which confirms it runs through the Org
Tom Davey tda...@gmail.com writes:
Hi folks,
This is a very interesting discussion. I too have run into this issue,
and addressed it in a different way.
My init.el contains only a defun and an add-hook. The defun is simple.
It adds a few miscellaneous directories to load-path and then
Achim Gratz strom...@nexgo.de writes:
Robert Horn writes:
I'm experimenting with starterkit on a new machine and have run into a
bug in org-mode elpa version 20121231.
Using two systems that hook into Emacs' startup sequence simultaneously
is asking for trouble. It may be solveable by
Robert Horn writes:
Starterkit does have code that looked correct and proper for
coordinating the init with elpa, and I think that for packages not
used by org-mode it will be OK. But, the automagic startup executes the
lisp code using babel from org files. This means that org and it's
Robert Horn rjh...@alum.mit.edu writes:
I'm experimenting with starterkit on a new machine and have run into a
bug in org-mode elpa version 20121231.
With the stock distribution org-mode (7.8.11) in emacs 24.2 there is no
problem. With the elpa version 20121231 I get an error, see the
I'm experimenting with starterkit on a new machine and have run into a
bug in org-mode elpa version 20121231.
With the stock distribution org-mode (7.8.11) in emacs 24.2 there is no
problem. With the elpa version 20121231 I get an error, see the
attached output from emacs --debug-init.
It's
20 matches
Mail list logo
