Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

> Visual or terminal-based means to configure rudimentary touchpad settings. The fewest options I could imagine supporting for v1 would be: scroll speed/acceleration, scroll speed, natural scrolling toggle, hopefully support for gestures.

You gave up on libinput after an inability to configure scroll speed, but the rest of those are all configurable with libinput and libinput-gestures[1].

I don't use gestures yet and default scroll speed has always been fine, and the following tiny libinput configuration hits the rest of your points.

  $ cat /etc/X11/xorg.conf.d/30-touchpad.conf

  Section "InputClass"
      Identifier "touchpad"
      Driver "libinput"
      MatchIsTouchpad "on"
      Option "Tapping" "on"
      Option "TappingButtonMap" "lrm"
      Option "NaturalScrolling" "true"
  EndSection
Is there a reason you haven't asked the libinput maintainer about whether configurable scroll speed would be welcome upstream (in the prior post, it comes across like your question was far more open ended)? Forking it just to add scroll speed configuration and replicate work that's already been done elsewhere seems a little excessive.

[1] https://github.com/bulletmark/libinput-gestures



Appreciate the actionable ideas re: config file.

As far as the broader configurability questions, it's not so much that I want options libinput doesn't have (though that's a little bit of it).

It's more that I want the default behavior to be good enough where accessing the options aren't necessary (e.g., Macbook). In the event that the default options aren't that good, I want visual settings to tune the experience. Gnome 3 with libinput currently provides two options. Neither is pointer acceleration.

Since much of what I hope to improve the "feel" of default behavior, I don't think this could be as straightforward as "submit a PR to libinput." I think it could end up being a lot of work to get the default experience feeling great. The number of folks with interest in this esoteric subject seems to me like evidence of that.


Why not just create a gnome-widget that does libinput configuration under the hood?

The purpose of the fork cannot be just to provide sane defaults.


> It's more that I want the default behavior to be good enough where accessing the options aren't necessary

Pretty sure that's what the libinput developers want, too.


Is there a way to follow the project? I'd be interested to help out but didn't quickly find a github link or similar.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: