plugins: Add colored-man-pages plugin

[RobLoach]

Inspired by the colored-man-pages zsh plugin.

This is likely not the best design, as I'm grabbing the specific colors. If there's a better method, feel free to let me know.

[akinomyoga]

This plugin affects the global behavior of less instead of just affecting man.

I thought we might need to accept it if the upstream OMZ plugin of the same name were behaving in the same way. However, I checked the upstream plugin and realized that the upstream version correctly implements it using a shell function with the local environment variable so that it only affects man.

Could you adjust it so that it doesn't affect the global behavior of less?

[akinomyoga]

Could you adjust it so that it doesn't affect the global behavior of less?

The upstream seems to be using env, but what I'm thinking is something like this:

function _omb_plugin_colored_man_pages_colored {
  local -x LESS_TERMCAP_mb=...
  ...

  command "$@"
}

_omb_util_binary_exists man &&
  function man { _omb_plugin_colored_man_pages_colored "$FUNCNAME" "$@"; }
_omb_util_binary_exists debman &&
  function debman { _omb_plugin_colored_man_pages_colored "$FUNCNAME" "$@"; }
...

[akinomyoga]

Thanks for updates!

I have a question. This plugin and also the upstream one define the function colored, but is this something that this plugin intentionally exposes to the user? Is the function colored intended to be also directly used by users? It doesn't seem to be the case to me. If so, can we rename the function as _omb_plugin_colored_man_pages_colored? We try to avoid polluting the namespace of the commands that the users directly type and run. What do you think?

Ah, OK. Please disregard this. I noticed the usage of colored in README.md. Thank you!

[akinomyoga]

@RobLoach Thanks!