all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: ;;;###autoload declarations
Date: Sun, 25 Jun 2023 03:55:12 +0200	[thread overview]
Message-ID: <87o7l45mrj.fsf@web.de> (raw)
In-Reply-To: Xuijxauvkcws2udK_4hLOV18vSFikKRin9iuSxbNeXKH4eQbD6GzqL3pRzxqydYz0jMghWLhiiqeQ20TM10J32gLsM2hm4lLdUmCtc6ugGA=@proton.me

uzibalqa <uzibalqa@proton.me> writes:

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

Not really, unless you have tons of such stuff and want to avoid to load
all of it.  Even then, explicit `require' calls or manually added
`autoload' calls may be better/simpler.

Keep in mind that the only thing you get is that you avoid that some
files are loaded into memory in sessions that don't need them.  If you
are the only user of this stuff this is not such a big win.  And the
disadvantage is that you have to remember to rebuild the loaddefs-file
after changing any of the affected files.

If you want to experiment in that direction, a better idea is probably
to build you own packages and install them with the package manager
using a local source (I never tried that myself, though).  Still, I
doubt it's worth the time until your goal is to share that stuff sooner
or later or learn something new.

Michael.




  reply	other threads:[~2023-06-25  1:55 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
2023-06-25  1:55         ` Michael Heerdegen [this message]
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=87o7l45mrj.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@gnu.org \
    /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.