Development list for the Stump WM.

headers Deepak Tripathi | 17 Apr 2013 08:11 · /sw2wolf/

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

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

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

---
 contrib/mpd.lisp | 60 ++++++++++++++++++++++++++++----------------------------
 1 file changed, 30 insertions(+), 30 deletions(-)

diff --git a/contrib/mpd.lisp b/contrib/mpd.lisp
index 6360cba..68438d5 100644
--- a/contrib/mpd.lisp
+++ b/contrib/mpd.lisp
 <at>  <at>  -47,7 +47,7  <at>  <at> 

 ;;; CODE:

-#-(or sbcl clisp) (error "unimplemented")
+#-(or sbcl clisp ccl) (error "unimplemented")

 (in-package :stumpwm)

 <at>  <at>  -107,7 +107,7  <at>  <at> 
 ;;mpd client
 (defparameter *mpd-socket* nil)
 (defparameter *mpd-server*
-  #+clisp
+  #+(or clisp ccl)
   "localhost"
   #+sbcl
   #(127 0 0 1)
 <at>  <at>  -124,12 +124,14  <at>  <at> 

 (defmacro with-mpd-connection (&body body)
   `(if *mpd-socket*
-       (handler-case (progn , <at> body)
-                     (error (c) (progn
-                                  (message "Error with mpd connection: ~a" c)
-                                  (setf *mpd-socket* nil)
-                                  (when *mpd-timer*
-                                    (cancel-timer *mpd-timer*)))))
+       (handler-case
+           (progn , <at> body)
+         (error (c)
+           (progn
+             (message "Error with mpd connection: ~a" c)
+             (setf *mpd-socket* nil)
+             (when *mpd-timer*
+               (cancel-timer *mpd-timer*)))))
      (message "Error: not connected to mpd")))

 (defun mpd-send (command)
 <at>  <at>  -137,10 +139,12  <at>  <at> 
   (with-mpd-connection
    (#+clisp
     ext:write-char-sequence
-    #+sbcl
+    #+(or sbcl ccl)
     write-sequence
-    (concatenate  'string command (string #\Newline))
-    *mpd-socket*)))
+    (concatenate 'string command (string #\Newline))
+    *mpd-socket*))
+  ;; This doesn't hurt, and on CCL it's necessary:
+  (force-output *mpd-socket*))

 (defun mpd-send-command (cmd)
   (mpd-send cmd)
 <at>  <at>  -181,25 +185,21  <at>  <at> 

 (defun init-mpd-connection ()
   "Connect to mpd server"
-    (setf *mpd-socket*
-          #+clisp
-        (handler-case (socket:socket-connect *mpd-port* *mpd-server*
-                                             :element-type 'character)
-                      ((or system::simple-os-error error)
-                       (err)
-                         (format t  "Error connecting to mpd: ~a~%" err)))
-          #+sbcl
-          (handler-case (let ((s (make-instance 'sb-bsd-sockets:inet-socket
-                                                :type :stream :protocol :tcp)))
-                          (sb-bsd-sockets:socket-connect s *mpd-server*
-                                                         *mpd-port*)
-                          (sb-bsd-sockets:socket-make-stream s
-                                                             :input t
-                                                             :output t
-                                                             :buffering :none))
-                        ((or simple-error error)
-                         (err)
-                       (format t  "Error connecting to mpd: ~a~%" err))))
+  (handler-case
+      (setf *mpd-socket*
+            #+clisp
+            (socket:socket-connect *mpd-port* *mpd-server* :element-type 'character)
+            #+sbcl
+            (let ((s (make-instance 'sb-bsd-sockets:inet-socket
+                                    :type :stream :protocol :tcp)))
+              (sb-bsd-sockets:socket-connect s *mpd-server* *mpd-port*)
+              (sb-bsd-sockets:socket-make-stream s :input t :output t :buffering :none))
+            #+ccl
+            (ccl:make-socket :remote-host *mpd-server*
+                             :remote-port *mpd-port*
+                             :external-format :utf-8))
+    (error (err)
+      (format t  "Error connecting to mpd: ~a~%" err)))
   (when *mpd-socket*
     (when *mpd-timeout*
       (setf *mpd-timer*
--

-- 
1.8.1.4

I'm on archlinux, and learning the colemak keyboard layout. My Stumpwm
prefix key is set to the usual C-t. I notice that if I run:

setxkbmap us -variant colemak

The prefix key is now located at what appears to be C-f (but is actually
still sending a C-t).

But if I use this:

setxkbmap -option 'grp:lalt_lshift_toggle' -variant ',colemak' -layout 'us,us'

And then hit the left alt and shift keys to toggle in and out of
colemak, Stumpwm continues to see C-t as C-t, even though the "t" key
should now be sending a "g".

It only happens for the first press: in fact I can mimic Stumpwm's "C-t
and then quit with C-g" by hitting C-t C-t. The first is read as C-t,
and the second as C-g.

I realize this is just as likely the fault of xkb internals as Stumpwm,
but I wanted to check here first to see if anyone had any experience
with this...

Thanks!
Eric

(ql:quickload :stumpwm)
To load "stumpwm":
   Load 1 ASDF system:
     stumpwm
; Loading "stumpwm"

*** - system::%find-package: There is no package with name "XLIB"
The following restarts are available:
USE-VALUE      :R1      Input a value to be used instead.
SKIP           :R2      skip 1 3 (IN-PACKAGE :XLIB)-1
RETRY          :R3      retry 1 3 (IN-PACKAGE :XLIB)-1
STOP           :R4      stop loading file  
/home/sw2wolf/.cache/common-lisp/clisp-2.49-un
ix-x86/home/sw2wolf/quicklisp/dists/quicklisp/software/stumpwm-20120107-git/workarounds.
fas
TRY-RECOMPILING :R5     Recompile workarounds and try loading it again
RETRY          :R6      Retry loading FASL for #<cl-source-file "stumpwm"  
"workarounds">
.
ACCEPT         :R7      Continue, treating loading FASL for  
#<cl-source-file "stumpwm" "
workarounds"> as having been successful.
ABORT          :R8      Give up on "stumpwm"
ABORT          :R9      Abort main loop
Break 1 [5]> :R9

Best Regards!

It seems I've finally managed to fix the problem. Thanks to Philippe.
I am not completely sure what I have done, but idea is not to call
#'update-configuration and set window-priority on those windows, which
minimal size hints equal maximum hints (if they are set).

I've also added quit hook (because there is start hook but no quit
hook, illogical! :). I use it to save preferences (i.e. chosen
wallpaper in my config) on exit. There is a patch for both the fix and
the hook:
http://pastebin.com/YkSQcWjF

Is anybody watching on stumpwm repo on github? I can make a pull
request if it is needed.

Hello. I started using StumpWM a while ago. I enjoy it much (mostly
because it is written in common lisp and highly customisable), but
there is a problem with fullscreen programs (mostly games).

There are programs (like xonotic, tremulous or warmux) which, if they
are executed in fullscreen mode, draw only black window on screen.
Xonotic, for example, draws nothing on screen (only black screen is
visible) if it is launched with C-t !, but works normal if it is
launched from terminal and if terminal is in the only one frame
present on the screen. But there are programs which run in fullscreen
mode good too (mplayer with -fs key, for example).

Please confirm or refute this, so I can know, if it is only my problem
(i.e. buggy/outdated video driver) or not. If it is a bug, let me know
what can I do. I have experience in Common Lisp, but know nothing how
window managers work and where I can start.

There is some info on versions of software I use:

[vasily <at> vonbraun]: ~> uname -a
FreeBSD vonbraun.vonbraun 9.1-RELEASE FreeBSD 9.1-RELEASE #3 r+aad4bc7: Sun F
eb 10 17:39:11 MSK 2013     vasily <at> vonbraun.vonbraun:/usr/obj/usr/src/sys/MYK
ERNEL  amd64
[vasily <at> vonbraun]: ~> sbcl
This is SBCL 1.1.3, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
...
* stumpwm::*version*
"0.9.7-80-gb1271a9 Compiled On Mon Feb 11 16:34:02"

Hi all,

I'm running StumpWM in Arch linux (compiled from the stumpwm-git AUR
package). I just reinstalled Arch today from scratch today, and Stumpwm
doesn't seem aware of my dual-monitor setup using xrandr. Other window
managers are working fine, but Stumpwm treats the two monitors like one
big head.

I would love to know if there's a way to fix this; if not, is there a
way to explicitly tell StumpWM what the heads to use are? This is a
desktop computer and I always use the same two monitors so I don't mind
hardcoding it in somewhere.

I'm using the open source ati radeon driver in case that makes any
difference. I can't figure out how to get Catalyst to work with my card.

Thanks

Mark Witmer

Hello All,

Recently I did some work to get dbus support in the
battery-portable.lisp contrib file (pull request [here]), but will
looking around the [wiki] I found a page that talks about [modules].

What I'm wondering is: what is the current status of the contrib
directory, and is it better to place modules elsewhere, such as
~/.stumpwm.d/modules (or what have you).

-F

[here] https://github.com/sabetts/stumpwm/pull/15
[wiki] https://github.com/sabetts/stumpwm/wiki
[modules] https://github.com/sabetts/stumpwm/wiki/Modules

I've got a laptop with an external monitor, managed I think by xrandr
(?), anyway not Xinerama. The external monitor basically works fine:
I switch between one and two using two xrandr commands:

one.sh:
#!/bin/sh
xrandr --output LVDS1 --mode 1280x800 --pos 0x0 --rotate normal --output DP1 --off --output VGA1 --off

and 

two.sh:
#!/bin/sh
xrandr --output LVDS1 --mode 1280x800 --pos 1440x100 --rotate normal --output DP1 --off --output VGA1
--mode 1440x900 --pos 0x0 --rotate normal

These are commands saved using arandr.

The laptop boots with the external monitor mirrored, and I create the
second display with the second command. The second display is another
frame, but not another screen (ie *screen-list* returns a list of one).
All this works fine.

The problem occurs when I use the first command above to deactivate the
external monitor. The frames collapse into one, and I get a weird thing
where there are two frames on top of one another. Things initially look
normal, but if I split the frame on my laptop screen, I can see half of
the other (fullscreen) frame still peeping around the side. By switching
and resizing the frames and windows and generally banging on it, I can
eventually get it to rearrange the frames properly.

It's not a disaster, but is annoying. I'm calling the above shell
commands via stumpwm user commands, so if there's anything I can run
before or after to clean things up, that would be very easy. Is there
anything I should be doing differently?

Thanks,
Eric

5	April 2013
8	March 2013
18	February 2013
6	January 2013
7	December 2012
10	November 2012
101	October 2012
18	September 2012
19	August 2012
12	July 2012
14	June 2012
29	May 2012
17	April 2012
40	March 2012
17	February 2012
23	January 2012
25	December 2011
64	November 2011
26	October 2011
23	September 2011
16	August 2011
46	July 2011
34	June 2011
34	May 2011
15	April 2011
108	March 2011
14	February 2011
2	January 2011
12	December 2010
17	November 2010
35	October 2010
25	September 2010
14	August 2010
24	July 2010
28	June 2010
51	May 2010
24	April 2010
20	March 2010
8	February 2010
18	January 2010
46	December 2009
113	November 2009
37	October 2009
95	September 2009
34	August 2009
52	July 2009
53	June 2009
47	May 2009
89	April 2009
61	March 2009
29	February 2009
42	January 2009
40	December 2008
33	November 2008
131	October 2008
52	September 2008
98	August 2008
138	July 2008
75	June 2008
143	May 2008
30	April 2008
39	March 2008
79	February 2008
38	January 2008
14	December 2007
5	November 2007
55	October 2007
10	September 2007
19	August 2007
32	July 2007
5	June 2007
19	May 2007
8	April 2007
1	March 2007
20	February 2007
20	January 2007
7	December 2006
29	November 2006
18	October 2006
11	September 2006
4	August 2006
8	June 2006
8	May 2006
34	April 2006
36	March 2006
1	February 2006
4	January 2006
1	December 2005
1	September 2005
8	July 2005
2	December 2004
14	November 2004
7	October 2004
1	September 2004
11	July 2004
11	June 2004
4	May 2004
2	April 2004
8	March 2004
5	February 2004
2	January 2004
14	October 2003
13	September 2003
1	February 2002

[STUMP] contrib/mpd modules with stumpwm.

[STUMP] contrib/cpu.lisp not working ?

[STUMP] Using conky with stumpwm

[STUMP] [PATCH] Added CCL support to contrib/mpd.lisp

[STUMP] setxkbmap strangeness

[STUMP] clisp load stumpwm error today

Re: [STUMP] Problems with fullscreen games

[STUMP] Problems with fullscreen games

[STUMP] Stumpwm ignores xrandr

[STUMP] Best place for modules

[STUMP] switching screens

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31