all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ;;;###autoload declarations
Date: Sat, 24 Jun 2023 11:27:50 +0000	[thread overview]
Message-ID: <Xuijxauvkcws2udK_4hLOV18vSFikKRin9iuSxbNeXKH4eQbD6GzqL3pRzxqydYz0jMghWLhiiqeQ20TM10J32gLsM2hm4lLdUmCtc6ugGA=@proton.me> (raw)
In-Reply-To: <87pm5lr52f.fsf@web.de>


------- Original Message -------
On Saturday, June 24th, 2023 at 2:02 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:


> uzibalqa uzibalqa@proton.me writes:
> 
> > What is the procedure of using a loaddefs.el?
> 
> 
> It's a file containing the autoload references. It's normally build
> automatically - when building Emacs, installing packages, etc. And
> normally loaded automatically at startup.
> 
> So it's a quite low-level mechanism not really useful for the end user.
> Unless maybe, you generate a loaddefs file for a bunch of third-party
> libraries that you want to use and you did not install them with package
> manager or the OS. Then it may make sense to build a loaddefs file
> yourself.
> 
> Michael.

Would you see benefits in using a loaddefs file for those writing their own
minor modes and customisation files ?  Autoloading could be useful if things
could be made easier to set up.




  reply	other threads:[~2023-06-24 11:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 11:09 ;;;###autoload declarations uzibalqa
2023-06-23 16:08 ` Michael Heerdegen
2023-06-23 16:42   ` uzibalqa
2023-06-24  2:02     ` Michael Heerdegen
2023-06-24 11:27       ` uzibalqa [this message]
2023-06-25  1:55         ` Michael Heerdegen
2023-06-23 18:26   ` Emanuel Berg
2023-06-26 13:27     ` [External] : " Drew Adams
2023-06-30 15:35       ` Emanuel Berg
2023-07-03 15:59         ` Drew Adams

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='Xuijxauvkcws2udK_4hLOV18vSFikKRin9iuSxbNeXKH4eQbD6GzqL3pRzxqydYz0jMghWLhiiqeQ20TM10J32gLsM2hm4lLdUmCtc6ugGA=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.