Re: [STUMP] Crash Report

2014-04-26 Thread iii_iii
This one? https://github.com/stumpwm/stumpwm/commit/8a59c96f340351559f87a39685268e8c15a98e0e iii_...@aim.com -Original Message- From: David Bjergaard To: Eric Abrahamsen Cc: stumpwm-devel Sent: Sun, Apr 27, 2014 5:22 am Subject: Re: [STUMP] Crash Report This appears related to

Re: [STUMP] Crash Report

2014-04-26 Thread iii_iii
quot;) 28: (STUMPWM ":0") 29: ((LAMBDA () :IN "/home/lg1/stumpwm/make-image.lisp")) 30: ((FLET #:WITHOUT-INTERRUPTS-BODY-54 :IN SB-EXT:SAVE-LISP-AND-DIE)) 31: ((LABELS SB-IMPL::RESTART-LISP :IN SB-EXT:SAVE-LISP-AND-DIE)) iii_...@aim.com -Original Message- From: Shawn B

Re: [STUMP] Crash Report

2014-04-26 Thread iii_iii
I knew there was somewhere I had seen xrandr mentioned. I get this when I launch an application with wine: err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. The nouveau driver isn't an option though, it

Re: [STUMP] Crash Report

2014-04-26 Thread iii_iii
: width 1920 start 1968 end 2000 total 2228 skew0 clock 73.9KHz v: height 1200 start 1203 end 1209 total 1232 clock 60.0Hz iii_...@aim.com -Original Message- From: David Bjergaard To: iii_iii Cc: Stumpwm-devel Sent: Sat, Apr 26, 2014 7:21 pm Subject: Re

Re: [STUMP] Crash Report

2014-04-26 Thread iii_iii
I am using Opensuse 12.3 The kernel is 3.7.10-1.28-desktop #1 SMP PREEMPT Mon Feb 3 14:11:15 UTC 2014 (c9a2c6c) x86_64 x86_64 x86_64 GNU/Linux Name: sbcl Version : 1.1.2 Release : 2.1.1 Architecture: x86_64 Install Date: Thu 20 Mar 2014 18:45:37 GMT Group : Development/Lang

[STUMP] Crash Report

2014-04-26 Thread iii_iii
Hi, I have received a crash. I haven't pasted the whole thing as I am not sure if it is worth it. I am using an nvidia driver, and I was trying to clone the display onto tv-out. There are warnings about the nvidia driver when I start the system but it works ok most of the time. I usually extend

Re: [STUMP] Windows key prefix key oddity

2014-03-29 Thread iii_iii
x.php/xmodmap "Generally it is not recommended to use xmodmap, except maybe for the simplest tasks. " What I have done seems to work, and as I have done it I should think it's a simple task. :) -Original Message- From: David Bjergaard To: Bernard Hurley Cc: iii_iii ; stum

Re: [STUMP] Windows key prefix key oddity - solved

2014-03-26 Thread iii_iii
Just in case anyone else comes down this road, I have solved this as follows: In .xsession, I put xmodmap -e "clear mod4" xmodmap -e "keycode 133 = hstroke" And in .stumpwmrc I put (set-prefix-key (stumpwm:kbd "hstroke")) It's necessary to refer to hstroke by name in set-prefix-key, although t

Re: [STUMP] Windows key prefix key oddity

2014-03-25 Thread iii_iii
Quote: /If sanity is worth nothing to someone, mapping F9 to backtick _after_ StumpWM is loaded could work. StumpWM seems to grab a set of keycodes,so if they are rewired after StumpWM has found out what the mapping is, you can enter the grave character withut StumpWM minding./ I have fixed thi

Re: [STUMP] Windows key prefix key oddity

2014-03-25 Thread iii_iii
Okay, I have probably confused the issue by telling everything, rather than narrowing it down to a single thing. What I think I have done is set F9 to do the same thing as the "Windows Key", that thing with a Windows logo on it next to the left alt key. The commands I have used to do this are

[STUMP] Windows key prefix key oddity

2014-03-25 Thread iii_iii
Hi I tried to set my windows key as the prefix key according to the instructions in the faq, but it didn't work, so I decided instead to use the grave key. (Backward apostrophe, to the left of 1). This worked, but in order to be able to continue to type the grave character if I needed to, whi