File clickity-paths.patch of Package clickity
--- clickity.html.orig 2010-06-24 07:28:45.000000000 +0200
+++ clickity.html 2010-06-24 07:29:38.000000000 +0200
@@ -40,10 +40,10 @@
autoscanning until an action is performed.</p></dd><dt><span class="term">-j, --jump</span></dt><dd><p>Holding the left button uses the next, rather than current, action in the profile if dwell mode is active. For example, if your profile
is <span class="emphasis"><em>left-click right-click</em></span> dwelling will perform a left click and holding will perform a right click.</p></dd><dt><span class="term">-v, --revert</span></dt><dd><p>After performing an action that was stepped to, the selected action will be restored to the one you started from.</p></dd><dt><span class="term">-p, --profile <code class="filename">name</code></span></dt><dd><p>Use the named profile from the configuration file. If this option is not used, the profile specified by the <span class="emphasis"><em>profile</em></span> option in the configuration
file will be used if it exists. A profile on the command line will override this.</p></dd><dt><span class="term">-h, --help</span></dt><dd><p>Display help for Clickity</p></dd><dt><span class="term">--version</span></dt><dd><p>Display Clickity's version number.</p></dd></dl></div></div><div class="refsect1" title="FILES"><a name="files"></a><h2>FILES</h2><p>Clickity looks for a
-configuration file (clickity/clickity.cfg) in the user configuration
-directory ($XDG_CONFIG_HOME or ~/.config/ or the appropriate place on win32
+configuration file (clickity.cfg) in the user configuration
+directory ($XDG_CONFIG_HOME/clickity or ~/.config/clickity or the appropriate place on win32
systems); failing that, it will look for one in the system-wide
-configuration directory ($XDG_CONFIG_DIRST or /etc/xdg/; not on win32
+configuration directory ($XDG_CONFIG_DIR/clickity or /etc/; not on win32
systems). The configuration file contains two sections, [settings] and
[profiles]. [settings] contains name=value pairs where the names are the
same as the long names for the options without the leading dashes. Options
@@ -51,9 +51,6 @@
take "true" or "false" as their values. [profile] contains profile
definitions consisting of the profile's name, an equal sign, and a list of
action names separated by spaces as if they were included on the command
-line.</p><p>A sample configuration file, clickity/clickity.cfg.sample, is
-installed in the system-wide configuration directory; you can copy it to
-your user configuration directory and edit it to specify your
-preferences.</p><p>As of version 0.1.2, all settings and profiles can be edited using a
+line.</p><p>As of version 0.1.2, all settings and profiles can be edited using a
dialog box from the Preferences item in the menu. They will be saved to a
configuration file in the user configuration directory.</p></div><div class="refsect1" title="EXAMPLES"><a name="examples"></a><h2>EXAMPLES</h2><div class="variablelist"><dl><dt><span class="term">clickity --dwell=1000 --jump --revert left-click right-click middle-click &</span></dt><dd><p>Dwelling left-clicks, holding right-clicks or steps to middle-click, going back to right-click</p></dd><dt><span class="term">clickity --delay=500 -profile=touchpad &</span></dt><dd><p>No dwell, use defined profile</p></dd></dl></div></div><div class="refsect1" title="AUTHORS"><a name="authors"></a><h2>AUTHORS</h2><p>Clickity was written by Eric Bohlman <ericbohlman@gmail.com></p></div></div></body></html>
--- setup.py.orig 2010-06-24 07:26:24.000000000 +0200
+++ setup.py 2010-06-24 07:26:42.000000000 +0200
@@ -12,7 +12,6 @@
data_files=[
('share/man/man1',['clickity.1']),
('share/applications',['clickity.desktop']),
- ('share/icons',['clickity.png']),
- ('/etc/xdg/clickity',['clickity.cfg.sample']),
+ ('share/pixmaps',['clickity.png']),
],
)
--- clickity.1.orig 2010-06-24 07:26:45.000000000 +0200
+++ clickity.1 2010-06-24 07:28:16.000000000 +0200
@@ -190,14 +190,12 @@
.RE
.SH "FILES"
.PP
-Clickity looks for a configuration file (clickity/clickity\&.cfg) in the user configuration directory ($XDG_CONFIG_HOME or ~/\&.config/ or the appropriate place on win32 systems); failing that, it will look for one in the system\-wide configuration directory ($XDG_CONFIG_DIRST or /etc/xdg/; not on win32 systems)\&. The configuration file contains two sections, [settings] and [profiles]\&. [settings] contains name=value pairs where the names are the same as the long names for the options without the leading dashes\&. Options on the command line will override these settings\&. The
+Clickity looks for a configuration file (clickity\&.cfg) in the user configuration directory ($XDG_CONFIG_HOME/clickity or ~/\&.config/clickity or the appropriate place on win32 systems); failing that, it will look for one in the system\-wide configuration directory ($XDG_CONFIG_DIRST/clickity or /etc/clickity; not on win32 systems)\&. The configuration file contains two sections, [settings] and [profiles]\&. [settings] contains name=value pairs where the names are the same as the long names for the options without the leading dashes\&. Options on the command line will override these settings\&. The
\fBjump\fR
and
\fBrevert\fR
options take "true" or "false" as their values\&. [profile] contains profile definitions consisting of the profile\*(Aqs name, an equal sign, and a list of action names separated by spaces as if they were included on the command line\&.
.PP
-A sample configuration file, clickity/clickity\&.cfg\&.sample, is installed in the system\-wide configuration directory; you can copy it to your user configuration directory and edit it to specify your preferences\&.
-.PP
As of version 0\&.1\&.2, all settings and profiles can be edited using a dialog box from the Preferences item in the menu\&. They will be saved to a configuration file in the user configuration directory\&.
.SH "EXAMPLES"
.PP
--- clickity.orig 2010-06-24 07:28:18.000000000 +0200
+++ clickity 2010-06-24 07:28:42.000000000 +0200
@@ -163,13 +163,13 @@
config_dirs=''
else:
config_home=os.environ.get('XDG_CONFIG_HOME') or os.path.expandvars('$HOME/.config')
- config_dirs=os.environ.get('XDG_CONFIG_DIRS') or '/etc/xdg'
+ config_dirs=os.environ.get('XDG_CONFIG_DIRS') or '/etc'
path=os.path.join(config_home,self.cfgpath)
- if not os.path.isfile(path):
+ if not os.path.isdir(path):
path=None
for cfd in config_dirs.split(':'):
path=os.path.join(cfd,self.cfgpath)
- if os.path.isfile(path):
+ if os.path.isdir(path):
break
return path
