• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

AUTHORSH A D30-Apr-200177 32

ChangeLogH A D13-Mar-20101.3 KiB2928

INSTALLH A D22-Jun-20007 KiB173132

LICENSEH A D30-Apr-20011.1 KiB2117

Makefile.amH A D30-Apr-20013.7 KiB129117

Makefile.inH A D13-Mar-201023 KiB745651

READMEH A D13-Mar-20104.1 KiB9978

TODOH A D30-Apr-200129 21

acinclude.m4H A D03-Oct-20056.9 KiB256224

aclocal.m4H A D13-Mar-201034.2 KiB965867

autogen.shH A D03-Oct-2005144 129

config.h.inH A D13-Mar-20101.5 KiB5939

configureH A D13-Mar-2010193.4 KiB6,9535,779

configure.inH A D13-Mar-2010541 2920

depcompH A D03-Oct-200515.6 KiB531330

install-shH A D03-Oct-20059 KiB324189

main.cH A D03-Oct-20056.3 KiB268213

missingH A D03-Oct-200510.8 KiB361268

mkinstalldirsH A D03-Oct-20053.4 KiB159109

README

1
2                                 NUMLOCKX 1.2
3
4This little thingy allows you to start X with NumLock turned on ( which is
5 a feature that a lot of people seem to miss and nobody really knew how to
6 achieve this ).
7This code relies on X extensions called XTest and XKB, so you need to have
8 at least one of these X extensions installed ( you most probably do ).
9
10Please note that I'm not interested in problems caused by your distribution
11 being different from mine. NumLockX is written so it should work on plain X,
12 and I don't have the time to play with all distros there are, sorry.
13 If it doesn't work with your distro because they changed something
14 in the configuration files, bother them to include this package with their
15 next release ( with the necessary modifications ). It's much better that way,
16 since NumLockX requires modifications of several files and it's better if
17 they do the changes themselves. This is supposed to be the last version
18 of NumLockX anyway ( hopefully ).
19The same way, please don't send me any binary packages. Such packages simply
20 can't be good because they need to modify files that don't belong to them.
21 Please bother your favourite distribution instead.
22
23QUICK INSTALL :
24
25First of all, make sure this package isn't already included in your
26 distribution ( e.g. Mandrake includes it ). If you distribution already
27 includes NumLockX, use their package instead ( it needn't be necessarily
28 called NumLockX, it may be e.g. part of some other package ).
29
30Otherwise, do :
31  ./configure
32  make
33  make install
34  make xsetup
35  make xinitrc
36
37If everything compiles, installs and works fine, you're done. Great :) .
38
39DETAILED INSTALL :
40
41First of all, make sure this package isn't already included in your
42 distribution ( e.g. Mandrake includes it ). If you distribution already
43 includes NumLockX, use it instead. To find out if your distribution includes
44 NumLockX, read the docs, or see if there's a package called 'numlock'
45 or similar.
46
47Otherwise, do :
48  ./configure
49  make
50  make install
51
52'make install' will put the executable in your <X directory>/bin directory.
53Do 'numlockx ?' for usage.
54Now you need to call it somewhere while starting X and it will always
55 make X start with NumLock turned on.
56
57If you use kdm ( xdm, whatever ... simply if X starts automatically ), add
58 a line containing '/usr/X11R6/bin/numlockx on' ( assuming that the compiled
59 binary is in /usr/X11R6/bin ) somewhere in file /etc/X11/xdm/Xsetup_0
60 ( make xsetup will do this ). For people using startx, put that line somewhere
61 at the beginning of file /etc/X11/xinit/xinitrc ( make xinitrc will do this ).
62 In case you don't know if you use kdm/xdm/... or startx, simply modify both
63 files.
64Both 'make xsetup' and 'make xinitrc' copy your original Xsetup_0 and xinitrc
65 to Xsetup_0.sav and xinitrc.sav respectively in numlockx build directory
66 in case something goes wrong.
67'make xsetup_uninstall' and 'make xinitrc_uninstall' remove changes made
68 in Xsetup_0 and xinitrc.
69
70PROBLEMS :
71
72First of all, let me repeat that I'm not interested in your distribution
73 specific problems. It works fine here, and I don't time to bother with your
74 distro, sorry. Try to bother your distribution to include this package
75 with their next release with the necessary changes.
76
77If it doesn't compile, there are two possibilities :
78 - You have XTest or XKB, but configure failed to find it. Do 'xdpyinfo' and
79   look for 'XTEST' or 'XKB' in the list of extensions.
80 - You have neither XTest nor XKB ... bad luck :(.
81If the executable doesn't work ... bad luck :( .
82If configure fails to find Xsetup_0 or xinitrc, because you have them elsewhere
83 than in the directories where configure script looks for them, do the change
84 manually.
85If you're not root and therefore you can modify neither Xsetup_0 nor xinitrc,
86 you can use your ~/.xinitrc ( in your home directory ). NumLock won't be
87 turned on in kdm/xdm/... but it will be turned on after starting your X
88 session ( you may use 'make user_xinitrc' to do this ).
89
90
91Thanks to
92 Oswald Buddenhagen <ossi@kde.org> for the XKB way of doing things.
93 Chris Vanden Berghe <Chris@vandenberghe.org> for toggle option.
94
95
96Lubos Lunak
97l.lunak@kde.org
98
99