From: Allen Li <darkfeline@felesatra.moe>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 35022-done@debbugs.gnu.org
Subject: bug#35022: 26.1; Load order of custom-autoload, custom-load-symbol, custom-loads is backward?
Date: Sat, 13 Apr 2019 21:57:02 +0000 [thread overview]
Message-ID: <CADbSrJwTSa+5FobrmhXUsVeWLkOhQMB0YDzrmvQht7L3G+H1Og@mail.gmail.com> (raw)
In-Reply-To: <87o95d9uic.fsf@gmail.com>
On Thu, Apr 11, 2019 at 1:54 AM Noam Postavsky <npostavs@gmail.com> wrote:
>
> Allen Li <darkfeline@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)
The site-start is shipped by the distro which I don't have control over.
>
> Otherwise, I guess extending custom-add-load and custom-load-symbol to
> handle entries of the form (LIBRARY . RELATIVE-NAME) could make sense.
After some deliberation, I think custom-add-load's current behavior is correct,
so I'll take my issue downstream.
Thanks
prev parent reply other threads:[~2019-04-13 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 19:45 bug#35022: 26.1; Load order of custom-autoload, custom-load-symbol, custom-loads is backward? Allen Li
2019-03-27 21:08 ` Allen Li
2019-04-11 1:54 ` Noam Postavsky
2019-04-13 21:57 ` Allen Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADbSrJwTSa+5FobrmhXUsVeWLkOhQMB0YDzrmvQht7L3G+H1Og@mail.gmail.com \
--to=darkfeline@felesatra.moe \
--cc=35022-done@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.