Version 1.1.0 release.

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "evsieve"
-version = "1.0.0"
+version = "1.1.0"
 authors = ["Kars Mulder <[email protected]>"]
 edition = "2018"
 keywords = ["evdev"]

README.md

@@ -29,8 +29,8 @@ Compiling this program requires the Rust toolchain and the libevdev library. To
 After you've installed the dependencies, you can obtain a copy of the source code and compile the program using:
 
 ```
-wget https://github.com/KarsMulder/evsieve/archive/v1.0.0.tar.gz -O evsieve.tar.gz
-tar -xzf evsieve.tar.gz && cd evsieve-1.0.0
+wget https://github.com/KarsMulder/evsieve/archive/v1.1.0.tar.gz -O evsieve.tar.gz
+tar -xzf evsieve.tar.gz && cd evsieve-1.1.0
 cargo build --release
 ```
 
@@ -766,7 +766,7 @@ There are some questions left surrounding the design of the `auto` mode, so it i
 The basic syntax for the `--output` argument is:
 
 ```
-    --output [EVENTS...] [create-link=PATH] [repeat[=enable|disable|passive]]
+    --output [EVENTS...] [create-link=PATH] [name=NAME] [repeat[=enable|disable|passive]]
 ```
 
 The `--output` argument creates a virtual event device and sends events to it. If the `--output` argument is specified multiple times, a different virtual device will be created for each argument.
@@ -801,6 +801,16 @@ Evsieve will create the link when it starts, and try to remove the link when it
 
 In case a symlink already exists at the path you provided to `create-link=`, evsieve will overwrite that link. This behaviour has been chosen to not make any scripts involving evsieve mysteriously break after an unexpected power loss.
 
+**Names**
+
+A name for the device can be specified using the `name=` clause, e.g.:
+
+```
+    --output name="My keyboard"
+```
+
+If no name is specified, then `Evsieve Virtual Device` is chosen by default. The device name is usually of little consequence, but some third-party tools may care about it. For example, the `evtest` utility is able to display the device name.
+
 **Repeats**
 
 Some devices, like most keyboards, will send repeat events when a key or button is held down. These are events with type EV_KEY and value 2. Most applications ignore these repeat events and use their own internal logic to detect keys that are held down, but for correctness' sake, evsieve is capable of handling them.