unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: ulm@gentoo.org, gnu-emacs@gentoo.org, emacs-devel@gnu.org
Subject: Re: Where should dynamic modules be installed?
Date: Thu, 24 Oct 2019 17:04:05 +0300	[thread overview]
Message-ID: <83imoexmsq.fsf@gnu.org> (raw)
In-Reply-To: <b3085e6a-53aa-1b62-38bf-e2546eec0ce3@cs.ucla.edu> (message from Paul Eggert on Wed, 23 Oct 2019 17:31:30 -0700)

> > Also, wouldn't it be cleaner if Emacs had a separate variable (analog to
> > image-load-path, custom-theme-load-path, etc.) for loading of dynamic
> > modules, instead of reusing load-path?
> 
> Emacs should do that, yes. How about if we use a variable named 
> 'module-directory' for that? It would work like exec-directory, except 
> for modules.

I think a single directory would be too restrictive, we should have a
path.  And we should use load-path as fallback, because we used that
for several releases.



  parent reply	other threads:[~2019-10-24 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 10:45 Where should dynamic modules be installed? Ulrich Mueller
2019-10-21 13:44 ` Eli Zaretskii
2019-10-21 14:36   ` Ulrich Mueller
2019-10-24  0:31 ` Paul Eggert
2019-10-24 12:02   ` Andy Moreton
2019-10-24 14:28     ` Stefan Monnier
2019-10-24 14:04   ` Eli Zaretskii [this message]
2019-10-24 15:39   ` Ulrich Mueller
     [not found] <mailman.96.1571932821.13349.emacs-devel@gnu.org>
2019-10-24 16:24 ` Ulrich Mueller
2019-10-24 18:36   ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83imoexmsq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=gnu-emacs@gentoo.org \
    --cc=ulm@gentoo.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).