unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: guix-devel@gnu.org
Subject: Re: guile-wm / xcb questions
Date: Tue, 12 Dec 2017 14:04:35 +0000	[thread overview]
Message-ID: <20171212140435.rxk4gxdpa7afmz7w@abyayala> (raw)
In-Reply-To: <20171212134448.idrb3orqsltn3scy@abyayala>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

ng0 transcribed 1.8K bytes:
> I am able to use guile-wm. It starts, I can work it for a
> very long time without crashing.
> I'm trying to learn more about it so that I can extend it.
> Now there's a problem where I'm not sure if the problem
> lies within the Guix package or my way to load the module:
> 
> > scheme@(guile-user)> (use-modules (guile-wm module root-keymap))
> > While compiling expression:
> > no code for module (xcb xml)
> 
> guile-wm/modules/root-keymap.scm includes the set-rootkey
> I'm trying to debug in my config of Guile-wm. Now Guile-wm
> depends on Guile-xcb and the store folder of the guile-wm
> build references guile-xcb.
> When guile-wm is installed globally (system-wide) shouldn't
> the xcb module be in my guile load path?

With guile-xcb installed globally it works just fine:


> scheme@(guile-user)> (use-modules (guile-wm module root-keymap))
> 14:01:56 Defining wm init proc for #<directory (guile-wm module message) 23a5640>
> 14:01:56 Defining wm init proc for #<directory (guile-wm module root-keymap) 1b6b960>


-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-12 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 13:44 guile-wm / xcb questions ng0
2017-12-12 14:04 ` ng0 [this message]
2017-12-12 14:52 ` Ricardo Wurmus
2017-12-12 17:25   ` ng0

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=20171212140435.rxk4gxdpa7afmz7w@abyayala \
    --to=ng0@n0.is \
    --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).