Bastien writes:
> Sorry, maybe I was unclear, but I'm looking forward to reading
> a *recipe* to reproduce the bug.
Bastien,
I think what Achim is saying is that, for those of us that install org
from git, the system of autoloading is *fragile* because it depends on
non-predictable behaviour of
Bastien writes:
> Sorry, maybe I was unclear, but I'm looking forward to reading
> a *recipe* to reproduce the bug.
Build an Emacs without Org or remove all autoload forms for Org from
loaddefs.el, then install a standalone Org and don't add any requires to
the startup files. Try to use any Org f
Sorry, maybe I was unclear, but I'm looking forward to reading
a *recipe* to reproduce the bug.
I will re-read your email when I have time to parse it in full
details.
Thanks,
--
Bastien
Bastien writes:
> Can you point at an actual reproducible and simple bug with
> the current way Org defines autoloads?
After the introduction of org-loaddefs, the autoloads should be
extracted into two files and only the first is supposed to be loaded
before org is actually used and the second, or
Achim Gratz writes:
> Bastien writes:
>> What is "autoload-rubric"?
>
> C-h f autoload-rubric
>
> autoload-rubric is a compiled Lisp function in `autoload.el'.
Thanks. The function is not autoloaded, so I had to
(require 'autoload) before being able to access it.
--
Bastien
Bastien writes:
> What is "autoload-rubric"?
C-h f autoload-rubric
autoload-rubric is a compiled Lisp function in `autoload.el'.
(autoload-rubric FILE &optional TYPE FEATURE)
Return a string giving the appropriate autoload rubric for FILE.
TYPE (default "autoloads") is a string stating the type
Hi Achim,
let's start fresh.
Can you point at an actual reproducible and simple bug with
the current way Org defines autoloads?
Thanks,
--
Bastien
Hi Achim,
Bastien writes:
>> + (write-region (autoload-rubric "org-install.el" nil "org-install") nil
>> "org-install.el")
>> + (write-region (autoload-rubric "org-loaddefs.el" nil "org-loaddefs") nil
>> "org-install.el")
>
> I don't know what "autoload-rubric" is. Hint?
You didn't reply t
Bastien writes:
> You mean "in case users install Org from a tar/zip archive that does
> not contain org-loaddefs.el"?
>
> For now the tar/zip archives does not contain org-loaddefs.el but it
> will starting from Org 7.9.3.
>
> (require 'org-loaddefs) is wrong in case users who cloned Org from Git
Hi Achim,
Achim Gratz writes:
> It is if you are using Org from Git and you only want the autoload
> definitions pulled in on startup and not the whole of Org plus most of
> its dependencies. This is what a
>
> (require 'org-install)
>
> did before the change to org-loaddefs.el. You can't rely
Bastien writes:
> No, (require 'org-loaddefs) is never needed IMHO.
It is if you are using Org from Git and you only want the autoload
definitions pulled in on startup and not the whole of Org plus most of
its dependencies. This is what a
(require 'org-install)
did before the change to org-load
Hi Simon,
Simon Thum writes:
>>;;; org-install.el --- backward compatibility file for obsolete
>> configuration
>>;;
>>;;; Code:
>>(warn "The file org-install is obsolete.
>>It is provided here so that (require 'org-install) does not
>>trigger an error for users with obs
Hi Sébastien,
"Sebastien Vauban"
writes:
> Wouldn't it be better to tell users to require 'org-loaddefs instead
No, (require 'org-loaddefs) is never needed IMHO.
> , so that
> they don't have a performance penalty when loading their .emacs file, until
> they really access Org -- if they do,
Hi Bastien,
thanks a lot for clarifying this. One nit left, see below.
I'm having a look at putting a summary in worg.
Thanks,
Simon
On 10/27/2012 09:33 AM, Bastien wrote:
Hi Simon,
Simon Thum writes:
Sorry but to me this just worsens the (or my) confusion around
org-install.
In git we
Bastien writes:
> Achim Gratz writes:
>
>> As a result, you must now load org (which in turn loads org-loaddefs).
>
> I don't think so.
Fake an autoload refering to some non-existing file or function in
org-loaddefs.el in the Git worktree and try if you see that without
doing a (require 'org). T
Hi Bastien,
Bastien wrote:
>> ;;; Code:
>> (warn "The file org-install is obsolete.
>> Please change your configuration to (require 'org) instead.")
>
> Yes, this was confusing. I updated this file like this
>
> ;;; org-install.el --- backward compatibility file for obsolete
> configuration
>
Achim Gratz writes:
> As a result, you must now load org (which in turn loads org-loaddefs).
I don't think so.
With a fresh git clone in e.g. ~/org-mode/ and "make autoloads",
or with the tar/zip archive unpacked in this directory, I get the
correct autoloads without (require 'org). Here is h
Simon Thum writes:
> Which is the recommended thing in what setup? If ELPA needs not even
> org, which AFAIK is not the case, then what? And what about git
> installs?
>
> I guess I'm wholly confused now.
You never needed to do anything extra for using Org as it comes with
Emacs, the autoloads are
Hi Simon,
Simon Thum writes:
> Sorry but to me this just worsens the (or my) confusion around
> org-install.
>
> In git we find this org-install.el:
>
> ;;; org-install.el --- autogenerated file, do not edit
> ;;
> ;;; Code:
> (warn "The file org-install is obsolete.
> Please change your configu
On 10/25/2012 12:42 AM, Bastien wrote:
Hi Simon,
Simon Thum writes:
I just set up another machine and noticed that the ELPA install still
recommends (require 'org-install).
http://orgmode.org/elpa.html
That worked but got me warnings.
I added a note about (require 'org-install) not being
Hi Simon,
Simon Thum writes:
> I just set up another machine and noticed that the ELPA install still
> recommends (require 'org-install).
>
> http://orgmode.org/elpa.html
>
> That worked but got me warnings.
I added a note about (require 'org-install) not being required for
Org > 7.9.2 -- thank
Hi,
I just set up another machine and noticed that the ELPA install still
recommends (require 'org-install).
http://orgmode.org/elpa.html
That worked but got me warnings.
Cheers,
Simon
22 matches
Mail list logo
