unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Howto run guix.el correctly?
Date: Wed, 26 Nov 2014 17:23:51 +0100	[thread overview]
Message-ID: <87y4qyszfs.fsf@gnu.org> (raw)
In-Reply-To: <87vbm3v0ts.fsf@gmail.com> (Alex Kost's message of "Tue, 25 Nov 2014 16:58:39 +0300")

Alex Kost <alezost@gmail.com> skribis:

> As I wrote at
> <http://lists.gnu.org/archive/html/guix-devel/2014-08/msg00165.html>, I
> see the only way to achieve that:
>
> - to modify emacs package recipes so that they will provide some files
>   with all required initial configuration (and to name such file
>   "…-autoloads.el", for example);

‘FOO-autoloads.el’ is the most common convention, right?

> - to modify “guix-init.el” so that (require 'guix-init) will load those
>   autoloads files;
>
> - to write some elisp code for auto-loading "…-autoloads.el" on the fly
>   — i.e., to make it possible to install an Emacs package using
>   "guix.el" and to use "M-x <package-command>" immediately.

Yep, that sounds good.

> So if it's acceptable, what about modifying the current recipes
> step-by-step.  With geiser it's easy: as "geiser-install.el" provides
> all required setup (including autoloads for "M-x …" commands),
> "geiser-autoloads.el" may just be a symlink to "geiser-install.el".  I'm
> attaching the patch for that.

Yes.

> +    (arguments
> +     '(#:phases (alist-cons-after
> +                 'install 'post-install
> +                 (lambda* (#:key outputs #:allow-other-keys)
> +                   (symlink "geiser-install.el"
> +                            (string-append (assoc-ref outputs "out")
> +                                           "/share/emacs/site-lisp/"
> +                                           "geiser-autoloads.el")))
> +                 %standard-phases)))

This particular instance won’t work because it’s called from
$top_builddir.

Actually, since it’s going to be used in most packages, what about
adding an ‘install-autoloads’ procedure in (guix build emacs-utils)?
So the above would become

  (alist-cons-after
   'install 'post-install
   (lambda* (#:key outputs #:allow-other-keys)
     (install-autoloads (assoc-ref outputs "out")))
   %standard-phases)

Or better yet, (guix build emacs-utils) could provide
%standard-emacs-phases.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2014-11-26 16:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 22:28 Howto run guix.el correctly? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2014-12-01 17:15 Federico Beffa
2014-12-02  7:52 ` 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=87y4qyszfs.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --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).