From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kost Subject: Re: Howto run guix.el correctly? Date: Tue, 02 Dec 2014 10:52:44 +0300 Message-ID: <87vblusd2r.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52190) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XviGW-0006oK-G3 for guix-devel@gnu.org; Tue, 02 Dec 2014 02:53:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XviGN-0000eG-EJ for guix-devel@gnu.org; Tue, 02 Dec 2014 02:52:56 -0500 In-Reply-To: (Federico Beffa's message of "Mon, 1 Dec 2014 18:15:07 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Federico Beffa Cc: Guix-devel Federico Beffa (2014-12-01 20:15 +0300) wrote: > AFAIU the initialization of each package is already defined inside each > package by the author. The way emacs's packaging infrastructure works > goes along the lines (see (elisp) Packaging Basics): > > * At installation: > > - Search every Lisp file in the content directory for autoload magic > comments (*note Autoload::). These autoload definitions are saved > to a file named `NAME-autoloads.el' in the package's content > directory. > > - Byte-compiles every Lisp file in the package. > > - Add the package's content directory to `load-path', and evaluates > the autoload definitions in `NAME-autoloads.el'. > > * At startup: > > - Emacs scans for a predefined directory for NAME-autoloads.el files > and evaluates them ('package-initialize' function). We could maybe > exploit 'after-init-hook' or something something similar. Thanks, I know all that stuff. (I'm sorry if it was sounded rude) -- Alex