[ANN] Guile-WM 0.1/Guile XCB 1.1

[ANN] Guile-WM 0.1/Guile XCB 1.1

[mark]

Hi all,

I feel like it's time to announce Guile-WM, my stab at an all-Guile
Window Manager. It's actually more of a toolkit for writing X
applications, with the window manager stuff being what's implemented so
far. It includes live REPL support, the usual
keymap/minibuffer/user-defined command paradigm, and more. I'll put the
README at the end of the email.

Archive: http://www.markwitmer.com/dist/guile-wm-0.1.tar.gz
Git:     http://github.com/mwitmer/guile-wm

I've also dramatically revamped Guile XCB. Previously the variable names
and symbols used came directly from the XML-XCB files, and they weren't
very Scheme-y. I've normalized them to typical lowercase-dash-separated
form. I also made the interface "smarter" so that the you don't have
to deal with ugly details of the X protocol when it isn't absolutely
necessary.

On top of the core X protocol stuff, I added an optional (but highly
recommended) event loop that uses delimited continuations to let you
switch back and forth pretty seamlessly between your code and an X event
loop.

Archive: http://www.markwitmer.com/dist/guile-xcb-1.1.tar.gz
Git:     http://github.com/mwitmer/guile-xcb

Feel free to share your ideas, questions, or comments!

Thanks

-- 
Mark Witmer

                         ━━━━━━━━━━━━━━━━━━━━━
                                GUILE-WM


                              Mark Witmer
                          mark@markwitmer.com
                         ━━━━━━━━━━━━━━━━━━━━━


Table of Contents
─────────────────

1 Overview
2 Why?
3 What's Actually Implemented
4 What's Not Implemented
.. 4.1 Wish List
.. 4.2 Even Crazier Wish List
5 Sample
6 Installation and Prerequisites





1 Overview
══════════

  Guile-WM is a framework for creating an X window manager (or any other
  X application, really) and a set of useful modules designed for that
  purpose. Users are encouraged to pick and choose from ones presently
  available and contribute their own as well!

  Guile-WM relies /heavily/ on its user init file. In fact, it won't do
  anything on its own without one. The intention is to provide something
  100% configurable.


2 Why?
══════

  Guile Scheme is just so much fun to work with, I wanted to build my
  house out of it. (Also, StumpWM won't work in my Linux distribution
  right now. And I find LOOP macros unsettling for some reason.)

  I didn't want to build a WM on top of xlib. It's obsolete, or should
  be, anyway. XCB is great, and when I saw that it comes with XML files
  that describe the X protocol so that you can easily implement an X
  client in a different language, I decided to build the whole X client
  stack in Scheme. Why not? So I made Guile XCB. And then, finally, I
  got to work on this.


3 What's Actually Implemented
═════════════════════════════

  • keymaps/minibuffer/user-defined commands: The usual emacs-style
    stuff.
  • tinywm-inspired window management: Though I do some reparenting and
    highlight the focused window.
  • Built-in repl: make changes to the WM while it's running, talk to
    the X server directly (if you're into that kind of thing), integrate
    with Geiser in Emacs, etc. (Note: if you call a procedure that talks
    to the X server, use the metacommand ,post to evalute the
    expression.  That way it'll run inside the event loop on the other
    thread).
  • "icccm" support: Ha ha, not really, but I have a few bits and pieces
    implemented
  • And more! It's completely open, so you could implement whatever
    window-management paradigm you like.


4 What's Not Implemented
════════════════════════

  There's a lot more I'd like to do, but as you can see, it gets
  progressively more grandiose and, um… crazy, perhaps.


4.1 Wish List
─────────────

  • Command-line options. Mainly to let you pick a different init file.
  • A more sophisticated tiling window manager algorithm
  • Some kind of window decoration
  • Built-in replacements for those little X utility programs (xmodmap,
    xsetbg, etc.) I did part of xrandr as a proof-of-concept.
  • A status bar/modeline type thing
  • Antialiased fonts! guile-pango would be good for this.
  • Whatever else you want… ideas (and implementations) welcome.


4.2 Even Crazier Wish List
──────────────────────────

  • Implement enough of a widget toolkit to actually run Guile Emacs
    inside of Guile-WM all on Guile XCB. You would basically be running
    a Lisp-machine at that point and all of your friends will be
    jealous.
  • Add support for XInput2 to Guile XCB w/touch gestures and whatnot
    and build a hackable mobile device interface. Isn't it a tragedy
    that smartphones are becoming the most common type of computer, but
    you can't really hack on them? Real XCB doesn't support XInput2 yet,
    but we don't have to wait for them…
  • Build a WM on top of Wayland. That would require a Scheme Wayland
    client, which could be built along the lines of Guile XCB, since the
    Wayland projects comes with the same kind of XML spec files that XCB
    uses.


5 Sample
════════

  An annotated sample init file is included with the distribution as
  "wm-init-sample.scm". It demonstrates how to set up the configurable
  values in the available modules. Copy it to ~/.guile-wm to try it out.


6 Installation and Prerequisites
════════════════════════════════

  You can use the typical ./configure, make, make install chain to build
  Guile-WM.

  Guile-WM requires Guile XCB and the latest release of Guile (2.0.9).

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Mark H Weaver]

Hi Mark,

mark@markwitmer.com writes:

> I feel like it's time to announce Guile-WM, my stab at an all-Guile
> Window Manager. It's actually more of a toolkit for writing X
> applications, with the window manager stuff being what's implemented so
> far. It includes live REPL support, the usual
> keymap/minibuffer/user-defined command paradigm, and more. [...]
>
> I've also dramatically revamped Guile XCB.

This all sounds very exciting!  Enough so that I finally pulled
guile-xcb and attempted to build it from git.  Unfortunately, I ran into
several problems:

* Although the README says that Guile 2.0.9 is required, the configure
  script will accept nothing less than Guile 2.2.  Since 2.2 does not
  exist yet, it would be good to accept Guile 2.0 in the meantime :)

* After changing 2.2 -> 2.0, the next problem is that the build process
  seems to assume that (xcb xml) is already in Guile's %load-path, but
  the build system doesn't arrange for this.  I worked around this by
  setting GUILE_LOAD_PATH to the build directory.

* After setting GUILE_LOAD_PATH to the build dir, it then tries to load
  the (xcb xml xproto) module, but xproto.scm does not exist anywhere in
  the source tree.

At this point, I give up.  Can you help?

     Thanks,
       Mark

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Amirouche Boubekki]

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

2013/8/24 Mark H Weaver <mhw@netris.org>

> Hi Mark,
>
> mark@markwitmer.com writes:
>
> > I feel like it's time to announce Guile-WM, my stab at an all-Guile
> > Window Manager. It's actually more of a toolkit for writing X
> > applications, with the window manager stuff being what's implemented so
> > far. It includes live REPL support, the usual
> > keymap/minibuffer/user-defined command paradigm, and more. [...]
> >
> > I've also dramatically revamped Guile XCB.
>
> This all sounds very exciting!


Indeed I'm thrilled to have a WM that works like emacs!

[-- Attachment #2: Type: text/html, Size: 1052 bytes --]

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Matt Wette]

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

FYI, there is also "sawfish" : http://sawfish.wikia.com/wiki/Main_Page

I used sawfish (aka sawmill?) many years ago 

On Aug 24, 2013, at 4:07 PM, Amirouche Boubekki wrote:

> 
> 
> 
> 2013/8/24 Mark H Weaver <mhw@netris.org>
> Hi Mark,
> 
> mark@markwitmer.com writes:
> 
> > I feel like it's time to announce Guile-WM, my stab at an all-Guile
> > Window Manager. It's actually more of a toolkit for writing X
> > applications, with the window manager stuff being what's implemented so
> > far. It includes live REPL support, the usual
> > keymap/minibuffer/user-defined command paradigm, and more. [...]
> >
> > I've also dramatically revamped Guile XCB.
> 
> This all sounds very exciting!
> 
> Indeed I'm thrilled to have a WM that works like emacs!


[-- Attachment #2: Type: text/html, Size: 1528 bytes --]

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Klaus Schilling]

From: Matt Wette <mwette@alumni.caltech.edu>
Subject: Re: [ANN] Guile-WM 0.1/Guile XCB 1.1
Date: Sat, 24 Aug 2013 16:40:18 -0700

> FYI, there is also "sawfish" : http://sawfish.wikia.com/wiki/Main_Page
> 
> I used sawfish (aka sawmill?) many years ago 
> 
> On Aug 24, 2013, at 4:07 PM, Amirouche Boubekki wrote:
> 
> > 
> > 
> > 
> > 2013/8/24 Mark H Weaver <mhw@netris.org>
> > This all sounds very exciting!
> > 
> > Indeed I'm thrilled to have a WM that works like emacs!

There is also Stumpwm, a window manager in common lisp. It is created
by dumping a new memory image of an interactive common lisp engine
with a new main function wrapping the repl.

Many years ago, there was SCWM by former leading guile developer Maciej
Stachowiak (or similar), but it has disappeared long since.

Klaus Schilling

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[dsmich]

---- Klaus Schilling <schilling.klaus@web.de> wrote: 
> From: Matt Wette <mwette@alumni.caltech.edu>
> Subject: Re: [ANN] Guile-WM 0.1/Guile XCB 1.1
> Date: Sat, 24 Aug 2013 16:40:18 -0700
> 
> > FYI, there is also "sawfish" : http://sawfish.wikia.com/wiki/Main_Page
> > 
> > I used sawfish (aka sawmill?) many years ago 
> > 
> > On Aug 24, 2013, at 4:07 PM, Amirouche Boubekki wrote:
> > 
> > > 
> > > 
> > > 
> > > 2013/8/24 Mark H Weaver <mhw@netris.org>
> > > This all sounds very exciting!
> > > 
> > > Indeed I'm thrilled to have a WM that works like emacs!
> 
> There is also Stumpwm, a window manager in common lisp. It is created
> by dumping a new memory image of an interactive common lisp engine
> with a new main function wrapping the repl.
> 
> Many years ago, there was SCWM by former leading guile developer Maciej
> Stachowiak (or similar), but it has disappeared long since.


It's still around.  It's still at sourceforge but is now in git.  It requires guile 2.0.  The C code and Scheme code have been mostly de-bitrotted except for the gtk+/gnome interfaces.

-Dale

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[mark.d.witmer]

Mark H Weaver <mhw@netris.org> writes:

> This all sounds very exciting!  Enough so that I finally pulled
> guile-xcb and attempted to build it from git.  Unfortunately, I ran into
> several problems:

Thanks for taking a look at it. I'll see if I can help:

>
> * Although the README says that Guile 2.0.9 is required, the configure
>   script will accept nothing less than Guile 2.2.  Since 2.2 does not
>   exist yet, it would be good to accept Guile 2.0 in the meantime :)

Yes, that's a mistake on my part. I've pushed the necessary change the
configure.ac.

>
> * After changing 2.2 -> 2.0, the next problem is that the build process
>   seems to assume that (xcb xml) is already in Guile's %load-path, but
>   the build system doesn't arrange for this.  I worked around this by
>   setting GUILE_LOAD_PATH to the build directory.

This one has me a bit confused; I compiled it all right with
GUILE_LOAD_PATH unset. Can you send me the output from running make?

> * After setting GUILE_LOAD_PATH to the build dir, it then tries to load
>   the (xcb xml xproto) module, but xproto.scm does not exist anywhere in
>   the source tree.
>

It looks like xcb/event-loop.scm needs to come after xcb/xml/xproto.scm
in Makefile.am. That should fix the problem loading (xcb xml
xproto). There isn't actually any xproto.scm; building the package
generates a .go file directly from xproto.xml.

Thanks,

-- 
Mark Witmer

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Mark H Weaver]

mark.d.witmer@gmail.com writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> * Although the README says that Guile 2.0.9 is required, the configure
>>   script will accept nothing less than Guile 2.2.  Since 2.2 does not
>>   exist yet, it would be good to accept Guile 2.0 in the meantime :)
>
> Yes, that's a mistake on my part. I've pushed the necessary change the
> configure.ac.

Excellent, thanks!

>> * After changing 2.2 -> 2.0, the next problem is that the build process
>>   seems to assume that (xcb xml) is already in Guile's %load-path, but
>>   the build system doesn't arrange for this.  I worked around this by
>>   setting GUILE_LOAD_PATH to the build directory.
>
> This one has me a bit confused; I compiled it all right with
> GUILE_LOAD_PATH unset. Can you send me the output from running make?

Here's what happens on my Debian wheezy system, starting from a pristine
git checkout (using "git clean -dxf"):

--8<---------------cut here---------------start------------->8---
mhw@tines:~/guile-xcb$ ./configure && make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
configure: checking for guile 2.0
configure: checking for guile 2.2
configure: found guile 2.2
checking for Guile site directory... /usr/local/share/guile/site/2.0
checking for guile... /usr/local/bin/guile
checking for guild... /usr/local/bin/guild
checking for guile-config... /usr/local/bin/guile-config
checking Guile lib directory... /usr/local/lib
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
restore=: && backupdir=".am$$" && \
	am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
	rm -rf $backupdir && mkdir $backupdir && \
	if (/bin/bash /home/mhw/guile-xcb/build_aux/missing makeinfo --version) >/dev/null 2>&1; then \
	  for f in guile-xcb.info guile-xcb.info-[0-9] guile-xcb.info-[0-9][0-9] guile-xcb.i[0-9] guile-xcb.i[0-9][0-9]; do \
	    if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
	  done; \
	else :; fi && \
	cd "$am__cwd"; \
	if /bin/bash /home/mhw/guile-xcb/build_aux/missing makeinfo   -I . \
	 -o guile-xcb.info guile-xcb.texi; \
	then \
	  rc=0; \
	  CDPATH="${ZSH_VERSION+.}:" && cd .; \
	else \
	  rc=$?; \
	  CDPATH="${ZSH_VERSION+.}:" && cd . && \
	  $restore $backupdir/* `echo "./guile-xcb.info" | sed 's|[^/]*$||'`; \
	fi; \
	rm -rf $backupdir; exit $rc
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile flow/event-loop.scm --output=flow/event-loop.go
wrote `flow/event-loop.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/records.scm --output=xcb/xml/records.go
wrote `xcb/xml/records.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/enum.scm --output=xcb/xml/enum.go
wrote `xcb/xml/enum.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/type.scm --output=xcb/xml/type.go
wrote `xcb/xml/type.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile language/xml-xcb/support.scm --output=language/xml-xcb/support.go
wrote `language/xml-xcb/support.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/union.scm --output=xcb/xml/union.go
wrote `xcb/xml/union.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/struct.scm --output=xcb/xml/struct.go
wrote `xcb/xml/struct.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/doc.scm --output=xcb/xml/doc.go
wrote `xcb/xml/doc.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/connection.scm --output=xcb/xml/connection.go
wrote `xcb/xml/connection.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile language/xml-xcb/compile-scheme.scm --output=language/xml-xcb/compile-scheme.go
wrote `language/xml-xcb/compile-scheme.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile language/xml-xcb/spec.scm --output=language/xml-xcb/spec.go
wrote `language/xml-xcb/spec.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/xml/xproto.xml --from=xml-xcb --output=xcb/xml/xproto.go
wrote `xcb/xml/xproto.go'
GUILE_FLAGS="-C /home/mhw/guile-xcb" /usr/local/bin/guild compile xcb/event-loop.scm --output=xcb/event-loop.go
Backtrace:
In system/base/target.scm:
  59: 19 [with-target "x86_64-unknown-linux-gnu" ...]
In system/base/compile.scm:
 150: 18 [compile-file "xcb/event-loop.scm" #:output-file ...]
  43: 17 [call-once #<procedure 13682c0 at system/base/compile.scm:56:5 ()>]
In ice-9/boot-9.scm:
 171: 16 [with-throw-handler #t ...]
In system/base/compile.scm:
  59: 15 [#<procedure 1368280 at system/base/compile.scm:58:9 ()>]
 153: 14 [#<procedure 1368300 at system/base/compile.scm:151:8 (port)> #<closed: file 0>]
 216: 13 [read-and-compile #<input: xcb/event-loop.scm 5> #:from ...]
 232: 12 [lp () #f #<module (#{ g117}#) 1509d80>]
 180: 11 [lp (#<procedure compile-tree-il (x e opts)>) (define-module # # ...) ...]
In ice-9/boot-9.scm:
2320: 10 [save-module-excursion #<procedure 169b6c0 at language/scheme/compile-tree-il.scm:29:3 ()>]
In language/scheme/compile-tree-il.scm:
  31: 9 [#<procedure 169b6c0 at language/scheme/compile-tree-il.scm:29:3 ()>]
In ice-9/psyntax.scm:
1091: 8 [expand-top-sequence ((define-module # # # ...)) () ((top)) ...]
 976: 7 [scan ((define-module (xcb event-loop) #:use-module ...)) () ...]
 270: 6 [scan ((#(syntax-object let # ...) (#) (# #) ...)) () ...]
In ice-9/eval.scm:
 411: 5 [eval # ()]
In ice-9/boot-9.scm:
2870: 4 [define-module* (xcb event-loop) #:filename ...]
2845: 3 [resolve-imports ((#) (#) (#) (#) ...)]
2786: 2 [resolve-interface (xcb xml) #:select ...]
In unknown file:
   ?: 1 [scm-error misc-error #f "~A ~S" ("no code for module" (xcb xml)) #f]
In ice-9/boot-9.scm:
 106: 0 [#<procedure 1368240 at ice-9/boot-9.scm:97:6 (thrown-k . args)> misc-error ...]

ice-9/boot-9.scm:106:20: In procedure #<procedure 1368240 at ice-9/boot-9.scm:97:6 (thrown-k . args)>:
ice-9/boot-9.scm:106:20: no code for module (xcb xml)
make: *** [xcb/event-loop.go] Error 1
mhw@tines:~/guile-xcb$ 
--8<---------------cut here---------------end--------------->8---

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[mark]

Mark H Weaver <mhw@netris.org> writes:

> Here's what happens on my Debian wheezy system, starting from a pristine
> git checkout (using "git clean -dxf"):
> ...
> ice-9/boot-9.scm:106:20: In procedure #<procedure 1368240 at ice-9/boot-9.scm:97:6 (thrown-k . args)>:
> ice-9/boot-9.scm:106:20: no code for module (xcb xml)
> make: *** [xcb/event-loop.go] Error 1
> mhw@tines:~/guile-xcb$ 

Thanks for sending this. That was another file placed out of order in
Makefile.am.  I've pushed a fix for that as well now and did a complete
make uninstall/make/make install and it looks all right. I believe
(fingers crossed!) it should build correctly if you pull the latest
changes.

-- 
Mark Witmer

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Mark H Weaver]

mark@markwitmer.com writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> Here's what happens on my Debian wheezy system, starting from a pristine
>> git checkout (using "git clean -dxf"):
>> ...
>> ice-9/boot-9.scm:106:20: In procedure #<procedure 1368240 at ice-9/boot-9.scm:97:6 (thrown-k . args)>:
>> ice-9/boot-9.scm:106:20: no code for module (xcb xml)
>> make: *** [xcb/event-loop.go] Error 1
>> mhw@tines:~/guile-xcb$ 
>
> Thanks for sending this. That was another file placed out of order in
> Makefile.am.  I've pushed a fix for that as well now and did a complete
> make uninstall/make/make install and it looks all right. I believe
> (fingers crossed!) it should build correctly if you pull the latest
> changes.

That fixes the build for me.

    Thanks!
      Mark

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Alex Sassmannshausen]

Hello,

Don't know if anyone else has had any further luck getting guile-wm to
run, but I'm currently hitting the error:
  ERROR: In procedure scm-error:
  ERROR: no code for module (guile-wm shared)

This is after a successful configure; make; make install of both
guile-xcb and guile-wm.

Is there anything else I need to do before using guile-wm?

(I'm invoking it from within an .xinitrc file).

Best wishes,

Alex

>>> "Mark" == Mark H Weaver <mhw@netris.org> writes:

Mark> mark@markwitmer.com writes:
>> Mark H Weaver <mhw@netris.org> writes:
>> 
>>> Here's what happens on my Debian wheezy system, starting from a
>>> pristine git checkout (using "git clean -dxf"): ...
>>> ice-9/boot-9.scm:106:20: In procedure #<procedure 1368240 at
>>> ice-9/boot-9.scm:97:6 (thrown-k . args)>:
>>> ice-9/boot-9.scm:106:20: no code for module (xcb xml) make: ***
>>> [xcb/event-loop.go] Error 1 mhw@tines:~/guile-xcb$
>> 
>> Thanks for sending this. That was another file placed out of
>> order in Makefile.am.  I've pushed a fix for that as well now and
>> did a complete make uninstall/make/make install and it looks all
>> right. I believe (fingers crossed!) it should build correctly if
>> you pull the latest changes.

Mark> That fixes the build for me.

Mark>     Thanks!  Mark

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[mark.d.witmer]

Alex Sassmannshausen <alex.sassmannshausen@gmail.com> writes:

> Hello,
>
> Don't know if anyone else has had any further luck getting guile-wm to
> run, but I'm currently hitting the error:
>   ERROR: In procedure scm-error:
>   ERROR: no code for module (guile-wm shared)
>
> This is after a successful configure; make; make install of both
> guile-xcb and guile-wm.
>
> Is there anything else I need to do before using guile-wm?
>
> (I'm invoking it from within an .xinitrc file).
>
> Best wishes,
>
> Alex
>

Do you know what directory the files for guile-wm were installed in? It
should be your guile site directory (/usr/share/guile/site or something
similar to that). If the directory they are in isn't in the %load-path
variable that's defined when you start Guile, it won't be able to find
them.

When I start guile up, the variable %load-path is the list '("./"
"/usr/share/guile/2.0" "/usr/share/guile/site/2.0"
"/usr/share/guile/site" "/usr/share/guile").

Could you send me yours and also the output of running make install for
Guile WM? I'd like to improve the build script so that it works for
everyone else and not just me!

Thanks for trying this out,

-- 
Mark Witmer

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[dsmich]

---- mark.d.witmer@gmail.com wrote: 
> Alex Sassmannshausen <alex.sassmannshausen@gmail.com> writes:
> 
> When I start guile up, the variable %load-path is the list '("./"
> "/usr/share/guile/2.0" "/usr/share/guile/site/2.0"
> "/usr/share/guile/site" "/usr/share/guile").

Beware!  You really should not have "." in your %load-path for the same reasons you should not have "." in your PATH.

-Dale

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Alex Sassmannshausen]

Hi Mark,

>>>>> "mark" == mark d witmer <mark.d.witmer@gmail.com> writes:
> Do you know what directory the files for guile-wm were installed in?
> It should be your guile site directory (/usr/share/guile/site or
> something similar to that). If the directory they are in isn't in the
> %load-path variable that's defined when you start Guile, it won't be
> able to find them.

You are right — it was a simple path issue. I've double-checked it now
and Guile-WM loads. I will have a play with it, but thanks for your
help!

Best wishes,

Alex

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Mark H Weaver]

Hi Mark,

Shortly after the releases of Guile XCB 1.1 and Guile WM 0.1, some
important problems were fixed in the build system.  Would you be willing
to produce new tarball releases?

Several of us are interested in Guile WM and would like to make it
easier for new users to play with and hack on.  Toward that end, we'd
like to package it for GNU Guix <http://www.gnu.org/s/guix>, which has a
policy of using only upstream tarballs.

    Thanks!
      Mark

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[mark.d.witmer]

Mark H Weaver <mhw@netris.org> writes:

> Hi Mark,
>
> Shortly after the releases of Guile XCB 1.1 and Guile WM 0.1, some
> important problems were fixed in the build system.  Would you be willing
> to produce new tarball releases?
>
> Several of us are interested in Guile WM and would like to make it
> easier for new users to play with and hack on.  Toward that end, we'd
> like to package it for GNU Guix <http://www.gnu.org/s/guix>, which has a
> policy of using only upstream tarballs.
>
>     Thanks!
>       Mark
>
>

Thanks for looking; at your suggestion, I've updated the version numbers
and put new tarballs on my site.

http://www.markwitmer.com/dist/guile-wm-0.2.tar.gz
http://www.markwitmer.com/dist/guile-xcb-1.2.tar.gz

I'm glad there's interest in including guile-wm with guix. Hopefully
I'll have some time in the near future to keep improving it. So far I've
been using it as my only WM for the past few months and it's been
working well within its small feature set. Suggestions or useful patches
would be most welcome!

Thanks

-- 
Mark Witmer

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Ludovic Courtès]

mark.d.witmer@gmail.com skribis:

> Thanks for looking; at your suggestion, I've updated the version numbers
> and put new tarballs on my site.
>
> http://www.markwitmer.com/dist/guile-wm-0.2.tar.gz
> http://www.markwitmer.com/dist/guile-xcb-1.2.tar.gz

Both are now in the GNU distro:

  http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/guile-wm.scm

There were a couple of glitches to work around, notably to get modules
installed under $prefix/share/guile/site/2.0 rather than under Guile’s
own prefix.  (We can discuss this off-line or on IRC if you want.)

Thanks!

Ludo’.

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Feng Shu]

Mark H Weaver <mhw@netris.org> writes:

> Hi Mark,
>
> Shortly after the releases of Guile XCB 1.1 and Guile WM 0.1, some
> important problems were fixed in the build system.  Would you be willing
> to produce new tarball releases?

I am very interested in this project and expect Guile-wm as prowerful as awesome and
stumpwm! 

May be A web page should be build for this project


>
> Several of us are interested in Guile WM and would like to make it
> easier for new users to play with and hack on.  Toward that end, we'd
> like to package it for GNU Guix <http://www.gnu.org/s/guix>, which has a
> policy of using only upstream tarballs.
>
>     Thanks!
>       Mark

-- 

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[mark.d.witmer]

Feng Shu <tumashu@gmail.com> writes:


> I am very interested in this project and expect Guile-wm as prowerful
> as awesome and stumpwm!
>
> May be A web page should be build for this project
>
>

That's an excellent idea. Here are websites for both Guile XCB and
Guile-WM:

http://www.markwitmer.com/guile-xcb/guile-xcb.html
http://www.markwitmer.com/guile-xcb/guile-wm.html

I can't say that Guile-WM is as powerful and awesome as StumpWM
yet, but I think it's got lots of potential.

Thanks

-- 
Mark Witmer

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[msematman]

Seems interesting. 

I noticed that one of the ideas mentioned on the website was to create a
widget set for the wm. I hope this
does not mutate into a full-fledged graphical desktop environment :-) .
Some of us detest having anything heavier than
a wm (such as fluxbox, or stump) on our machines. But, something like a
slit would be nice. Even better if you could bolt into it any kind of  X
program. While I am at it, a tree-like slit would be awesome :-)
(container is a container is a container ...) !

Not that I expect anyone to work on this, i just thought of adding my
thoughts.



On Mon, Dec 2, 2013, at 05:34 AM, mark.d.witmer@gmail.com wrote:
> Feng Shu <tumashu@gmail.com> writes:
> 
> 
> > I am very interested in this project and expect Guile-wm as prowerful
> > as awesome and stumpwm!
> >
> > May be A web page should be build for this project
> >
> >
> 
> That's an excellent idea. Here are websites for both Guile XCB and
> Guile-WM:
> 
> http://www.markwitmer.com/guile-xcb/guile-xcb.html
> http://www.markwitmer.com/guile-xcb/guile-wm.html
> 
> I can't say that Guile-WM is as powerful and awesome as StumpWM
> yet, but I think it's got lots of potential.
> 
> Thanks
> 
> -- 
> Mark Witmer
> 
> 


-- 
  
  msematman@myopera.com

Re: [ANN] Guile-WM 0.1/Guile XCB 1.1

[Feng Shu]

mark.d.witmer@gmail.com writes:

> Feng Shu <tumashu@gmail.com> writes:
>
>
>> I am very interested in this project and expect Guile-wm as prowerful
>> as awesome and stumpwm!
>>
>> May be A web page should be build for this project
>>
>>
>
> That's an excellent idea. Here are websites for both Guile XCB and
> Guile-WM:
>
> http://www.markwitmer.com/guile-xcb/guile-xcb.htmlhttp://www.markwitmer.com/guile-xcb/guile-wm.html
>

Cool -> "Guile Emacs integration: Make Emacs your window manager! " 


> I can't say that Guile-WM is as powerful and awesome as StumpWM
> yet, but I think it's got lots of potential.
>
> Thanks

--