When ACPI returns multiple batteries, and not all of them related to laptop
battery, this option can be used to specify which battery to be used for
status information. Example of this is Logitech Unifying Receiver, returning
battery information for keyboard/mouse.

Also remove some trailing space.

Closes: nojhan/liquidprompt#675

LP_KUBECONTEXT_DELIMITER_SUFFIX removes a suffix (dev-cluster and - becomes ->
dev). But sometimes the boilerplate part is a prefix, as when using AWS
EKS (Elastic Kubernetes Service).

`aws eks update-kubeconfig --name $CLUSTER_NAME` sets the cluster's ARN
as the context name, most of which is boilerplate:
`arn:aws:eks:$REGION:$ACCOUNT_ID:cluster/$CLUSTER_NAME`.

Fixes https://github.com/nojhan/liquidprompt/issues/600.

Fixes: https://github.com/nojhan/liquidprompt/issues/249

This will add `[profile_name]` to the prompt should it find either
`AWS_PROFILE` or `AWS_DEFAULT_PROFILE` set in the environment.

This is useful when switching between different AWS profiles and
working with multiple accounts.

Add a data source to get the current Kubernetes context. Includes a
mechanism for truncating the context to the first matching character,
configurable.

The data source is disabled by default. The truncation is also disabled
by default (disabled by setting the config option to the empty string).

Add a default theme function to format the context like the other
development environments.

I use a file sync to keep my `.liquidpromptrc` the same on all my hosts, but on a couple of the individual machines I want to change/add config, so I added this.

The load average display has been notoriously not helpful. It is scaled
by the CPU count, and then multiplied by 100 to make it apear like a
percentage. But load average and CPU utilization have almost nothing to
do with each other.

This change displays the actual load average, while keeping the
threshold and color calculations the same. This means the functionality
is no different, just that the display has changed formats.

To make the configuration options LP_LOAD_THRESHOLD less confusing, it
too has been changed to be an actual load value, no longer "centiload".
Old values are still supported, which is done by checking for a period
('.') in the string. So for this historical reason, all new values must
have a period in them. Which should not be a problem, any useful value
would be a float.

Change the greater-than comparison to a greater-than-or-equal-to, since
it is a little more intuitive to what would be expected from the config
option.

Since I was at it, I added a new config option LP_LOAD_CAP, to configure
the range for color values output by _lp_color_map() for load averages.
It too takes a load average float value. As it does not have the
historical reason above, it does not accept "centiload" values.

The implementation details are long. Floating point math does not exist
in shells (which I suspect is the reason that "centiload" was used in
the first place). To make it possible to compare, the values are scaled
up by 100 just like before. They are not shown to the user. 100 scaling
should be plenty for the precision we need.

To do the scaling, __lp_floating_scale() is added, which as a standalone
function, can be unit tested.

And for good measure, the lp_load return value is passed through
__lp_escape(), just in case.

Special thanks to Tore Anderson (@toreanderson) for helping dig through
the issues here.

I had been documenting the new functions I was adding directly in the
liquidprompt source file, but when I added the Sphinx documentation, it
ended up duplicated. Rather than try to keep the documentation in sync,
I am removing it from the source file, since the Sphinx documentation is
much higher quality.

Someday maybe I will try to build a Sphinx plugin that can read
documentation from shell files, but that sounds like a huge pain. And
the liquidprompt file is already large enough without detailed
documentation in it.

Add _lp_error() to get the last error, and to return a error code if
there is one. This is more to be in line with the other data functions.

Change lp_err to lp_error, to match the function name.

Make the return codes to have a distinct code for when the username is
disabled (LP_USER_ALWAYS=-1) vs just not shown (logged in user).

Add valid value for LP_USER_ALWAYS: -1, which disables username display.

This prompted a hack in the Powerline theme to get the possibility of no
username to work, so I need to make a more elegant seperator solution.

Add a separate config option for _lp_detached_sessions(), which lets a
user use it and not _lp_jobcount(), or vice versa.

The default theme has historically lumped them together, but that
doesn't mean any other theme has to, nor that they should be configured
together.

Having a config var that stores paths as one string separated by a
specific char is a error waiting to happen. It's much safer (and easier
to read) to use a true array. This would be a breaking change, so
deprecate LP_DISABLED_VCS_PATH, and add LP_DISABLED_VCS_PATHS array. Add
a conversion function in the config file loading section.

An example config change would be:
    LP_DISABLED_VCS_PATH="/my/one/path:/my/other/path"
to
    LP_DISABLED_VCS_PATHS=("/my/one/path" "/my/other/path")

`LP_LOAD_THRESHOLD` is configured using a rather eccentric "centiload per CPU"
value, not the actual load average value reported by `/proc/loadavg` and
`uptime`. This is likely not what a user would intuitively expect, so document
it better.

Signed-off-by: Tore Anderson <tore@fud.no>

Disabled by default, if enabled the prompt will ring the terminal bell
after any command takes longer than LP_RUNTIME_BELL_THRESHOLD to
execute.

This is handy when you have a long running process on a different
virtual desktop and want to be notified when it completes.

Print the bell character to stderr. This means it won't be captured in
LP_RUNTIME, and thus won't end up in PS1.  This matters in the case
where a RUNTIME prompt is displayed because the last command on a given
shell was slow.  If the bell character is captured in PS1, it will ring
every time the terminal is resized, since bash reprints PS1 in response
to SIGWINCH, which spuriously rings the bell again.

Now your lambda or arrow can take over the role of the colon.

* Tried to use a more consistent and declarative voice throughout the
entire file.
* Moved an entry or two around to be closer to related features.
* Expanded the explanation of a few of the features.
* Made sure all comment lines fit in 80 characters (for no good reason)

To stay friend with sysadmins. Closes #345.
https://github.com/nojhan/liquidprompt/issues/345

Change the color of the prompt mark while 'sudo' credentials are cached.

New variables:
- LP_ENABLE_SUDO
- LP_COLOR_MARK_SUDO

https://github.com/nojhan/liquidprompt/issues/335

- Various grammatical changes and rephrasings
- Capitalize names of VCSes and "Bash"
- Standardize references to project name ("Liquid Prompt")
- Use title casing in README section headers
- Use multiple list-levels in README where appropriate
- Fix code block in pull request instructions in CONTRIBUTING

Thanks to @pkkolos for catching them in
https://github.com/pkkolos/liquidprompt/commit/1eb35f46b0918974cebe351ca8441e4659b869a5

Now the prompt mark can be at the beginning
of a new line without a space before it.

Conflicts:
	liquidprompt

Fedora, RHEL, and CentOS provide support for multiple versions of
the same software components using Software Collections.  This
patch lists the active collections in a similar manner to Python
virtualenvs.

Using `LP_TIME_ANALOG`, you can now display an analog clock instead of
numeric values. The analog clock is "accurate" to the nearest half hour.

Do you want to display the percentages of load/batteries along with their
corresponding marks? Set to 0 to only print the colored marks.
Defaults to 1 (display percentages)

Adds the LP_ENABLE_SSH_COLORS option to use a numeric hash of the hostname as the displayed color.