[clfswm-devel] Feature request and questions

[Philippe Brochard]

Thomas Sanchez writes:

> Hi,
>
> I'm not entirely sure that it is the right place for this but here is
> some ideas/remarks I got.
>
> I started to test/use clfswm some days ago and some features are
> missing or to hard to use:
>
> * We should be able to create a child frame in an easier way, I'm
> still not sure to have the right shortcut;
>
Second-mode+a is not what you want? It create a named frame in the
current frame.

> * If mod-1 L2 == mod-1 F12, why isn't F12 used ? wouldn't it be
> clearer ?
>
Right, old Stumpwm keysym definition. Fixed with commit d296482.
For others, please update your configuration file if needed.
L1 become F11, L2->F12 and so on.

> * Child frame should be given the possibility to not go outside its root frame:
>    * by extension a frame could not change of screen which isn't a bad
> idea because it leads to some weird case;
>
No, I think it's a feature. But you are right, this can bite you if
you're not aware.


> * What is mod-5 ?
>
Alt Gr

> * We should be able to name some frame or create a group of frame,
> then:
>
second-mode+c: rename current child (works for frames and windows)

To create a group of frame: create a frame and new frames inside it.
You may have to make it fullscreen to be able to create a new frame with
the mouse.

>   * We could decide to hide some frame;
>
second-mode+c: hide the current child (be careful with this, this can be
messy)

>   * Search a frame by name;
>
second-mode+n

you can do the same by numbers (second-mode+u)

> * Changing the default terminal should be easier (I prefer urxvt to
> xterm) !
>
Add this in your configuration file:

--------------------------------------------------
(defun local-binding ()
  (define-shell ("t") b-start-xterm "start an xterm" "cd $HOME && exec urxvt"))

(add-hook *binding-hook* 'local-binding)
--------------------------------------------------

But you're right this needs to be configurable.


> * We should be able to reorganise automatically the frame according to
> some predefined layout (tiling);
>
hmmm..., this is all what clfswm is about!

second-mode+f+l : open the layout menu.

> * I run the trunk version of the code and I haven't the default cursor
> but a cross instead...
>
Yes, this is done externally for now with 

xsetroot -cursor_name left_ptr 

in your .xsession/.xinitrc/.XClients/whatever.

> * is there some logs ?
>
Yes, but they're disabled by default. Recompile clfswm with the two
lines uncommented in load.lisp:

;;;;; Uncomment the line below if you want to see all ignored X errors
(pushnew :xlib-debug *features*)

;;;;; Uncomment the line below if you want to see all event debug messages
(pushnew :event-debug *features*)


> * Having the possibility to focus automatically the frame under the
> cursor could be useful.
>
(setf *default-focus-policy* :click)

 "Default mouse focus policy. One of :click, :sloppy, :sloppy-strict or :sloppy-select."


Please, read the documentation! All is auto documented on it. CLFSWM is
here since more than 6 years and, I know, it's really dense.

But those informations must be in the FAQ on the wiki. (As soon as I've
time).

> Other thing, maybe a bug:
> I have 2 frames, one with chromium, one empty.
> I decide to write a mail on gmail, then the website open a new  window
> that take all the space on the frame. I decide to move the window in
> another frame so I do a: alt-t ctrl-x and paste the window
> in another frame. (please see the attached image) each time the new
> frame get the focus, the original frame act like as if I required to
> have its info.
>
Here second-mode+ctrl-x cut the current frame and all its content.
You may have some interest in second-mode+k which open a menu to cut or
copy the current window.

> Thank you !
>
Hope this help.

Philippe