Shawn Betts | 2 May 2008 09:21
Picon

Re: [STUMP] Transparency



On Mon, Mar 17, 2008 at 4:26 PM, Patrice Lespagnol <Patrice.Lespagnol <at> free.fr> wrote:
Hello,

First, thanks very much for this cool wm !

I've just switched from ratpoison to stumpwm. I used to bind 'C-t a'
to a small script that randomly choose one of the cairo-clocks to
display time, during a few seconds at screen center. While with
ratpoison I've gotten all the eye candy of those clocks, with stumpwm
the clock appears inside a bounding black rectangle, without any
transparency. Is there a way to workaround this ?

Currently there is not. I'd like to make the borders optional but they aren't, right now.

-Shawn

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Shawn Betts | 2 May 2008 09:40
Picon

Re: [STUMP] stumpish and utf-8

Thanks! This patch is in git, with a small modification.

-Shawn

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Shawn Betts | 2 May 2008 10:01
Picon

Re: [STUMP] stumpwm can not startup, if (setf *startup-message* nil)



On Sun, Mar 2, 2008 at 6:46 PM, S. P. Tseng <deftsp <at> gmail.com> wrote:

stumpwm can not startup, if (setf *startup-message* nil).
But (setf *startup-message* "") will be ok.

Thanks  for the bug report. This is fixed in git now.

-Shawn

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Shawn Betts | 2 May 2008 10:12
Picon

Re: [STUMP] [PATCH] Fixes for input.lisp

These patches don't fix the problems the FIXMEs highlight. in the case of the cons, it doesn't matter. Maybe a structure would be better but it doesn't really matter. And the unwind-protect does nothing :).

The loop, however, was good so I stole that part. Thanks for that :).

-Shawn

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Vitaly Mayatskih | 2 May 2008 10:33
Picon
Gravatar

Re: [STUMP] stumpish and utf-8

On Fri, May 2, 2008 at 9:40 AM, Shawn Betts <sabetts <at> gmail.com> wrote:

> Thanks! This patch is in git, with a small modification.

Am I right, that string-to-bytes and string-to-utf8 (and their counterparts) are doing the same work?

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Shawn Betts | 2 May 2008 10:52
Picon

Re: [STUMP] [PATCH] Exchange windows; Changed window numbering to start at 1; Delete specific notifications.

Hi Matt,

I threw your patch into git with a few modifications. Thanks!

-Shawn

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Michael Stevens | 2 May 2008 10:59

Re: [STUMP] can't use second screen

2008/4/29 Bob Farrell <robertanthonyfarrell <at> googlemail.com>:
>  I've never tried it with xinerama, but I run Stump on two heads with
>  mergedfb, which seems to simplify things a lot. Here's a section from
>  my /etc/X11/xorg.conf:
>
>  Section "Device"
>         Identifier  "ATI Technologies Inc M22 [Radeon Mobility M300]"
>         Driver      "ati"
>         BusID       "PCI:1:0:0"
>         Option      "DynamicClocks" "true"
>         Option      "VBERestore"        "true"
>         Option          "backingstore"  "true"
>         Option          "RenderAccel"   "true"
>         Option          "VideoOverlay"  "on"
>         Option          "OpenGLOverlay" "off"
>         Option "XAANoOffscreenPixmaps" "true"
>         Option  "UseInternalAGPGART"    "no"
>         Option "MergedFB"       "true"
>         Option "CRT2Position"   "LeftOf"
>         Option "MergedNonRectangular" "true"
>         Option "SWCursor" "true"
>         Option "CRT2HSync" "30-69"
>         Option "CRTVRefresh" "47.5-125"
>         Option "MetaModes" "1680x1050-1280x1024"
>  EndSection

Thanks for the help, but I've worked it out now. it was user error - I
hadn't realised each head would start as separate frames, and was
searching the documentation for ways to switch heads with no luck.

Michael
Shawn Betts | 2 May 2008 11:01
Picon

Re: [STUMP] stumpish and utf-8



On Fri, May 2, 2008 at 1:33 AM, Vitaly Mayatskih <v.mayatskih <at> gmail.com> wrote:
On Fri, May 2, 2008 at 9:40 AM, Shawn Betts <sabetts <at> gmail.com> wrote:

> Thanks! This patch is in git, with a small modification.

Am I right, that string-to-bytes and string-to-utf8 (and their counterparts) are doing the same work?

I don't really know the definitive answer, but I would imagine they don't do exactly the same thing since one always converts to utf8. But perhaps the calls to those functions could really just use the bytes functions and not know the difference.

-Shawn
_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Shawn Betts | 2 May 2008 11:07
Picon

Re: [STUMP] keyboard input capture



On Sat, Apr 12, 2008 at 2:51 AM, Duncan Watts <djmwatts <at> gmail.com> wrote:
Hi

When my laptop is running with a high load, keyboard input meant for
Stumpwm often goes through to the focussed application instead: For
example, I have the prefix mapped to the windows key and use the Fn
keys to switch groups and under load Stumpwm misses the prefix key and
the F1 goes through to firefox bringing up the help page.

With zero knowledge of programming window managers I would have
assumed that all keyboard input passed through stumpwm before being
directed to the appropriate application and would be queued up when
Stumpwm is busy, but this seems not to be the case. Would this be
considered a bug or just the expected behaviour based on the input
model implemented in Stumpwm?

It wasn't always like this. Stumpwm used to capture all input and deal with it properly except sometimes it would mysteriously hang. This had something to do with how stumpwm reserved the top level bindings. It told X to deliver the key event to stumpwm and also freeze the keyboard so no other events would be processed (events would still queue up on the server) until stumpwm thawed the keyboard. It was a great idea and should have worked, but caused too many hangs and I couldn't figure out why (it didnt help that my computer didnt hang except for rare exceptions).

So now stumpwm doesn't freeze the keyboard and computers don't hang. Unfortunately, now you have to be a bit more cautious when sending that second key press.

I would love it if an X guru teleported in and first explain what I was doing wrong and then supply a patch :).

-Shawn

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Shawn Betts | 2 May 2008 11:17
Picon

Re: [stump] stumpwm crashes with clisp 2.44.1


> 'at the top level. Please report this.


Looks like your paste cut off the actual error message.

But it looks to me like there may be a second error in there messing things up: the backtrace may have a nonascii character in it. First things first though. Can you post the full error message? Sorry for the delay in getting back to you on this. I expect this error is long gone.

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

Gmane