[STUMP] date and echo patch

Yo man.  I added C-t a for the date stuff and changed how the windows
list is printed a bit to use a more generic echo function I also made.

I'm just starting out on the clisp thing, so if it's total crap let me
know what needs to be done.

ryan

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/stumpwm-devel

[STUMP] What CLISP to install?

I'm planning to try out stumpwm, and I'm just wondering which CLISP
implementation you would recommend me to install on my GNU/Linux system.

--

-- 
Björn Lindström <bkhl <at> elektrubadur.se>
http://bkhl.elektrubadur.se/

Hearken to the new *Elektrubadur* demo at http://elektrubadur.se/

Re: [STUMP] What CLISP to install?

bkhl <at> elektrubadur.se (Björn Lindström) writes:

> I'm planning to try out stumpwm, and I'm just wondering which CLISP
> implementation you would recommend me to install on my GNU/Linux system.

I would recommend CMUCL or SBCL.

Shawn

[STUMP] Re: [RP] Stump WM

Nikolai Weibull <ratpoison-devel-list <at> pcppopper.org> writes:

> Sorry for posting on this list, but I was wondering about the connection
> between ratpoison and StumpWM.  Both are maintained by Shawn Betts, so
> does this mean that StumpWM will take over the role of ratpoison?

StumpWM has similar goals. It will operate a lot like ratpoison, but
the advantage is that it is written entirely in common lisp. This will
finally give the flexibility and customizability that is basically not
possible with ratpoison. No more sick /bin/sh hacks, no more exporting
internal data in actions.c with def* commands. Just good, wholesome
lisp hacks. The best kind.

The advantage ratpoison has over StumpWM is that it is written in C
and takes <1M of memory to run. StumpWM requires a CL environment and
currently only runs on SBCL and Common Lisp which take their fair
share :). It'd be nice to run it in Gnu CLISP because it's much easier
on memory, but it seems CLX support for CLISP is not very good.

If you haven't heard of StumpWM yet, check it out at:

http://www.nongnu.org/stumpwm

Shawn

[STUMP] cmucl 18d, clx, stumpwm cvs

My experience with stumpwm-cvs is similar to Jay Belanger's.

Here's the dribble session, with debug messages, of stumpwm cvs
with cmucl 18d:

;; Loading #p"/usr/local/lib/cmucl/lib/subsystems/clx-library.x86f".
;; Loading #p"/home/chrisb/stumpwm/stumpwm.lisp".

Warning: This function is undefined:
  READ-KEY
;; Loading #p"/home/chrisb/stumpwm/stumpwm-input.lisp".
;; Loading #p"/home/chrisb/stumpwm/stumpwm-user.lisp".
CMU Common Lisp 18d, running on conewego
Send questions to cmucl-help <at> cons.org. and bug reports to cmucl-imp <at> cons.org.
Loaded subsystems:
    Python 1.0, target Intel x86
    CLOS based on PCL version:  September 16 92 PCL (f)
    CLX X Library MIT R5.02
* (stumpwm:stumpwm "conewego" :display 0)

Error in function XLIB::OPEN-X-STREAM:
   Failed to connect to X11 server: conewego (display 0)

Restarts:
  0: [ABORT] Return to Top-Level.

Debug  (type H for help)

(XLIB::OPEN-X-STREAM "conewego" 0 #<unused-arg>)
Source: Error finding source:

Re: [STUMP] cmucl 18d, clx, stumpwm cvs

Chris Beggy <chrisb <at> kippona.com> writes:

> My experience with stumpwm-cvs is similar to Jay Belanger's.

Yeah, that looks similar to my problem.
Shawn pointed out my problem and helped me fix it.
(Of course, any stupid things I ended up doing I did
on my own.)
The problem is that X wasn't running when I tried to start
StumpWM.  What I did (which I don't think is the standard 
thing to do) is to have a simple shell script to start 
StumpWM, and then call it from .xinitrc.  So my .xinitrc 
looks like

--begin .xinitrc--
rxvt &
startstumpwm
--end .xinitrc----

(I need to have the rxvt terminal running, I'm not sure how to start a
new program in stumpwm without it) and I have the executable file
startstumpwm in my PATH, the file is

--begin startstumpwm--
#!/bin/sh
lisp -load /home/belanger/.bin/stump.lisp
--end startstumpwm----

Hm.  There are more layers here than I remembered.  Anyhow,

Re: [STUMP] cmucl 18d, clx, stumpwm cvs

Jay Belanger <belanger <at> truman.edu> writes:

> (I need to have the rxvt terminal running, I'm not sure how to start a
> new program in stumpwm without it) and I have the executable file
> startstumpwm in my PATH, the file is

Yeah, stumpwm doesn't have the facility to boot programs yet. But
cmucl does, and clocc and a uniform interface for that stuff. In the
next release I'll add something for this.

Shawn

Re: [STUMP] cmucl 18d, clx, stumpwm cvs

On 25 Sep 2003 08:35:03 -0500, Jay Belanger <belanger <at> truman.edu> wrote: 

> Chris Beggy <chrisb <at> kippona.com> writes:
> 
> > My experience with stumpwm-cvs is similar to Jay Belanger's.
> 
> Yeah, that looks similar to my problem.
> Shawn pointed out my problem and helped me fix it.
> (Of course, any stupid things I ended up doing I did
> on my own.)
> The problem is that X wasn't running when I tried to start
> StumpWM.  What I did (which I don't think is the standard 
> thing to do) is to have a simple shell script to start 
> StumpWM, and then call it from .xinitrc.  So my .xinitrc 
> looks like

Thanks!  That's just what I needed to take a test drive.

Chris

Re: [STUMP] cmucl 18d, clx, stumpwm cvs

Jay Belanger writes:

>The problem is that X wasn't running when I tried to start
>StumpWM.  What I did (which I don't think is the standard 
>thing to do) is to have a simple shell script to start 
>StumpWM, and then call it from .xinitrc.  So my .xinitrc 
>looks like
>
>--begin .xinitrc--
>rxvt &
>startstumpwm
>--end .xinitrc----

If you use
xterm -e startstumpwm

or as I do using xdm under Debian 
exec xterm -e startstumpwm & 
in .xsession

you will be able to stop stumpwm, make changes (within lisp) and then restart it
again without leaving X.

>(I need to have the rxvt terminal running, I'm not sure how to start a
>new program in stumpwm without it)

Temporarily I use xbindkeys and ratmenu - previously set up for
ratpoison.

Re: [STUMP] cmucl 18d, clx, stumpwm cvs

Harold Sargeant <harold.sargeant <at> ntlworld.com> writes:
...
> If you use
> xterm -e startstumpwm
> 
> or as I do using xdm under Debian 
> exec xterm -e startstumpwm & 
> in .xsession
> 
> you will be able to stop stumpwm, make changes (within lisp) and then restart it
> again without leaving X.

*Thunk*
Okay, I get it now.
And this is what Shawn meant when he said that he ran StumpWM from 
within emacs.

But then this brings up the obvious question.
If you can run emacs in X without a window manager, who needs a window
manager?  Ratpoison and StumpWM have been nice, but I guess I don't
need them anymore.

> >(I need to have the rxvt terminal running, I'm not sure how to start a
> >new program in stumpwm without it)
> 
> Temporarily I use xbindkeys and ratmenu - previously set up for
> ratpoison.

Oh, yeah, that makes sense.  I never used those when I ran ratpoison,