* init table trait
* add shrink_col_index and max_width method to Table trait
* make unicodes work when shrinking
* improve readability of the table
* replace old table system with new one
* update changelog
* Added signature seperator option plus some refactoring
* Have add_content make newline seperation to headers
* Remove signature separator as a separate argument
* Replace echo with printf
The echo(1) command varies among sh implementations. Some interpret
hyphen command-line options.
It would be unusual, but in theory if $PREFIX began with a hyphen or
two then this usage of echo might cause an error or unknown behaviour
in such implementations.
The printf(1) command is consistent across shell implementations.
* Leave privilege elevation to the user
* Add die function
* Break long line
* Add default.nix for nix support
* Convert to flake
* gitignore before building the source
* Add default.nix and shell.nix for legacy workflows
* Use https://github.com/oxalica/rust-overlay
This one works for development workflow, with a functional rust-analyzer for using with language server support in IDEs.
Also add .vscode/ for pre-configured settings.
* Add documentation
* Restore old TOC and apply TOC patch manually
* Clarify that these two commands are either-or
* Add installing from local checkout (nix-env)
* Add note about version update
* Improve Nix workflow, for zero maintenance
Use https://github.com/nmattia/naersk
This avoids having to set a sha and version in Nix scripts.
* Simplify using crate2nix
Ref: https://www.reddit.com/r/rust/comments/mmbfnj/nixifying_a_rust_project/
* Use rootCrate
* Propagate openssl deps to non-shell build
* Try the oxalica overlay
* Get rid of gitignore crate
cf. https://www.reddit.com/r/rust/comments/mmbfnj/nixifying_a_rust_project/gtsgxal/?context=3
* Configure himalaya crate under defaultCrateOverrides
* Specify openssl in buildInputs
* Make a note about a potential error when using Nix 2.4pre
* Remove PKG_CONFIG_PATH (unnecessary)
* Add cargo-watch
Co-authored-by: Alexander Bantyev <balsoft@balsoft.ru>
Co-authored-by: Alexander Bantyev <balsoft@balsoft.ru>
