GNU bug report logs - #35022
custom-add-load, custom-load-symbol don't support filenames with directory components

Previous Next

Full log

View this message in rfc822 format

From: Noam Postavsky <npostavs <at> gmail.com>
To: Allen Li <darkfeline <at> felesatra.moe>
Cc: 35022 <at> debbugs.gnu.org
Subject: bug#35022: 26.1; Load order of custom-autoload, custom-load-symbol, custom-loads is backward?
Date: Wed, 10 Apr 2019 21:54:19 -0400

retitle 35022 custom-add-load, custom-load-symbol don't support filenames with directory components
severity 35022 wishlist
quit

Allen Li <darkfeline <at> felesatra.moe> writes:

> 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.

Would it be too impertinent to suggest the proper aproach is this:

    ;; Called from site-start
    (add-to-list 'load-path (expand-file-name "some/path/to"))
    (custom-autoload 'foo-some-variable "foo" nil)
    ;; Called from init.el/package-initialize
    (custom-autoload 'foo-some-variable "foo" nil)

Otherwise, I guess extending custom-add-load and custom-load-symbol to
handle entries of the form (LIBRARY . RELATIVE-NAME) could make sense.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.