* feat(control char): add basic control char support
* feat(control char): fix wrong x when \n after \b
* feat(control char): add `\t` support, same behavior as `\t` in c printf
* Gonna go with 4 spaces per tab to be safer
* fix(control chars): leading control chars run into 'out of bounds memory acessing', and render at wrong position
* doc(control chars): describe the control chars behavior and declare the influenced options and bump date to SEP 2021.
* update to NOV
* Bump years
* Redo manpage
Co-authored-by: Raymond Li <hi@raymond.li>
* Add adjustable total bar width and bar position
* Update parameter name and documentation
* Fix option name in error message
* Reword error message
Co-authored-by: Raymond Li <hi@raymond.li>
This adds some feedback to a keypress which previously had no visible effect.
While the text “no input” isn’t the most descriptive, it was the only one I
could think of which fit into the unlock indicator circle. If you have a better
suggestion, let me know.
fixes#164
theoretical potential security concerns; no use unless using bar and you care... I hammered pretty hard on my kb for a while to try and see if it's possible to configure it poorly and get the render thread to crash, but to no avail.
Display "locking…" message when grabbing the pointer/keyboard,
after at least 250 ms of unfruitful attempts. If grabbing
eventually fails, application will not fork and return 1.
See also:
http://article.gmane.org/gmane.linux.kernel/1268792
The C compiler will handle (void) as "no arguments" and () as "variadic
function" (equivalent to (...)) which might lead to subtle errors, such
as the one which was fixed with commit 0ea64ae4.
SuperDJY