ratpoison-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RP] ratpoison, patches, and the future


From: Joren Van Onder
Subject: Re: [RP] ratpoison, patches, and the future
Date: Tue, 30 Dec 2014 00:02:34 +0100
User-agent: mu4e 0.9.9.6pre3; emacs 24.4.1

Hi Jeff,

I've built your ratpoison and I've been running it today. I've taken a
quick look at your git log to figure out what kind of things you added
or changed from a user perspective (so disregarding internal stuff and
refactoring), just to make sure I'm not missing out on something. I've
come up with pushwindow, pullwindow and focus_policy. Does that sound
right?

I really like the push/pullwindow commands, they make certain things
much easier. In regards to the focus_policy, is there a specific reason
you didn't implement that as a variable (that can be modified with
'set')? Not a big deal ofcourse, but I feel it would be more in line
with how ratpoison is currently being configured.

I also like your plan to support workspaces. As some other people have
said, rpws isn't really all that great. And I'm not sure why the
decision was made to implement workspaces in a perl script of all
things. It is much slower than the native ratpoison commands. These days
I tend to just use ratpoison groups because of this. This works well but
has some obvious limitations, because a ratpoison group is just a group
of windows without any kind of frame layout associated with it. Portings
rpws functionality into ratpoison itself would be great. (I haven't
looked at the code, but it might not be that hard if it's possible to
reuse the already existing group code and add a frame layout and
window->frame mappings (fdump) to each group to make up a workspace.)


Happy holidays,
--
        Joren

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]