[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#35022: 26.1; Load order of custom-autoload, custom-load-symbol, cust
From: |
Allen Li |
Subject: |
bug#35022: 26.1; Load order of custom-autoload, custom-load-symbol, custom-loads is backward? |
Date: |
Wed, 27 Mar 2019 14:08:42 -0700 |
Please ignore my patch. In my haste, I missed that custom-load-symbol
already checks whether a dependency is already loaded, because that
logic wasn't firing for my case (where the load path is an actual path
rather than a package name).
To clarify, the existing code works for this:
;; Called from site-start
(custom-autoload 'foo-some-variable "foo" nil)
;; Called from init.el/package-initialize
(custom-autoload 'foo-some-variable "foo" nil)
But not for this:
;; Called from site-start
(custom-autoload 'foo-some-variable "some/path/to/foo" nil)
;; Called from init.el/package-initialize
(custom-autoload 'foo-some-variable "foo" nil)
I'm not sure yet what the proper approach for my problem is.