unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Merging guix.el
Date: Wed, 27 Aug 2014 17:11:34 +0400	[thread overview]
Message-ID: <87fvgim60p.fsf@gmail.com> (raw)
In-Reply-To: <874mx3z9h2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 23 Aug 2014 14:17:13 +0200")

Hello,

Ludovic Courtès (2014-08-23 16:17 +0400) wrote:

> Hello!
>
> I think we can merge guix.el in the repo anytime now.  Here are some
> notes on how this could be done:
>
>   • Put all the .el and .scm files of the guix.el repo under an emacs/
>     directory.

Done.  I have made “emacs-ui” branch with what I did so far.  But as I
have no experience with autotools, I'm afraid all that stuff need to be
reviewed carefully.

>   • Have them appropriately listed in the top-level Makefile.am (I can
>     help with that, if you’re not familiar.)

Along with the small changes to top-level "Makefile.am", I made
"Makefile.am" in "emacs" dir and...

I imagine there may be... for example vi users, who wouldn't want to
install this feature, so I made some changes in "configure.ac" to add
“--disable-emacs-ui” option.

Also I use almost the same code in "guix-helper.scm.in" that is used in
"scripts/guix.in", so I think it will be good to have some little
additional module with ‘config-lookup’ function.  WDYT?

>   • Add a section in the manual, probably under “Package Management”,
>     describing the interface (probably as a separate .texi file
>     @included from the main one.)  It can come later.

This is new subject for me as well; I'll write it as soon as possible.

For now the most important part of the documentation is that after
installing guix with emacs UI, it may be used by putting:

  (require 'guix-init)

into ".emacs".  After that autoloaded "guix-..." commands should be
available.

-- 
Alex Kost

  parent reply	other threads:[~2014-08-27 13:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23 12:17 Merging guix.el Ludovic Courtès
2014-08-24  6:59 ` Alex Kost
2014-08-25  8:23   ` Ludovic Courtès
2014-08-25 12:31     ` Alex Kost
2014-08-25 22:03       ` Ludovic Courtès
2014-08-26  4:14         ` Alex Kost
2014-08-27 13:11 ` Alex Kost [this message]
2014-08-28 12:41   ` Ludovic Courtès
2014-08-28 18:22     ` Alex Kost
2014-08-28 20:09       ` Ludovic Courtès
2014-08-29 18:24         ` Alex Kost
2014-08-31 14:59           ` Ludovic Courtès
2014-09-01  8:26             ` Alex Kost
2014-09-01 12:10               ` Ludovic Courtès
2014-09-02 20:22                 ` Alex Kost
2014-09-03  7:09                   ` Ludovic Courtès
2014-09-03 20:53                     ` Alex Kost
2014-09-01 22:28               ` Ludovic Courtès
2014-09-02 20:22                 ` Alex Kost
2014-09-02 21:13                   ` Ludovic Courtès
2014-09-02 20:22             ` Alex Kost
2014-09-02 21:09               ` Ludovic Courtès

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=87fvgim60p.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).