1645288080
keyboard
Take full control of your keyboard with this small Python library. Hook global events, register hotkeys, simulate key presses and much more.
ctrl+shift+m, ctrl+space
) with controllable timeout.Ctrl+ç
).pip install mouse
).Install the PyPI package:
pip install keyboard
or clone the repository (no installation required, source files are sufficient):
git clone https://github.com/boppreh/keyboard
or download and extract the zip into your project folder.
Then check the API docs below to see what features are available.
Use as library:
import keyboard
keyboard.press_and_release('shift+s, space')
keyboard.write('The quick brown fox jumps over the lazy dog.')
keyboard.add_hotkey('ctrl+shift+a', print, args=('triggered', 'hotkey'))
# Press PAGE UP then PAGE DOWN to type "foobar".
keyboard.add_hotkey('page up, page down', lambda: keyboard.write('foobar'))
# Blocks until you press esc.
keyboard.wait('esc')
# Record events until 'esc' is pressed.
recorded = keyboard.record(until='esc')
# Then replay back at three times the speed.
keyboard.play(recorded, speed_factor=3)
# Type @@ then press space to replace with abbreviation.
keyboard.add_abbreviation('@@', 'my.long.email@example.com')
# Block forever, like `while True`.
keyboard.wait()
Use as standalone module:
# Save JSON events to a file until interrupted:
python -m keyboard > events.txt
cat events.txt
# {"event_type": "down", "scan_code": 25, "name": "p", "time": 1622447562.2994788, "is_keypad": false}
# {"event_type": "up", "scan_code": 25, "name": "p", "time": 1622447562.431007, "is_keypad": false}
# ...
# Replay events
python -m keyboard < events.txt
event.device == None
). #21/dev/input/input*
) but this requires root.keyboard
will be unable to report events.keyboard
via SSH, the server will not detect your key events.import keyboard
keyboard.add_hotkey('space', lambda: print('space was pressed!'))
# If the program finishes, the hotkey is not in effect anymore.
# Don't do this! This will use 100% of your CPU.
#while True: pass
# Use this instead
keyboard.wait()
# or this
import time
while True:
time.sleep(1000000)
import keyboard
# Don't do this! This will use 100% of your CPU until you press the key.
#
#while not keyboard.is_pressed('space'):
# continue
#print('space was pressed, continuing...')
# Do this instead
keyboard.wait('space')
print('space was pressed, continuing...')
import keyboard
# Don't do this!
#
#while True:
# if keyboard.is_pressed('space'):
# print('space was pressed!')
#
# This will use 100% of your CPU and print the message many times.
# Do this instead
while True:
keyboard.wait('space')
print('space was pressed! Waiting on it again...')
# or this
keyboard.add_hotkey('space', lambda: print('space was pressed!'))
keyboard.wait()
import keyboard
# Don't do this! This will call `print('space')` immediately then fail when the key is actually pressed.
#keyboard.add_hotkey('space', print('space was pressed'))
# Do this instead
keyboard.add_hotkey('space', lambda: print('space was pressed'))
# or this
def on_space():
print('space was pressed')
keyboard.add_hotkey('space', on_space)
# or this
while True:
# Wait for the next event.
event = keyboard.read_event()
if event.event_type == keyboard.KEY_DOWN and event.name == 'space':
print('space was pressed')
# Don't do this! The `keyboard` module is meant for global events, even when your program is not in focus.
#import keyboard
#print('Press any key to continue...')
#keyboard.get_event()
# Do this instead
input('Press enter to continue...')
# Or one of the suggestions from here
# https://stackoverflow.com/questions/983354/how-to-make-a-script-wait-for-a-pressed-key
API
press_and_release
)unblock_key
, unhook_key
, unremap_key
)register_hotkey
)clear_hotkey
, unregister_hotkey
, unremap_hotkey
)clear_all_hotkeys
, remove_all_hotkeys
, unregister_all_hotkeys
)replay
)register_word_listener
)remove_abbreviation
)register_abbreviation
)= 'down'
= 'up'
= {'alt', 'alt gr', 'ctrl', 'left alt', 'left ctrl', 'left shift', 'left windows', 'right alt', 'right ctrl', 'right shift', 'right windows', 'shift', 'windows'}
= {'alt', 'ctrl', 'shift', 'windows'}
= '0.13.5'
Returns True if key
is a scan code or name of a modifier key.
Returns a list of scan codes associated with this key (name or scan code).
Parses a user-provided hotkey into nested tuples representing the parsed structure, with the bottom values being lists of scan codes. Also accepts raw scan codes, which are then wrapped in the required number of nestings.
Example:
parse_hotkey("alt+shift+a, alt+b, c")
# Keys: ^~^ ^~~~^ ^ ^~^ ^ ^
# Steps: ^~~~~~~~~~^ ^~~~^ ^
# ((alt_codes, shift_codes, a_codes), (alt_codes, b_codes), (c_codes,))
Sends OS events that perform the given hotkey hotkey.
hotkey
can be either a scan code (e.g. 57 for space), single key (e.g. 'space') or multi-key, multi-step hotkey (e.g. 'alt+F4, enter').do_press
if true then press events are sent. Defaults to True.do_release
if true then release events are sent. Defaults to True.
send(57)
send('ctrl+alt+del')
send('alt+F4, enter')
send('shift+s')
Note: keys are released in the opposite order they were pressed.
Presses and holds down a hotkey (see send
).
Releases a hotkey (see send
).
Returns True if the key is pressed.
is_pressed(57) #-> True
is_pressed('space') #-> True
is_pressed('ctrl+space') #-> True
Calls the provided function in a new thread after waiting some time. Useful for giving the system some time to process an event, without blocking the current execution flow.
Installs a global listener on all available keyboards, invoking callback
each time a key is pressed or released.
The event passed to the callback is of type keyboard.KeyboardEvent
, with the following attributes:
name
: an Unicode representation of the character (e.g. "&") or description (e.g. "space"). The name is always lower-case.scan_code
: number representing the physical key, e.g. 55.time
: timestamp of the time the event occurred, with as much precision as given by the OS.Returns the given callback for easier development.
Invokes callback
for every KEY_DOWN event. For details see hook
.
Invokes callback
for every KEY_UP event. For details see hook
.
Hooks key up and key down events for a single key. Returns the event handler created. To remove a hooked key use unhook_key(key)
or unhook_key(handler)
.
Note: this function shares state with hotkeys, so clear_all_hotkeys
affects it as well.
Invokes callback
for KEY_DOWN event related to the given key. For details see hook
.
Invokes callback
for KEY_UP event related to the given key. For details see hook
.
Removes a previously added hook, either by callback or by the return value of hook
.
Removes all keyboard hooks in use, including hotkeys, abbreviations, word listeners, record
ers and wait
s.
Suppresses all key events of the given key, regardless of modifiers.
Whenever the key src
is pressed or released, regardless of modifiers, press or release the hotkey dst
instead.
Parses a user-provided hotkey. Differently from parse_hotkey
, instead of each step being a list of the different scan codes for each key, each step is a list of all possible combinations of those scan codes.
Invokes a callback every time a hotkey is pressed. The hotkey must be in the format ctrl+shift+a, s
. This would trigger when the user holds ctrl, shift and "a" at once, releases, and then presses "s". To represent literal commas, pluses, and spaces, use their names ('comma', 'plus', 'space').
args
is an optional list of arguments to passed to the callback during each invocation.suppress
defines if successful triggers should block the keys from being sent to other programs.timeout
is the amount of seconds allowed to pass between key presses.trigger_on_release
if true, the callback is invoked on key release instead of key press.The event handler function is returned. To remove a hotkey call remove_hotkey(hotkey)
or remove_hotkey(handler)
. before the hotkey state is reset.
Note: hotkeys are activated when the last key is pressed, not released. Note: the callback is executed in a separate thread, asynchronously. For an example of how to use a callback synchronously, see wait
.
Examples:
# Different but equivalent ways to listen for a spacebar key press.
add_hotkey(' ', print, args=['space was pressed'])
add_hotkey('space', print, args=['space was pressed'])
add_hotkey('Space', print, args=['space was pressed'])
# Here 57 represents the keyboard code for spacebar; so you will be
# pressing 'spacebar', not '57' to activate the print function.
add_hotkey(57, print, args=['space was pressed'])
add_hotkey('ctrl+q', quit)
add_hotkey('ctrl+alt+enter, space', some_callback)
Removes a previously hooked hotkey. Must be called with the value returned by add_hotkey
.
Removes all keyboard hotkeys in use, including abbreviations, word listeners, record
ers and wait
s.
Whenever the hotkey src
is pressed, suppress it and send dst
instead.
Example:
remap('alt+w', 'ctrl+up')
Builds a list of all currently pressed scan codes, releases them and returns the list. Pairs well with restore_state
and restore_modifiers
.
Given a list of scan_codes ensures these keys, and only these keys, are pressed. Pairs well with stash_state
, alternative to restore_modifiers
.
Like restore_state
, but only restores modifier keys.
Sends artificial keyboard events to the OS, simulating the typing of a given text. Characters not available on the keyboard are typed as explicit unicode characters using OS-specific functionality, such as alt+codepoint.
To ensure text integrity, all currently pressed keys are released before the text is typed, and modifiers are restored afterwards.
delay
is the number of seconds to wait between keypresses, defaults to no delay.restore_state_after
can be used to restore the state of pressed keys after the text is typed, i.e. presses the keys that were released at the beginning. Defaults to True.exact
forces typing all characters as explicit unicode (e.g. alt+codepoint or special events). If None, uses platform-specific suggested value.Blocks the program execution until the given hotkey is pressed or, if given no parameters, blocks forever.
Returns a string representation of hotkey from the given key names, or the currently pressed keys if not given. This function:
Example:
get_hotkey_name(['+', 'left ctrl', 'shift'])
# "ctrl+shift+plus"
Blocks until a keyboard event happens, then returns that event.
Blocks until a keyboard event happens, then returns that event's name or, if missing, its scan code.
Similar to read_key()
, but blocks until the user presses and releases a hotkey (or single key), then returns a string representing the hotkey pressed.
Example:
read_hotkey()
# "ctrl+shift+p"
Given a sequence of events, tries to deduce what strings were typed. Strings are separated when a non-textual key is pressed (such as tab or enter). Characters are converted to uppercase according to shift and capslock status. If allow_backspace
is True, backspaces remove the last character typed.
This function is a generator, so you can pass an infinite stream of events and convert them to strings in real time.
Note this functions is merely an heuristic. Windows for example keeps per- process keyboard state such as keyboard layout, and this information is not available for our hooks.
get_type_strings(record()) #-> ['This is what', 'I recorded', '']
Starts recording all keyboard events into a global variable, or the given queue if any. Returns the queue of events and the hooked function.
Use stop_recording()
or unhook(hooked_function)
to stop.
Stops the global recording of events and returns a list of the events captured.
Records all keyboard events from all keyboards until the user presses the given hotkey. Then returns the list of events recorded, of type keyboard.KeyboardEvent
. Pairs well with play(events)
.
Note: this is a blocking function. Note: for more details on the keyboard hook and events see hook
.
Plays a sequence of recorded events, maintaining the relative time intervals. If speed_factor is <= 0 then the actions are replayed as fast as the OS allows. Pairs well with record()
.
Note: the current keyboard state is cleared at the beginning and restored at the end of the function.
Invokes a callback every time a sequence of characters is typed (e.g. 'pet') and followed by a trigger key (e.g. space). Modifiers (e.g. alt, ctrl, shift) are ignored.
word
the typed text to be matched. E.g. 'pet'.callback
is an argument-less function to be invoked each time the word is typed.triggers
is the list of keys that will cause a match to be checked. If the user presses some key that is not a character (len>1) and not in triggers, the characters so far will be discarded. By default the trigger is only space
.match_suffix
defines if endings of words should also be checked instead of only whole words. E.g. if true, typing 'carpet'+space will trigger the listener for 'pet'. Defaults to false, only whole words are checked.timeout
is the maximum number of seconds between typed characters before the current word is discarded. Defaults to 2 seconds.Returns the event handler created. To remove a word listener use remove_word_listener(word)
or remove_word_listener(handler)
.
Note: all actions are performed on key down. Key up events are ignored. Note: word matches are case sensitive.
Removes a previously registered word listener. Accepts either the word used during registration (exact string) or the event handler returned by the add_word_listener
or add_abbreviation
functions.
Registers a hotkey that replaces one typed text with another. For example
add_abbreviation('tm', u'™')
Replaces every "tm" followed by a space with a ™ symbol (and no space). The replacement is done by sending backspace events.
match_suffix
defines if endings of words should also be checked instead of only whole words. E.g. if true, typing 'carpet'+space will trigger the listener for 'pet'. Defaults to false, only whole words are checked.timeout
is the maximum number of seconds between typed characters before the current word is discarded. Defaults to 2 seconds.For more details see add_word_listener
.
Given a key name (e.g. "LEFT CONTROL"), clean up the string and convert to the canonical representation (e.g. "left ctrl") if one is known.
Author: Boppreh
Source Code: https://github.com/boppreh/keyboard
License: MIT License
1645288080
keyboard
Take full control of your keyboard with this small Python library. Hook global events, register hotkeys, simulate key presses and much more.
ctrl+shift+m, ctrl+space
) with controllable timeout.Ctrl+ç
).pip install mouse
).Install the PyPI package:
pip install keyboard
or clone the repository (no installation required, source files are sufficient):
git clone https://github.com/boppreh/keyboard
or download and extract the zip into your project folder.
Then check the API docs below to see what features are available.
Use as library:
import keyboard
keyboard.press_and_release('shift+s, space')
keyboard.write('The quick brown fox jumps over the lazy dog.')
keyboard.add_hotkey('ctrl+shift+a', print, args=('triggered', 'hotkey'))
# Press PAGE UP then PAGE DOWN to type "foobar".
keyboard.add_hotkey('page up, page down', lambda: keyboard.write('foobar'))
# Blocks until you press esc.
keyboard.wait('esc')
# Record events until 'esc' is pressed.
recorded = keyboard.record(until='esc')
# Then replay back at three times the speed.
keyboard.play(recorded, speed_factor=3)
# Type @@ then press space to replace with abbreviation.
keyboard.add_abbreviation('@@', 'my.long.email@example.com')
# Block forever, like `while True`.
keyboard.wait()
Use as standalone module:
# Save JSON events to a file until interrupted:
python -m keyboard > events.txt
cat events.txt
# {"event_type": "down", "scan_code": 25, "name": "p", "time": 1622447562.2994788, "is_keypad": false}
# {"event_type": "up", "scan_code": 25, "name": "p", "time": 1622447562.431007, "is_keypad": false}
# ...
# Replay events
python -m keyboard < events.txt
event.device == None
). #21/dev/input/input*
) but this requires root.keyboard
will be unable to report events.keyboard
via SSH, the server will not detect your key events.import keyboard
keyboard.add_hotkey('space', lambda: print('space was pressed!'))
# If the program finishes, the hotkey is not in effect anymore.
# Don't do this! This will use 100% of your CPU.
#while True: pass
# Use this instead
keyboard.wait()
# or this
import time
while True:
time.sleep(1000000)
import keyboard
# Don't do this! This will use 100% of your CPU until you press the key.
#
#while not keyboard.is_pressed('space'):
# continue
#print('space was pressed, continuing...')
# Do this instead
keyboard.wait('space')
print('space was pressed, continuing...')
import keyboard
# Don't do this!
#
#while True:
# if keyboard.is_pressed('space'):
# print('space was pressed!')
#
# This will use 100% of your CPU and print the message many times.
# Do this instead
while True:
keyboard.wait('space')
print('space was pressed! Waiting on it again...')
# or this
keyboard.add_hotkey('space', lambda: print('space was pressed!'))
keyboard.wait()
import keyboard
# Don't do this! This will call `print('space')` immediately then fail when the key is actually pressed.
#keyboard.add_hotkey('space', print('space was pressed'))
# Do this instead
keyboard.add_hotkey('space', lambda: print('space was pressed'))
# or this
def on_space():
print('space was pressed')
keyboard.add_hotkey('space', on_space)
# or this
while True:
# Wait for the next event.
event = keyboard.read_event()
if event.event_type == keyboard.KEY_DOWN and event.name == 'space':
print('space was pressed')
# Don't do this! The `keyboard` module is meant for global events, even when your program is not in focus.
#import keyboard
#print('Press any key to continue...')
#keyboard.get_event()
# Do this instead
input('Press enter to continue...')
# Or one of the suggestions from here
# https://stackoverflow.com/questions/983354/how-to-make-a-script-wait-for-a-pressed-key
API
press_and_release
)unblock_key
, unhook_key
, unremap_key
)register_hotkey
)clear_hotkey
, unregister_hotkey
, unremap_hotkey
)clear_all_hotkeys
, remove_all_hotkeys
, unregister_all_hotkeys
)replay
)register_word_listener
)remove_abbreviation
)register_abbreviation
)= 'down'
= 'up'
= {'alt', 'alt gr', 'ctrl', 'left alt', 'left ctrl', 'left shift', 'left windows', 'right alt', 'right ctrl', 'right shift', 'right windows', 'shift', 'windows'}
= {'alt', 'ctrl', 'shift', 'windows'}
= '0.13.5'
Returns True if key
is a scan code or name of a modifier key.
Returns a list of scan codes associated with this key (name or scan code).
Parses a user-provided hotkey into nested tuples representing the parsed structure, with the bottom values being lists of scan codes. Also accepts raw scan codes, which are then wrapped in the required number of nestings.
Example:
parse_hotkey("alt+shift+a, alt+b, c")
# Keys: ^~^ ^~~~^ ^ ^~^ ^ ^
# Steps: ^~~~~~~~~~^ ^~~~^ ^
# ((alt_codes, shift_codes, a_codes), (alt_codes, b_codes), (c_codes,))
Sends OS events that perform the given hotkey hotkey.
hotkey
can be either a scan code (e.g. 57 for space), single key (e.g. 'space') or multi-key, multi-step hotkey (e.g. 'alt+F4, enter').do_press
if true then press events are sent. Defaults to True.do_release
if true then release events are sent. Defaults to True.
send(57)
send('ctrl+alt+del')
send('alt+F4, enter')
send('shift+s')
Note: keys are released in the opposite order they were pressed.
Presses and holds down a hotkey (see send
).
Releases a hotkey (see send
).
Returns True if the key is pressed.
is_pressed(57) #-> True
is_pressed('space') #-> True
is_pressed('ctrl+space') #-> True
Calls the provided function in a new thread after waiting some time. Useful for giving the system some time to process an event, without blocking the current execution flow.
Installs a global listener on all available keyboards, invoking callback
each time a key is pressed or released.
The event passed to the callback is of type keyboard.KeyboardEvent
, with the following attributes:
name
: an Unicode representation of the character (e.g. "&") or description (e.g. "space"). The name is always lower-case.scan_code
: number representing the physical key, e.g. 55.time
: timestamp of the time the event occurred, with as much precision as given by the OS.Returns the given callback for easier development.
Invokes callback
for every KEY_DOWN event. For details see hook
.
Invokes callback
for every KEY_UP event. For details see hook
.
Hooks key up and key down events for a single key. Returns the event handler created. To remove a hooked key use unhook_key(key)
or unhook_key(handler)
.
Note: this function shares state with hotkeys, so clear_all_hotkeys
affects it as well.
Invokes callback
for KEY_DOWN event related to the given key. For details see hook
.
Invokes callback
for KEY_UP event related to the given key. For details see hook
.
Removes a previously added hook, either by callback or by the return value of hook
.
Removes all keyboard hooks in use, including hotkeys, abbreviations, word listeners, record
ers and wait
s.
Suppresses all key events of the given key, regardless of modifiers.
Whenever the key src
is pressed or released, regardless of modifiers, press or release the hotkey dst
instead.
Parses a user-provided hotkey. Differently from parse_hotkey
, instead of each step being a list of the different scan codes for each key, each step is a list of all possible combinations of those scan codes.
Invokes a callback every time a hotkey is pressed. The hotkey must be in the format ctrl+shift+a, s
. This would trigger when the user holds ctrl, shift and "a" at once, releases, and then presses "s". To represent literal commas, pluses, and spaces, use their names ('comma', 'plus', 'space').
args
is an optional list of arguments to passed to the callback during each invocation.suppress
defines if successful triggers should block the keys from being sent to other programs.timeout
is the amount of seconds allowed to pass between key presses.trigger_on_release
if true, the callback is invoked on key release instead of key press.The event handler function is returned. To remove a hotkey call remove_hotkey(hotkey)
or remove_hotkey(handler)
. before the hotkey state is reset.
Note: hotkeys are activated when the last key is pressed, not released. Note: the callback is executed in a separate thread, asynchronously. For an example of how to use a callback synchronously, see wait
.
Examples:
# Different but equivalent ways to listen for a spacebar key press.
add_hotkey(' ', print, args=['space was pressed'])
add_hotkey('space', print, args=['space was pressed'])
add_hotkey('Space', print, args=['space was pressed'])
# Here 57 represents the keyboard code for spacebar; so you will be
# pressing 'spacebar', not '57' to activate the print function.
add_hotkey(57, print, args=['space was pressed'])
add_hotkey('ctrl+q', quit)
add_hotkey('ctrl+alt+enter, space', some_callback)
Removes a previously hooked hotkey. Must be called with the value returned by add_hotkey
.
Removes all keyboard hotkeys in use, including abbreviations, word listeners, record
ers and wait
s.
Whenever the hotkey src
is pressed, suppress it and send dst
instead.
Example:
remap('alt+w', 'ctrl+up')
Builds a list of all currently pressed scan codes, releases them and returns the list. Pairs well with restore_state
and restore_modifiers
.
Given a list of scan_codes ensures these keys, and only these keys, are pressed. Pairs well with stash_state
, alternative to restore_modifiers
.
Like restore_state
, but only restores modifier keys.
Sends artificial keyboard events to the OS, simulating the typing of a given text. Characters not available on the keyboard are typed as explicit unicode characters using OS-specific functionality, such as alt+codepoint.
To ensure text integrity, all currently pressed keys are released before the text is typed, and modifiers are restored afterwards.
delay
is the number of seconds to wait between keypresses, defaults to no delay.restore_state_after
can be used to restore the state of pressed keys after the text is typed, i.e. presses the keys that were released at the beginning. Defaults to True.exact
forces typing all characters as explicit unicode (e.g. alt+codepoint or special events). If None, uses platform-specific suggested value.Blocks the program execution until the given hotkey is pressed or, if given no parameters, blocks forever.
Returns a string representation of hotkey from the given key names, or the currently pressed keys if not given. This function:
Example:
get_hotkey_name(['+', 'left ctrl', 'shift'])
# "ctrl+shift+plus"
Blocks until a keyboard event happens, then returns that event.
Blocks until a keyboard event happens, then returns that event's name or, if missing, its scan code.
Similar to read_key()
, but blocks until the user presses and releases a hotkey (or single key), then returns a string representing the hotkey pressed.
Example:
read_hotkey()
# "ctrl+shift+p"
Given a sequence of events, tries to deduce what strings were typed. Strings are separated when a non-textual key is pressed (such as tab or enter). Characters are converted to uppercase according to shift and capslock status. If allow_backspace
is True, backspaces remove the last character typed.
This function is a generator, so you can pass an infinite stream of events and convert them to strings in real time.
Note this functions is merely an heuristic. Windows for example keeps per- process keyboard state such as keyboard layout, and this information is not available for our hooks.
get_type_strings(record()) #-> ['This is what', 'I recorded', '']
Starts recording all keyboard events into a global variable, or the given queue if any. Returns the queue of events and the hooked function.
Use stop_recording()
or unhook(hooked_function)
to stop.
Stops the global recording of events and returns a list of the events captured.
Records all keyboard events from all keyboards until the user presses the given hotkey. Then returns the list of events recorded, of type keyboard.KeyboardEvent
. Pairs well with play(events)
.
Note: this is a blocking function. Note: for more details on the keyboard hook and events see hook
.
Plays a sequence of recorded events, maintaining the relative time intervals. If speed_factor is <= 0 then the actions are replayed as fast as the OS allows. Pairs well with record()
.
Note: the current keyboard state is cleared at the beginning and restored at the end of the function.
Invokes a callback every time a sequence of characters is typed (e.g. 'pet') and followed by a trigger key (e.g. space). Modifiers (e.g. alt, ctrl, shift) are ignored.
word
the typed text to be matched. E.g. 'pet'.callback
is an argument-less function to be invoked each time the word is typed.triggers
is the list of keys that will cause a match to be checked. If the user presses some key that is not a character (len>1) and not in triggers, the characters so far will be discarded. By default the trigger is only space
.match_suffix
defines if endings of words should also be checked instead of only whole words. E.g. if true, typing 'carpet'+space will trigger the listener for 'pet'. Defaults to false, only whole words are checked.timeout
is the maximum number of seconds between typed characters before the current word is discarded. Defaults to 2 seconds.Returns the event handler created. To remove a word listener use remove_word_listener(word)
or remove_word_listener(handler)
.
Note: all actions are performed on key down. Key up events are ignored. Note: word matches are case sensitive.
Removes a previously registered word listener. Accepts either the word used during registration (exact string) or the event handler returned by the add_word_listener
or add_abbreviation
functions.
Registers a hotkey that replaces one typed text with another. For example
add_abbreviation('tm', u'™')
Replaces every "tm" followed by a space with a ™ symbol (and no space). The replacement is done by sending backspace events.
match_suffix
defines if endings of words should also be checked instead of only whole words. E.g. if true, typing 'carpet'+space will trigger the listener for 'pet'. Defaults to false, only whole words are checked.timeout
is the maximum number of seconds between typed characters before the current word is discarded. Defaults to 2 seconds.For more details see add_word_listener
.
Given a key name (e.g. "LEFT CONTROL"), clean up the string and convert to the canonical representation (e.g. "left ctrl") if one is known.
Author: Boppreh
Source Code: https://github.com/boppreh/keyboard
License: MIT License
1603415915
This article is all about my journey on switching from Windows 10 to Linux Mint 20, how I got easily adapted to the Linux environment, and some resources that helped me to set up a perfect Desktop environment.
Ok, now I have decided to switch to Linux but here comes the first question. Which distro will satisfy my needs both in terms of GUI and other aspects? Linux is not something new to me since I have been working with RHEL based distros in my work for the past 4 years with the command-line.
I know RHEL based distros are good for enterprises but not for personalized desktop environments, at least that’s what I am thinking till now. So I started my research to find the distro that should be easy for me to use and at the same time should have good community support if in case I ran into some problem. Among many Linux distros, I drilled down my list to 4 flavors.
Related Article: The Best Linux Distributions for Beginners
Before deciding the Distro it is necessary you formulate the list of tools/programs or packages needed and check if the distro you choose provides all those features.
For me, I use Linux for two main purposes: one is for my professional development work, writing articles, and second for my personal use like Video editing and Movies. Most of the popular software are created to be compatible with Windows, macOS, and Linux like Sublime Text, VSCode, VLC Media Player, Firefox/Chromium browser. Other than these software, cloud-based services make our life easy Like Microsoft Office 365 or G Suite.
#linux distros #linux mint #linux distros #linux mint tips #linux
1594368382
Looking to develop real-time applications?
Hire Dedicated Linux Developer from HourlyDeveloper.io, we have dedicated developers who have vast experience in developing applications for Linux and UNIX operating systems and have in-depth knowledge of their processes, kernel tools, internal architectures, and development packages.
Consult with experts:- https://bit.ly/2ZQ5ySP
#hire linux dedicated developer #linux developer #linux development company #linux development services #linux development #linux developer
1621850716
Live events have been a growing trend in the events industry this past year, offering many businesses a much-needed lifeline. Read on for our simple tips to planning your virtual event
#event coverage services #event photography #event video production #event videography #event coverage services #event photography
1601550900
The Windows Subsystem for Linux lets developers run a GNU/Linux environment — including most command-line tools, utilities, and applications — directly on Windows, unmodified, without the overhead of a traditional virtual machine or dualboot setup.
Using the following link here install the WSL 2 on your Windows 10. The Microsoft tutorial is very simple and clean.
#linux-on-windows #windows-10 #wsl-2 #linux