stumpwm-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [STUMP] starting up


From: Manuel Giraud
Subject: Re: [STUMP] starting up
Date: Tue, 29 Jun 2004 09:16:28 +0200
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

address@hidden (Eugene N. Tyurin) writes:

> Hello,
>
> I just started playing with stumpwm, and would really appreciate if those
> who have spent some time setting it up would share their recipees.
>
> Right now I have stumpwm started from .xsession via detachtty - but how
> do I connect to it from slime and make changes?
>

My .xsession looks like this :

      lisp -init $HOME/.stumpwm

I start CMUCL with a specific init file that adds personnal command and
then loads stumpwm. Then I connect with slime when needed.

> If I try to start a program with Ctrl-t :, I get the following error
> message:
>
> Error in KERNEL::UNBOUND-SYSTEM-ERROR-HANDLER: the variable
> /USR/BIN/ATERM is unbound
>

By default 'Ctrl-t :' is bound to 'eval-line which try to eval a lisp
sexp plus there is no reference to /usr/bin/aterm in the stumpwm
code. Have you modified a stumpwm variable that talk about 'aterm'? Can
you provide backtrace on this error?

> How do I make sure that after Ctrl-Alt-Bksp stumpwm cleans up after itself?
>

Don't know. I've defined the following command:
  (set-key-binding #\q '(:control) (lambda (s) (error 'stumpwm-quit)))

But I don't think it is cleaner.

> And what is the meaning of "frame"?  I can't seem to get this right:
> Ctrl-t S to split, Ctrl-t f 1 to select an "alternative frame" - and
> then...
>

A frame provide you the hability to split your screen (i.e. you will
have multiple windows visible at the same time). Example:

   Your are in emacs. You go : 'Ctrl-t s' 'Ctrl-t f 1' 'Ctrl-t ! xterm'
   and now you have an emacs and a xterm ('Ctrl-t r' -> back to normal)

I'm not an expert as I'm not a big fan of frames.

-- 
Manuel Giraud

ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,





reply via email to

[Prev in Thread] Current Thread [Next in Thread]