e frame automatically under the mouse, when the user
> move it
>
> It could then be used easily in the configuration file:
>
> set mousefocuspolicy click
BLASPHEMY ! HERESY ! ;-)
No , actually this is a good idea ; I would find useful
ed". This would mean that in the next release the man page will warn
people of this fact and inform them that the functionality has now become
part of ratpoison itself. And then in some late release , sloppy.c can be
ratpoisoned !
--
Spiros Bousbouras
_
On Monday 2017-08-07 Jeremie Courreges-Anglas wrote :
> As I already said on this list, mouse-focus support is likely to be
> accepted if someone actually takes the time to discuss and implement it,
> from scratch or using the work done by folks like Jeff Abrahamson.
What about the patch submitted
On Sunday 2017-08-27 Will Storey wrote :
> static void
> concat_width (struct sbuf *buf, char *s, int width)
I would turn this to const char *s
> + int i = 0;
> + /* The size of a character in bytes. */
> + int char_len = 0;
> + /* Index of the current character in the string. */
> + in
On Sunday 2017-08-27 Will Storey wrote :
> +void __test_concat_width(void)
Identifiers starting with __ are reserved for the C standard. A name like
rtp_test_concat_width seems fine to me.
___
Ratpoison-devel mailing list
Ratpoison-devel@nongnu.org
UserLAnd and should be reported to its maintainers. So I would say you
should continue to run ratpoison and see if any crash of ratpoison
(assuming this is what happens , you're not clear enough) affects the rest of
the system. If it does , you should report it to t
On Sun, 4 Apr 2021 13:11:42 -0700 Ian Hickson wrote :
> On Sun, Apr 4, 2021 at 2:41 AM Axel Svensson wrote:
> When this problem manifests, it doesn't matter where I move the focus. I
> can manually shift the focus around to different frames (using "focusleft",
> "focusdown", etc), and in each c
