From pbrochard at common-lisp.net Wed Jun 8 21:00:30 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Wed, 08 Jun 2011 23:00:30 +0200 Subject: [clfswm-devel] CLFSWM 1106 released. Message-ID: <87ei34t4wh.fsf@common-lisp.net> Hi all, I've made a new release of CLFSWM. The main change is a rectangular optimization to not display hidden children by other children. So CLFSWM is more responsive when there is a lot of children to display and when some are hidden by others. Some minor tweaking where also done. See the ChangeLog for more details. Another important change is that ***SVN IS NOT USED ANYMORE*** (as CVS before). The only revision control tool now is GIT. I've been able to setup the common-lisp.net TRAC to follow a GIT repository on common-lisp.net. So the main GIT repository is now at common-lisp.net: http://common-lisp.net/gitweb?p=projects/clfswm/clfswm.git The TRAC is the same as before with SVN: http://trac.common-lisp.net/clfswm/ http://trac.common-lisp.net/clfswm/browser And the old repo.or.cz repository is mirroring the common-lisp.net repository (I push in both). http://repo.or.cz/w/clfswm.git As always, any feedback is welcome (is there always someone using CLFSWM? :) ) Have fun, Philippe From pbrochard at common-lisp.net Mon Jun 13 19:21:49 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 13 Jun 2011 21:21:49 +0200 Subject: [clfswm-devel] Tr: Numlock bug + minor spelling patch In-Reply-To: <4DF558B4.8060900@gmail.com> (Sylvain HENRY's message of "Mon, 13 Jun 2011 02:24:20 +0200") References: <4DF558B4.8060900@gmail.com> Message-ID: <87lix5wn8y.fsf@common-lisp.net> From: Sylvain Henry Hi, After the annoucement about the new release on LinuxFr, I tested clfswm a little bit. I fixed some spelling mistakes. Please find the patch here (I can't send it as attached file to this mail because the latter is rejected as spam): http://hsyl20.fr/~hsyl20/clfswm/0001-Minor-spelling-fix.patch I have found a little bug. When numlock is activated (or maybe when its state changes), Mod1+t, Ctrl+>, Ctrl+Esc, etc. don't work anymore and the focus stays on the same window (even if it gets closed). I have to disable numlock to make it work again. Maybe numlock is considered as a permanent key modifier? Cheers Sylvain From dochang at gmail.com Mon Jun 13 20:07:48 2011 From: dochang at gmail.com (Desmond O. Chang) Date: Tue, 14 Jun 2011 04:07:48 +0800 Subject: [clfswm-devel] CLFSWM 1106 released. In-Reply-To: <87ei34t4wh.fsf@common-lisp.net> References: <87ei34t4wh.fsf@common-lisp.net> Message-ID: Hi Philippe, Congratulations on the new release! I've been using CLFSWM since January. Now it replaces StumpWM and becomes my primary WM. I really like its concept. I'm learning your recent improvements. But these days I'm busy on my projects, so I didn't feedback anything before. Now I'll report the problems I found so far. 1. Better support for multiple screens For example. The "second mode" window is in the center of the whole screen, not one of the physical screens. Another example. The ask-close/kill menu is always on the top-right corner of the whole screen, but the window might be on the left monitor. Maybe we can improve this behaviour. 2. Running commands based on key codes There're 3 PageUp definitions in keysyms.lisp $ git --no-pager grep -in \#xff55 src/keysyms.lisp:93:(cl-define-keysym #xff55 "Prior") ;Prior, previous src/keysyms.lisp:94:(cl-define-keysym #xff55 "Page_Up") src/keysyms.lisp:1923:(cl-define-keysym #xFF55 "SunPageUp") SunPageUp is the last one, so it overrides the others. This causes all the PageUp related keybindings unavailable. I have to reset the keyname to "Page_Up" in the rcfile. I think CLFSWM should associate commands with the key codes instead of key names. 3. How to send the binded keys? Using Mod-4 gets rid of most keybinding conflicts (with emacs) in main mode. But I also want to send several keys to the applications, such as C-Esc or F10. BTW1, dropping SVN is a very very correct decision. BTW2, the new ask-close/kill menu is good. Now I can operate the windows faster. Thanks, Des From pbrochard at common-lisp.net Mon Jun 13 20:33:04 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 13 Jun 2011 22:33:04 +0200 Subject: [clfswm-devel] Tr: [Patch] Disabling maximized window borders In-Reply-To: <4DF61726.3070303@gmail.com> (Sylvain HENRY's message of "Mon, 13 Jun 2011 15:56:54 +0200") References: <4DF61726.3070303@gmail.com> Message-ID: <87aadlqxof.fsf@common-lisp.net> Sylvain HENRY writes: > Hi, > > Attached is a small patch to add an option to disable window's border > when "no-layout" or "maximize-layout" is used. This way, fullscreen > videos don't have a nasty border. :) > > I think it may be further enhanced to remove borders in tiled layouts > when there is only one window in a frame. > > Cheers > Sylvain From pbrochard at common-lisp.net Mon Jun 13 20:45:28 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 13 Jun 2011 22:45:28 +0200 Subject: [clfswm-devel] Tr: Numlock bug + minor spelling patch In-Reply-To: <87lix5wn8y.fsf@common-lisp.net> (Philippe Brochard's message of "Mon, 13 Jun 2011 21:21:49 +0200") References: <4DF558B4.8060900@gmail.com> <87lix5wn8y.fsf@common-lisp.net> Message-ID: <8739jdqx3r.fsf@common-lisp.net> Philippe Brochard writes: > From: Sylvain Henry > > > Hi, > > After the annoucement about the new release on LinuxFr, I tested > clfswm a little bit. > Hi, I've tell you this already in french, but welcome on board. > I fixed some spelling mistakes. Please find the patch here (I can't > send it as attached file to this mail because the latter is rejected > as spam): > http://hsyl20.fr/~hsyl20/clfswm/0001-Minor-spelling-fix.patch > Many thanks for your patch. It's applied in your name. > I have found a little bug. When numlock is activated (or maybe when > its state changes), Mod1+t, Ctrl+>, Ctrl+Esc, etc. don't work anymore > and the focus stays on the same window (even if it gets closed). I > have to disable numlock to make it work again. Maybe numlock is > considered as a permanent key modifier? > Yes, numlock is a permanent key modifier. You have to add '(with-numlock)' in your .clfswmrc to make it works with it. Regards, Philippe From pbrochard at common-lisp.net Mon Jun 13 20:50:12 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 13 Jun 2011 22:50:12 +0200 Subject: [clfswm-devel] Tr: [Patch] Disabling maximized window borders In-Reply-To: <87aadlqxof.fsf@common-lisp.net> (Philippe Brochard's message of "Mon, 13 Jun 2011 22:33:04 +0200") References: <4DF61726.3070303@gmail.com> <87aadlqxof.fsf@common-lisp.net> Message-ID: <87y615pibf.fsf@common-lisp.net> > Sylvain HENRY writes: > > Hi, > Hi, > Attached is a small patch to add an option to disable window's border > when "no-layout" or "maximize-layout" is used. This way, fullscreen > videos don't have a nasty border. :) > > I think it may be further enhanced to remove borders in tiled layouts > when there is only one window in a frame. > A more simple solution to this if you don't like the border around (not so) maximized windows is to 'enter' in them with 'control+up' and then 'Alt+Enter' to maximize them. Another permanent solution is to add this in your .clfswmrc. But you loose a visual information about the current child: -------------------------------------------------- (defun get-fullscreen-size () "Return the size of root child (values rx ry rw rh) You can tweak this to what you want" (values (- (* *border-size* 2)) (- (* *border-size* 2)) (+ (xlib:screen-width *screen*) (* *border-size* 2)) (+ (xlib:screen-height *screen*) (* *border-size* 2)))) -------------------------------------------------- This tells to define the fullscreen size outside the current child border. Regards, Philippe From pbrochard at common-lisp.net Mon Jun 13 21:20:44 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 13 Jun 2011 23:20:44 +0200 Subject: [clfswm-devel] CLFSWM 1106 released. In-Reply-To: (Desmond O. Chang's message of "Tue, 14 Jun 2011 04:07:48 +0800") References: <87ei34t4wh.fsf@common-lisp.net> Message-ID: <87sjrdpgwj.fsf@common-lisp.net> Desmond O. Chang writes: > Hi Philippe, > Hi Des, > Congratulations on the new release! > Thanks! > I've been using CLFSWM since January. Now it replaces StumpWM and > becomes my primary WM. I really like its concept. > Wow, glad to hear this! > I'm learning your recent improvements. But these days I'm busy on my > projects, so I didn't feedback anything before. > > > Now I'll report the problems I found so far. > > 1. Better support for multiple screens > > For example. The "second mode" window is in the center of the > whole screen, not one of the physical screens. > > Another example. The ask-close/kill menu is always on the > top-right corner of the whole screen, but the window might be on > the left monitor. > > Maybe we can improve this behaviour. > You can change all windows positions with the with-placement macro. Have a look at src/clfswm-placement.lisp and src/package.lisp. You can define your own. For example: (setf *second-mode-placement* 'top-left-placement) Feel free to share. I don't use a multiple display this days so if you have something you're happy with, please, tell us. The frame-toggle-maximize function bound to mod-5+return is surely useful. > 2. Running commands based on key codes > > There're 3 PageUp definitions in keysyms.lisp > > $ git --no-pager grep -in \#xff55 > src/keysyms.lisp:93:(cl-define-keysym #xff55 "Prior") ;Prior, previous > src/keysyms.lisp:94:(cl-define-keysym #xff55 "Page_Up") > src/keysyms.lisp:1923:(cl-define-keysym #xFF55 "SunPageUp") > > SunPageUp is the last one, so it overrides the others. This causes > all the PageUp related keybindings unavailable. I have to reset > the keyname to "Page_Up" in the rcfile. > > I think CLFSWM should associate commands with the key codes instead > of key names. > Yes this is boring for me too. So I've repeated the Page_Up definition at the end of the file. BTW you can already define commands with keycodes. In fact, define-*-key accept a keysym, a keycode or a char for there keys. > 3. How to send the binded keys? > > Using Mod-4 gets rid of most keybinding conflicts (with emacs) in > main mode. But I also want to send several keys to the > applications, such as C-Esc or F10. > There is no way for now. If you want to use those bindings, remove them in your .clfswmrc. Something like this: -------------------------------------------------- (defun local-binding () (undefine-main-key ("Escape" :control)) (undefine-main-key ("F10"))) (add-hook *binding-hook* 'local-binding) -------------------------------------------------- > > BTW1, dropping SVN is a very very correct decision. > Yes, I think so! I've to remove all occurrence to SVN in the trac wiki. > BTW2, the new ask-close/kill menu is good. Now I can operate the > windows faster. > Yes that's also the case for me :) While I'm there. Do you have some news about the Debian package? I've seen something about licence problems. Indeed if you have some time! > Thanks, > Best regards, Philippe From dochang at gmail.com Sun Jun 19 05:49:30 2011 From: dochang at gmail.com (Desmond O. Chang) Date: Sun, 19 Jun 2011 13:49:30 +0800 (CST) Subject: [clfswm-devel] CLFSWM 1106 released. In-Reply-To: <87sjrdpgwj.fsf@common-lisp.net> References: <87ei34t4wh.fsf@common-lisp.net> <87sjrdpgwj.fsf@common-lisp.net> Message-ID: <20110619.134930.53274982.dochang@gmail.com> On Mon, 13 Jun 2011 23:20:44 +0200, Philippe Brochard wrote: > Desmond O. Chang writes: >> >> 1. Better support for multiple screens > You can change all windows positions with the with-placement macro. > Have a look at src/clfswm-placement.lisp and src/package.lisp. > You can define your own. > > For example: (setf *second-mode-placement* 'top-left-placement) Now I use *-child-placement. >> 2. Running commands based on key codes > Yes this is boring for me too. So I've repeated the Page_Up definition > at the end of the file. > BTW you can already define commands with keycodes. In fact, define-*-key > accept a keysym, a keycode or a char for there keys. Better Solution is translating keyname to keysym in define-*-key. > While I'm there. Do you have some news about the Debian package? I've > seen something about licence problems. Indeed if you have some time! I'll check the copyright and license text carefully and submit the deb package again. The copyright text in src/keysyms.lisp still has the "stumpwm" word. Is it necessary to update the text? BTW, Is there any Debian Developer on this list? Please join the Debian CL Team. We need more members? Thanks, Des From pbrochard at common-lisp.net Mon Jun 20 20:56:59 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 20 Jun 2011 22:56:59 +0200 Subject: [clfswm-devel] CLFSWM 1106 released. In-Reply-To: <20110619.134930.53274982.dochang@gmail.com> (Desmond O. Chang's message of "Sun, 19 Jun 2011 13:49:30 +0800 (CST)") References: <87ei34t4wh.fsf@common-lisp.net> <87sjrdpgwj.fsf@common-lisp.net> <20110619.134930.53274982.dochang@gmail.com> Message-ID: <87pqm88bms.fsf@common-lisp.net> Desmond O. Chang writes: > On Mon, 13 Jun 2011 23:20:44 +0200, Philippe Brochard wrote: >> Desmond O. Chang writes: >>> >>> 1. Better support for multiple screens >> You can change all windows positions with the with-placement macro. >> Have a look at src/clfswm-placement.lisp and src/package.lisp. >> You can define your own. >> >> For example: (setf *second-mode-placement* 'top-left-placement) > > Now I use *-child-placement. > This is a way to go. Another solution can be to make a new placement system with fixed positions. >>> 2. Running commands based on key codes >> Yes this is boring for me too. So I've repeated the Page_Up definition >> at the end of the file. >> BTW you can already define commands with keycodes. In fact, define-*-key >> accept a keysym, a keycode or a char for there keys. > > Better Solution is translating keyname to keysym in define-*-key. > Yes why not. But this part of the code is from the old clfswm and is pretty hard to change. I'll take a look. >> While I'm there. Do you have some news about the Debian package? I've >> seen something about licence problems. Indeed if you have some time! > > I'll check the copyright and license text carefully and submit the deb > package again. > Ok, thanks a lot. > The copyright text in src/keysyms.lisp still has the "stumpwm" word. > Is it necessary to update the text? > Maybe we've to add a line to claim the ownership of this file but without changing the licence and with the original copyright. > BTW, Is there any Debian Developer on this list? Please join the > Debian CL Team. We need more members? > There is not a lot of member on this list. I can volunteered to be in the Debian CL team (I follow the ML) but I don't use Debian as my main system even if I use it on some machines. Regards, Philippe From dochang at gmail.com Sat Jun 25 20:27:41 2011 From: dochang at gmail.com (Desmond O. Chang) Date: Sun, 26 Jun 2011 04:27:41 +0800 (CST) Subject: [clfswm-devel] CLFSWM 1106 released. In-Reply-To: <87pqm88bms.fsf@common-lisp.net> References: <87sjrdpgwj.fsf@common-lisp.net> <20110619.134930.53274982.dochang@gmail.com> <87pqm88bms.fsf@common-lisp.net> Message-ID: <20110626.042741.116681714.dochang@gmail.com> On Mon, 20 Jun 2011 22:56:59 +0200, Philippe Brochard wrote: > Desmond O. Chang writes: >> BTW, Is there any Debian Developer on this list? Please join the >> Debian CL Team. We need more members? >> > There is not a lot of member on this list. I can volunteered to be in > the Debian CL team (I follow the ML) but I don't use Debian as my main > system even if I use it on some machines. For people who want to join Debian CL Team, please check the team wiki page [1] for details. You need an Alioth [2] account to contribute your code. Once your account is created, request to join the team on the team's mailing list [3]. I recommend "Debian New Maintainers' Guide" [4] as a good start. [1] http://wiki.debian.org/Teams/DebianCommonLisp [2] http://alioth.debian.org/projects/pkg-common-lisp [3] pkg-common-lisp-devel at lists.alioth.debian.org [4] http://www.debian.org/doc/manuals/maint-guide/ From dochang at gmail.com Sat Jun 25 21:18:47 2011 From: dochang at gmail.com (Desmond O. Chang) Date: Sun, 26 Jun 2011 05:18:47 +0800 Subject: [clfswm-devel] [PATCH] CLFSWM should depend on sb-posix since src/tools.lisp uses sb-posix:getenv & sb-posix:putenv. Message-ID: <1309036727-8328-1-git-send-email-dochang@gmail.com> From: "Desmond O. Chang" --- clfswm.asd | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/clfswm.asd b/clfswm.asd index 8884df2..6f27c6d 100644 --- a/clfswm.asd +++ b/clfswm.asd @@ -78,7 +78,7 @@ (:file "bindings-second-mode" :depends-on ("clfswm" "clfswm-util" "clfswm-query" "bindings" "clfswm-pack" "clfswm-menu" "menu-def" "clfswm-layout"))))) - :depends-on ( #-:CLX :clx )) + :depends-on ( #-:CLX :clx #+:sbcl :sb-posix )) -- 1.7.5.4 From pbrochard at common-lisp.net Mon Jun 27 20:27:16 2011 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Mon, 27 Jun 2011 22:27:16 +0200 Subject: [clfswm-devel] [PATCH] CLFSWM should depend on sb-posix since src/tools.lisp uses sb-posix:getenv & sb-posix:putenv. In-Reply-To: <1309036727-8328-1-git-send-email-dochang@gmail.com> (Desmond O. Chang's message of "Sun, 26 Jun 2011 05:18:47 +0800") References: <1309036727-8328-1-git-send-email-dochang@gmail.com> Message-ID: <871uyf3tqz.fsf@common-lisp.net> Ok, commited. Thanks. Desmond O. Chang writes: > From: "Desmond O. Chang" > > --- > clfswm.asd | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/clfswm.asd b/clfswm.asd > index 8884df2..6f27c6d 100644 > --- a/clfswm.asd > +++ b/clfswm.asd > @@ -78,7 +78,7 @@ > (:file "bindings-second-mode" > :depends-on ("clfswm" "clfswm-util" "clfswm-query" "bindings" "clfswm-pack" "clfswm-menu" "menu-def" > "clfswm-layout"))))) > - :depends-on ( #-:CLX :clx )) > + :depends-on ( #-:CLX :clx #+:sbcl :sb-posix ))