Re: uploading xserver-xorg-input-synaptics [was Re: xserver-xorg-input-synaptics: Changes to 'upstream']
On Mon, May 11, 2009 at 09:26:23AM -0400, David Nusinow wrote: Mattia Dongili wrote: On Mon, May 11, 2009 at 10:04:49AM +0200, Julien Cristau wrote: ... xserver-xorg-input-synaptics (1.1.1~git20090510-1) unreleased; urgency=low [ David Nusinow ] * Add NEWS.Debian entry about enabling tapping again (closes: #497523) I think it'd be nice if the NEWS entry explained how to do this with synclient rather than xorg.conf / hal. The disadvantage with synclient is that the configuration is not persistent. The xorg.conf way probably needs things like a ServerLayout section, and I'm not sure how well it'll keep working. And fdi is not quite a nice config file format. Or we could point at gpointing-device-settings, since that has been accepted in the archive now. How about showing the synclient command line and pointing at the existing documentation for how to configure hal/xorg.conf? Something along the lines of: * Tapping has been disabled by default on many touchpads by upstream. If you want to re-enable it, you can do so from within the X environment by running the following commands in a terminal: $ synclient TapButton1=1 $ synclient TapButton2=2 $ synclient TapButton3=3 Note that the configuration will not be permanently modified, to do so please read the documentation about how to set up your xorg.conf file in the synaptics(4) manpage or in /usr/share/doc/xserver-xorg-input-synaptics. Another alternative is to use desktop environment specific tools like gpointing-device-settings or touchfreeze. Thoughts? This sounds good to me, although it might be a good idea to write either a section in the manpage devoted to setting this up and pointing users to that section in the NEWS file (e.g. Please see the section Tapping in your xorg.conf) so that users don't have to crawl through the entire manpage for what's very likely going to be a common thing. Hmmm, I'm unsure about how appropriate it would be to have a section just for tapping. Pointing to the NOTES section should be good though. I'll add a few words about tapping being disabled by default and the TapButton* options being the ones to look for. How's this? Index: xserver-xorg-input-synaptics/man/synaptics.man === --- xserver-xorg-input-synaptics.orig/man/synaptics.man 2009-05-13 00:14:36.753651106 +0900 +++ xserver-xorg-input-synaptics/man/synaptics.man 2009-05-13 00:27:28.785651827 +0900 @@ -813,6 +813,9 @@ vertical scrolling is enabled, horizontal two-finger scrolling is disabled and edge scrolling is disabled. If no multi-finger capabilities are reported, edge scrolling is enabled for both horizontal and vertical scrolling. +Tapping is disabled by default for touchpads with two buttons or more, to enable +it you need to map tap actions to buttons. See the TapButton1, TapButton2 +and TapButton3 option descriptions for their meaning. .LP Button mapping for physical buttons is handled in the server. If the device is switched to left-handed (an in-server mapping of physical and this: xserver-xorg-input-synaptics (1.1.1~git20090510-1) unstable; urgency=low * Tapping has been disabled by default on many touchpads by upstream, see the NOTES section in the synaptics(4) manpage for a short overview about how defaults are calculated. If you want to re-enable it, you can do so from within the X environment by running the following commands in a terminal: $ synclient TapButton1=1 $ synclient TapButton2=2 $ synclient TapButton3=3 Note that the configuration will not be permanently modified, to do so assign the above option values in your xorg.conf or custom fdi file (see the synaptics(4) manpage or the documents in /usr/share/doc/xserver-xorg-input-synaptics for additional details). Another alternative is to use desktop environment specific tools like gpointing-device-settings or touchfreeze. -- David Nusinow dnusi...@debian.org Sat, 11 Apr 2009 16:23:11 -0400 -- mattia :wq! -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: uploading xserver-xorg-input-synaptics [was Re: xserver-xorg-input-synaptics: Changes to 'upstream']
Mattia Dongili wrote: On Mon, May 11, 2009 at 09:26:23AM -0400, David Nusinow wrote: Mattia Dongili wrote: On Mon, May 11, 2009 at 10:04:49AM +0200, Julien Cristau wrote: ... xserver-xorg-input-synaptics (1.1.1~git20090510-1) unreleased; urgency=low [ David Nusinow ] * Add NEWS.Debian entry about enabling tapping again (closes: #497523) I think it'd be nice if the NEWS entry explained how to do this with synclient rather than xorg.conf / hal. The disadvantage with synclient is that the configuration is not persistent. The xorg.conf way probably needs things like a ServerLayout section, and I'm not sure how well it'll keep working. And fdi is not quite a nice config file format. Or we could point at gpointing-device-settings, since that has been accepted in the archive now. How about showing the synclient command line and pointing at the existing documentation for how to configure hal/xorg.conf? Something along the lines of: * Tapping has been disabled by default on many touchpads by upstream. If you want to re-enable it, you can do so from within the X environment by running the following commands in a terminal: $ synclient TapButton1=1 $ synclient TapButton2=2 $ synclient TapButton3=3 Note that the configuration will not be permanently modified, to do so please read the documentation about how to set up your xorg.conf file in the synaptics(4) manpage or in /usr/share/doc/xserver-xorg-input-synaptics. Another alternative is to use desktop environment specific tools like gpointing-device-settings or touchfreeze. Thoughts? This sounds good to me, although it might be a good idea to write either a section in the manpage devoted to setting this up and pointing users to that section in the NEWS file (e.g. Please see the section Tapping in your xorg.conf) so that users don't have to crawl through the entire manpage for what's very likely going to be a common thing. Hmmm, I'm unsure about how appropriate it would be to have a section just for tapping. Pointing to the NOTES section should be good though. I'll add a few words about tapping being disabled by default and the TapButton* options being the ones to look for. How's this? Index: xserver-xorg-input-synaptics/man/synaptics.man === --- xserver-xorg-input-synaptics.orig/man/synaptics.man 2009-05-13 00:14:36.753651106 +0900 +++ xserver-xorg-input-synaptics/man/synaptics.man 2009-05-13 00:27:28.785651827 +0900 @@ -813,6 +813,9 @@ vertical scrolling is enabled, horizontal two-finger scrolling is disabled and edge scrolling is disabled. If no multi-finger capabilities are reported, edge scrolling is enabled for both horizontal and vertical scrolling. +Tapping is disabled by default for touchpads with two buttons or more, to enable +it you need to map tap actions to buttons. See the TapButton1, TapButton2 +and TapButton3 option descriptions for their meaning. .LP Button mapping for physical buttons is handled in the server. If the device is switched to left-handed (an in-server mapping of physical and this: xserver-xorg-input-synaptics (1.1.1~git20090510-1) unstable; urgency=low * Tapping has been disabled by default on many touchpads by upstream, see the NOTES section in the synaptics(4) manpage for a short overview about how defaults are calculated. If you want to re-enable it, you can do so from within the X environment by running the following commands in a terminal: $ synclient TapButton1=1 $ synclient TapButton2=2 $ synclient TapButton3=3 Note that the configuration will not be permanently modified, to do so assign the above option values in your xorg.conf or custom fdi file (see the synaptics(4) manpage or the documents in /usr/share/doc/xserver-xorg-input-synaptics for additional details). Another alternative is to use desktop environment specific tools like gpointing-device-settings or touchfreeze. -- David Nusinow dnusi...@debian.org Sat, 11 Apr 2009 16:23:11 -0400 Looks good to me. - David Nusinow -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: uploading xserver-xorg-input-synaptics [was Re: xserver-xorg-input-synaptics: Changes to 'upstream']
On Mon, May 11, 2009 at 08:08:43 +0900, Mattia Dongili wrote: Later tonight (JST), if nobody objects, I'd like to upload a new xserver-xorg-input-synaptics based on the current upstream code of the 1.1 branch. Sounds good! xserver-xorg-input-synaptics (1.1.1~git20090510-1) unreleased; urgency=low [ David Nusinow ] * Add NEWS.Debian entry about enabling tapping again (closes: #497523) I think it'd be nice if the NEWS entry explained how to do this with synclient rather than xorg.conf / hal. The xorg.conf way probably needs things like a ServerLayout section, and I'm not sure how well it'll keep working. And fdi is not quite a nice config file format. Or we could point at gpointing-device-settings, since that has been accepted in the archive now. Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: uploading xserver-xorg-input-synaptics [was Re: xserver-xorg-input-synaptics: Changes to 'upstream']
On Mon, May 11, 2009 at 10:04:49AM +0200, Julien Cristau wrote: On Mon, May 11, 2009 at 08:08:43 +0900, Mattia Dongili wrote: Later tonight (JST), if nobody objects, I'd like to upload a new xserver-xorg-input-synaptics based on the current upstream code of the 1.1 branch. Sounds good! Excellent, let's figure out a good wording for the NEWS file and I'll upload it. xserver-xorg-input-synaptics (1.1.1~git20090510-1) unreleased; urgency=low [ David Nusinow ] * Add NEWS.Debian entry about enabling tapping again (closes: #497523) I think it'd be nice if the NEWS entry explained how to do this with synclient rather than xorg.conf / hal. The disadvantage with synclient is that the configuration is not persistent. The xorg.conf way probably needs things like a ServerLayout section, and I'm not sure how well it'll keep working. And fdi is not quite a nice config file format. Or we could point at gpointing-device-settings, since that has been accepted in the archive now. How about showing the synclient command line and pointing at the existing documentation for how to configure hal/xorg.conf? Something along the lines of: * Tapping has been disabled by default on many touchpads by upstream. If you want to re-enable it, you can do so from within the X environment by running the following commands in a terminal: $ synclient TapButton1=1 $ synclient TapButton2=2 $ synclient TapButton3=3 Note that the configuration will not be permanently modified, to do so please read the documentation about how to set up your xorg.conf file in the synaptics(4) manpage or in /usr/share/doc/xserver-xorg-input-synaptics. Another alternative is to use desktop environment specific tools like gpointing-device-settings or touchfreeze. Thoughts? I'd even go one step further and start Suggest-ing those 2 packages in this upload. PS: I just took a minute to re-read the docs provided in the package and actually I have to say that there is really no need to provide another fdi example, README.Debian points to /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi which already contains plenty of examples (might add the TapButton* options eventually). -- mattia :wq! -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: uploading xserver-xorg-input-synaptics [was Re: xserver-xorg-input-synaptics: Changes to 'upstream']
Mattia Dongili wrote: On Mon, May 11, 2009 at 10:04:49AM +0200, Julien Cristau wrote: On Mon, May 11, 2009 at 08:08:43 +0900, Mattia Dongili wrote: Later tonight (JST), if nobody objects, I'd like to upload a new xserver-xorg-input-synaptics based on the current upstream code of the 1.1 branch. Sounds good! ACK. Excellent, let's figure out a good wording for the NEWS file and I'll upload it. Yeah, I wrote the NEWS entry in order to give users some sort of documentation, but since I don't use synaptics myself it's definitely a suboptimal entry. xserver-xorg-input-synaptics (1.1.1~git20090510-1) unreleased; urgency=low [ David Nusinow ] * Add NEWS.Debian entry about enabling tapping again (closes: #497523) I think it'd be nice if the NEWS entry explained how to do this with synclient rather than xorg.conf / hal. The disadvantage with synclient is that the configuration is not persistent. The xorg.conf way probably needs things like a ServerLayout section, and I'm not sure how well it'll keep working. And fdi is not quite a nice config file format. Or we could point at gpointing-device-settings, since that has been accepted in the archive now. How about showing the synclient command line and pointing at the existing documentation for how to configure hal/xorg.conf? Something along the lines of: * Tapping has been disabled by default on many touchpads by upstream. If you want to re-enable it, you can do so from within the X environment by running the following commands in a terminal: $ synclient TapButton1=1 $ synclient TapButton2=2 $ synclient TapButton3=3 Note that the configuration will not be permanently modified, to do so please read the documentation about how to set up your xorg.conf file in the synaptics(4) manpage or in /usr/share/doc/xserver-xorg-input-synaptics. Another alternative is to use desktop environment specific tools like gpointing-device-settings or touchfreeze. Thoughts? This sounds good to me, although it might be a good idea to write either a section in the manpage devoted to setting this up and pointing users to that section in the NEWS file (e.g. Please see the section Tapping in your xorg.conf) so that users don't have to crawl through the entire manpage for what's very likely going to be a common thing. Another option is a separate document slipped in to /usr/share/doc/xserver-xorg-input-synaptics, but I think a manpage section that can be pushed upstream would be better. - David Nusinow -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
