unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Pimentel (d4n1)" <d4n1@d4n1.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Stumpwm and config.scm
Date: Sun, 19 Feb 2017 11:39:31 -0300	[thread overview]
Message-ID: <E1cfShL-0000Yt-Pt@eggs.gnu.org> (raw)

Guile-wm work too :)On Feb 19, 2017 11:01 AM, "Daniel Pimentel (d4n1)" <d4n1@d4n1.org> wrote:
>
> Thanks Jan,
>
> it' works :)
>
> I'll try with guile-wm.
>
> Happy hacking,On Feb 19, 2017 10:21 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> >
> > Daniel Pimentel (d4n1) writes: 
> >
> > > I add lisp and sbcl-stumpwm in my config.scm but stump binary not 
> > > exist. So it works if I installed sbcl-stumpwm:bin with normal user. 
> > > 
> > > I tried put sbcl-stumpwm: bin in my config but there's an error. I 
> > > didn't put sbcl-stumpwm in my config.scm but I installed sbcl-stumpwm: 
> > > bin and it works. 
> >
> > Yes, in (packages ... I have 
> >
> >       sbcl-stumpwm 
> >       (list sbcl-stumpwm "bin") 
> >
> > I don't know much about the common-lisp environment; I have no clue 
> > whether this is silly or logical.  It seems that setting up a REPL for 
> > lisp is also possible or has to with our stumpwm package or with our 
> > sbcl package...I'd much rather put effort in getting guile-wm to 
> > work... 
> >
> > Confused greetings, 
> > --janneke 
> >
> > -- 
> > Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org 
> > Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  

             reply	other threads:[~2017-02-19 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19 14:39 Daniel Pimentel (d4n1) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-19 14:36 Stumpwm and config.scm Daniel Pimentel (d4n1)
2017-02-19 14:01 Daniel Pimentel (d4n1)
2017-02-19 12:52 Daniel Pimentel (d4n1)
2017-02-19 13:21 ` Jan Nieuwenhuizen
2017-02-19 14:13 ` Huang, Ying

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=E1cfShL-0000Yt-Pt@eggs.gnu.org \
    --to=d4n1@d4n1.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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).