unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Howto run guix.el correctly?
Date: Tue, 02 Dec 2014 10:52:44 +0300	[thread overview]
Message-ID: <87vblusd2r.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPOZ2BvfYDJOSLc=ji1A2nRcrTxNASGFRnKwEdHDG7cuSQ@mail.gmail.com> (Federico Beffa's message of "Mon, 1 Dec 2014 18:15:07 +0100")

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

  reply	other threads:[~2014-12-02  7:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 17:15 Howto run guix.el correctly? Federico Beffa
2014-12-02  7:52 ` Alex Kost [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-21 22:28 Adam Pribyl
2014-11-22  8:03 ` Alex Kost
2014-11-22 10:52   ` Ludovic Courtès
2014-11-22 12:04     ` Alex Kost
2014-11-22 18:49 ` Alex Kost
2014-11-22 21:04   ` Adam Pribyl
2014-11-22 21:11     ` David Thompson
2014-11-22 22:17       ` Ludovic Courtès
2014-11-23  7:01         ` Alex Kost
2014-11-24 20:42           ` Ludovic Courtès
2014-11-25 13:58             ` Alex Kost
2014-11-26 16:23               ` Ludovic Courtès
2014-11-26 20:38                 ` Alex Kost
2014-11-26 22:41                   ` Ludovic Courtès
2014-12-01 12:20                     ` Alex Kost
2014-12-01 12:49                       ` Ludovic Courtès
2014-12-02  7:46                         ` Alex Kost
2014-12-02  8:39                           ` Ludovic Courtès
2014-12-02 19:13                             ` Alex Kost
2014-11-26 20:14     ` Alex Kost

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87vblusd2r.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=beffa@ieee.org \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).