Re: [STUMP] Workaround for SBCL hanging in run-prog-collect-output

Shawn <sabetts <at> gmail.com> writes:

> Fredrik Tolf <fredrik <at> dolda2000.com> writes:
>
>> I tried to do that. It seems to work, and I've attached the result.
>
> Thanks Fredrik! I've stuffed it into contrib.

Looks good. :) I still hope to get this fixed in SBCL Real Soon Now(tm).

Regards,
--

-- 
Julian Stecklina

Well, take it from an old hand: the only reason it would be easier to
program in C is that you can't easily express complex problems in C,
so you don't. - Erik Naggum (in comp.lang.lisp)

[STUMP] Compilation failure: format-time-string

Beginning with revision 
d24ee3796009b9a1e40d16517b1c172029b35bf5
compiling stumpwm gives the following error:

Compiling file .../stumpwm/version.lisp ...
*** - EVAL: undefined function FORMAT-TIME-STRING

I compile with clisp 2.43 provided by Gentoo.

--

-- 
Philip

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

Re: [STUMP] Compilation failure: format-time-string

"Philip M. White" <pmw <at> qnan.org> writes:

> Beginning with revision 
> d24ee3796009b9a1e40d16517b1c172029b35bf5
> compiling stumpwm gives the following error:
>
> Compiling file .../stumpwm/version.lisp ...
> *** - EVAL: undefined function FORMAT-TIME-STRING
>
> I compile with clisp 2.43 provided by Gentoo.

Hi Philip,

You need to rerun configure. version.lisp is generated from
version.lisp.in by the configure script.

-Shawn

[STUMP] gentoo package

Hello gentoo stumpwm users,

Apparently the stumpwm package maintainer got sacked for
inactivity. However, robbat2 has kindly offered to proxy-commit
updates to the package if there is anyone here who'd like to take up
the cause.

I've CC'd him to the message, please contact him if you think you have
what it takes.

-Shawn

Re: [STUMP] My patches for saving window placement data in window properties

Michael Raskin <38a938c2 <at> rambler.ru> writes:

> 		Hello
> 	Before fixing or abandoning (and making a forever private branch) my
> patches for saving window placement data in one more semi-persistent
> place, I would like to understand my options..

As we discussed on IRC, perhaps it would be better to dump the desktop
to a string and save it in a property on the root window.

-Shawn

[STUMP] Overlapping frames (reproducible)

Hi.

Michael Raskins has reported a case of overlapping frames but wasn't
able to reproduce it.

I think I can reliably reproduce a case of overlapping frames now, but
the setup is a bit complicated.

I have a frame setup I use for casually watching tv in a small frame
while dicking around on the internet or doing easy work that doesn't
require much concentration.

See attached file .stumpwm-desktop-tv.

I use the large frame in the second column from the left for the main
focus of attention. And when I resize that frame two steps to the right,
I get an error message:

Error In Command 'resize 10 0': The value NIL
                                           is not of type
                                             STUMPWM::HEAD.

With a further resize step, sometimes the "middle frame" will overlap
one of the two frames to its right, or stumpwm will hang.

Sometimes it doesn't hang, but keyboard movement commands will fail.

Also attaching an example of a desktop dump with overlapping frames.

HTH

Re: [STUMP] I want a _tiling_ WM, damn it!

Greg Pfeil <greg <at> technomadic.org> writes:

> I made a small change that should fix this issue (see attached
> diff). Rather than using TRUNCATE when calculating the adjustments for
> the subframes, use FLOOR, this way negative values when shrinking the
> frame won't get underestimated.

I've popped the cork on your patch. Aged perfectly.

-Shawn

Re: [STUMP] I want a _tiling_ WM, damn it!

Hiho!

Shawn schrieb:
> Greg Pfeil <greg <at> technomadic.org> writes:
> > I made a small change that should fix this issue (see attached
> > diff). Rather than using TRUNCATE when calculating the adjustments for
> > the subframes, use FLOOR, this way negative values when shrinking the
> > frame won't get underestimated.
---Zitatende---

This fixes the problems I reported in 
Message-ID: 20081105173133.GA32446 <at> taupan.ath.cx

(At least I'm totally unable to reproduce it now.)

--

-- 
        Friedrich Delgado Friedrichs <friedel <at> nomaden.org>
Laziness led to the invention of the most useful tools.

[STUMP] [PATCH] Use PPCRE for rules matching instead of the "..." syntax.

---
 window-placement.lisp |   20 ++++++++++++--------
 1 files changed, 12 insertions(+), 8 deletions(-)

diff --git a/window-placement.lisp b/window-placement.lisp
index cbb1186..696bab2 100644
--- a/window-placement.lisp
+++ b/window-placement.lisp
 <at>  <at>  -18,19 +18,23  <at>  <at> 
    :plist (make-hash-table)
    :unmap-ignores 0))

+(defvar *rule-scanners-cache* (make-hash-table :test 'equal)
+  "A cache for the ppcre scanners")
+
+(defun get-or-create-rule-scanner (regex)
+  (or (gethash regex *rule-scanners-cache*)
+      (setf (gethash regex *rule-scanners-cache*)
+	    (ppcre:create-scanner regex))))
+
 (defun string-match (string pat)
-  (let ((l (length pat)))
-    (when (> l 0)
-      (if (and (> l 3) (equal (subseq pat 0 3) "..."))
-          (search (subseq pat 3 l) string)
-          (equal string pat)))))
+  (ppcre:scan (get-or-create-rule-scanner pat) string))

 (defun window-matches-properties-p (window &key class instance type role title)
   "Returns T if window matches all the given properties"

[STUMP] [PATCH] Add fprev

This simply adds the opposite of fnext.

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