|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
||||
wsconsctl.conf variables
Hi.
I searched how-to reduce the keyboard delay. The problem is that the wsconsctl(8) man's page contains only few examples, not an entire list, and nothing to help me. I found wsconsctl.conf variables on the net : Code:
keyboard.repeat.del1=1 keyboard.repeat.deln=1 Is there an official list of wsconsctl.conf variables/parameters ?
__________________
ThinkPad W500 P8700 6GB HD3650 - faultry ThinkStation P700 2x2620v3 32GB 1050ti 3xSSD 1xHDD Last edited by LeFrettchen; 4th March 2018 at 01:02 AM. Reason: Clarity |
|
|||
For base config files, always check in /etc/examples/
|
|
||||
LeFrettchen does have a point. The wsconsctl(8) manpage only contains a subset of the possible variables as does /etc/examples/wsconsctl.conf, by the way.
/etc/examples/wsconstcl.conf: Code:
keyboard.repeat.del1=200 # change keyboard repeat/delay keyboard.repeat.deln=50 keyboard.encoding=ru # use different keyboard encoding keyboard.bell.volume=0 # mute keyboard beep display.vblank=on # enable vertical sync blank for screen burner display.screen_off=60000 # set screen burner timeout to 60 seconds display.msact=off # disable screen unburn w/ mouse Code:
keyboard.bell.pitch=1200 keyboard.bell.pitch+=200 keyboard.map+="keysym Caps_Lock = Control_L" Code:
display.kbdact if set to on, keyboard activity will unblank the screen. display.outact if set to on, screen output will unblank the screen. |
|
|||
Hi Le Frettchen,
Thanks for posting this question. I was looking for the complete list of wsconsctl.conf variables just yesterday. |
|
|||
wsconsctl sources
Hi LeFrettchen and Hi Le Frettchen.
Are you still interested in this topic? If yes, I write how I searched for information and what I found. I tried to check if the source code is documented and how much. I found that it is documented indeed, but I don't know if developers have something more than the comments in their sources. I downloaded and extracted src.tar.gz and sys.tar.gz from a mirror of OpenBSD. Suppose the extracted trees are in /home/user/src and /home/user/sys/sys (extracting src.tar.gz, it doesn't create another src directory; extracting sys.tar.gz it creates another sys directory). The c-source that contains the definitions of keyboard variables managed by wsconsctl is /home/user/src/sbin/wsconsctl/keyboard.c keyboard.c defines a table of all these varables: Code:
struct field keyboard_field_tab[] = { { "type", &kbtype, FMT_KBDTYPE, FLG_RDONLY }, { "bell.pitch", &bell.pitch, FMT_UINT, FLG_MODIFY }, { "bell.period", &bell.period, FMT_UINT, FLG_MODIFY }, { "bell.volume", &bell.volume, FMT_UINT, FLG_MODIFY }, { "bell.pitch.default", &dfbell.pitch, FMT_UINT, FLG_MODIFY }, { "bell.period.default", &dfbell.period, FMT_UINT, FLG_MODIFY }, { "bell.volume.default", &dfbell.volume, FMT_UINT, FLG_MODIFY }, { "map", &kbmap, FMT_KBMAP, FLG_MODIFY|FLG_N OAUTO }, { "repeat.del1", &repeat.del1, FMT_UINT, FLG_MODIFY }, { "repeat.deln", &repeat.delN, FMT_UINT, FLG_MODIFY }, { "repeat.del1.default", &dfrepeat.del1, FMT_UINT, FLG_MODIFY }, { "repeat.deln.default", &dfrepeat.delN, FMT_UINT, FLG_MODIFY }, { "ledstate", &ledstate, FMT_UINT, 0 }, { "encoding", &kbdencoding, FMT_KBDENC, FLG_MODIFY }, { "backlight", &backlight, FMT_PC, FLG_MODIFY|FLG_I NIT }, { NULL } }; These variables are declared in keyboard.c as structures of type wskbd_keyrepeat_data: Code:
static struct wskbd_keyrepeat_data repeat; static struct wskbd_keyrepeat_data dfrepeat; Code:
#include <dev/wscons/wsksymdef.h> #include <dev/wscons/wsconsio.h> #include "wsconsctl.h" /home/user/sys/sys/dev/wscons/wsconsio.h /home/user/sys/sys/dev/wscons/wskbd.c I opened wsconsio.h and I found Code:
/* Manipulate the emulation key repeat settings. */ struct wskbd_keyrepeat_data { u_int which; /* values to get/set */ u_int del1; /* delay before first, ms */ u_int delN; /* delay before rest, ms */ }; I don't understand completely the meaning of the "default" version of the same variables. Also /home/user/sys/sys/dev/wscons/wskbd.c is interesting. It seems to me that it is possible to investigate about every variable and extract information about them. If you want, we can join our efforts and create a file with the information we find. It's not easy, but it's been very instructive and funny to me. Ciao!! |
|
|||
I forgot gustaf. Hi gustaf!
|
|
|||
Thanks to you.
Your question brought me to download the sources. I never did it before. And so I discovered also the answer to another question I posted some days ago on "openBSD general", about libc: using only man pages I wasn't able to see libc's structure (the list of functions declared in a header, for example string.h). With the sources tree one can see everything and, for specific information, can look at man pages. So your question made me understand something more. Have a nice day. Ciao. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
wsconsctl elusive keycodes | radix | OpenBSD General | 15 | 8th March 2015 08:17 PM |
FreeBSD jail inherited user accounts and env variables | sysfu | FreeBSD General | 0 | 3rd November 2013 05:01 PM |
IPFW and sysctl variables questions | unixjingleman | FreeBSD Security | 1 | 12th June 2011 03:33 AM |
Dereferencing sh variables | J65nko | Programming | 3 | 29th January 2010 02:34 AM |
passing make args/variables to builds of prerequisite ports | jbhappy | FreeBSD Ports and Packages | 2 | 18th July 2008 02:35 PM |