===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
powerline-2.8.1/docs/source/configuration.rst-32- packages (e.g. when installing via Gentoo ebuilds).
powerline-2.8.1/docs/source/configuration.rst:33:#. If variable ``$XDG_CONFIG_DIRS`` is set and non-empty then to any
powerline-2.8.1/docs/source/configuration.rst-34- :file:`{directory}/powerline` where `{directory}` is a directory listed in
powerline-2.8.1/docs/source/configuration.rst:35: a colon-separated ``$XDG_CONFIG_DIRS`` list. Directories are checked in
powerline-2.8.1/docs/source/configuration.rst-36- reverse order.
powerline-2.8.1/docs/source/configuration.rst:37:#. User configuration directory located in :file:`$XDG_CONFIG_HOME/powerline`.
powerline-2.8.1/docs/source/configuration.rst-38- This usually corresponds to :file:`~/.config/powerline` on all platforms.
##############################################
powerline-2.8.1/docs/source/configuration/local.rst-196- ~/example )``. In addition to arrays usual colon-separated “array” string
powerline-2.8.1/docs/source/configuration/local.rst:197: can be used: ``POWERLINE_CONFIG_PATHS=$HOME/path1:$HOME/path2``.
powerline-2.8.1/docs/source/configuration/local.rst-198-
##############################################
powerline-2.8.1/docs/source/configuration/local.rst-224-
powerline-2.8.1/docs/source/configuration/local.rst:225:In addition to the above configuration options ``$POWERLINE_COMMAND``
powerline-2.8.1/docs/source/configuration/local.rst-226-environment variable can be used to tell shell or tmux to use specific powerline
powerline-2.8.1/docs/source/configuration/local.rst:227:implementation and ``$POWERLINE_CONFIG_COMMAND`` to tell zsh or tmux where
powerline-2.8.1/docs/source/configuration/local.rst-228-``powerline-config`` script is located. This is mostly useful for putting
##############################################
powerline-2.8.1/docs/source/configuration/local.rst-232-
powerline-2.8.1/docs/source/configuration/local.rst:233: ``$POWERLINE_COMMAND`` is always treated as one path in shell bindings, so
powerline-2.8.1/docs/source/configuration/local.rst-234- path with spaces in it may be used. To specify additional arguments one may
powerline-2.8.1/docs/source/configuration/local.rst:235: use ``$POWERLINE_COMMAND_ARGS``, but note that this variable exists for
powerline-2.8.1/docs/source/configuration/local.rst-236- testing purposes only and may be removed. One should use :ref:`Environment
##############################################
powerline-2.8.1/docs/source/configuration/local.rst-239-To disable prompt in shell, but still have tmux support or to disable tmux
powerline-2.8.1/docs/source/configuration/local.rst:240:support environment variables ``$POWERLINE_NO_{SHELL}_PROMPT`` and
powerline-2.8.1/docs/source/configuration/local.rst:241:``$POWERLINE_NO_{SHELL}_TMUX_SUPPORT`` can be used (substitute ``{SHELL}`` with
powerline-2.8.1/docs/source/configuration/local.rst-242-the name of the shell (all-caps) that should be affected (e.g. ``BASH``) or use
##############################################
powerline-2.8.1/docs/source/configuration/local.rst-248-In order to keep shell prompt, but avoid launching Python twice to get unused
powerline-2.8.1/docs/source/configuration/local.rst:249::ref:`above <config-themes-above>` lines in tcsh ``$POWERLINE_NO_TCSH_ABOVE`` or
powerline-2.8.1/docs/source/configuration/local.rst:250:``$POWERLINE_NO_SHELL_ABOVE`` variable should be set.
powerline-2.8.1/docs/source/configuration/local.rst-251-
powerline-2.8.1/docs/source/configuration/local.rst-252-In order to remove additional space from the end of the right prompt in fish
powerline-2.8.1/docs/source/configuration/local.rst:253:that was added in order to support multiline prompt ``$POWERLINE_NO_FISH_ABOVE``
powerline-2.8.1/docs/source/configuration/local.rst:254:or ``$POWERLINE_NO_SHELL_ABOVE`` variable should be set.
powerline-2.8.1/docs/source/configuration/local.rst-255-
##############################################
powerline-2.8.1/docs/source/configuration/reference.rst-40- ======= ===================================================================
powerline-2.8.1/docs/source/configuration/reference.rst:41: auto ``xterm`` or ``fbterm`` depending on ``$TERM`` variable value:
powerline-2.8.1/docs/source/configuration/reference.rst-42- ``TERM=fbterm`` implies ``fbterm`` escaping style, all other values
##############################################
powerline-2.8.1/docs/source/installation.rst-84-will have to be done (:file:`~/.local/bin` should be replaced with some path
powerline-2.8.1/docs/source/installation.rst:85:present in ``$PATH``).
powerline-2.8.1/docs/source/installation.rst-86-
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-51-#) If this problem is observed specifically within bash make sure that you clean
powerline-2.8.1/docs/source/troubleshooting.rst:52: ``$POWERLINE_COMMAND`` and ``$PROMPT_COMMAND`` environment variables on
powerline-2.8.1/docs/source/troubleshooting.rst-53- startup or, at least, that it was cleaned after update. While different
powerline-2.8.1/docs/source/troubleshooting.rst:54: ``$POWERLINE_COMMAND`` variable should not cause any troubles most of time
powerline-2.8.1/docs/source/troubleshooting.rst-55- (and when it will cause troubles are rather trivial) spoiled
powerline-2.8.1/docs/source/troubleshooting.rst:56: ``$PROMPT_COMMAND`` may lead to strange error messages or absence of exit
powerline-2.8.1/docs/source/troubleshooting.rst-57- code reporting.
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-73- this problem should not be seen after update only, it contains another
powerline-2.8.1/docs/source/troubleshooting.rst:74: example of ``$PROMPT_COMMAND`` spoiling results.
powerline-2.8.1/docs/source/troubleshooting.rst-75-
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-137-In order for tmux bindings to work ``powerline-config`` script is required to be
powerline-2.8.1/docs/source/troubleshooting.rst:138:present in ``$PATH``. Alternatively one may define ``$POWERLINE_CONFIG_COMMAND``
powerline-2.8.1/docs/source/troubleshooting.rst-139-environment variable pointing to the location of the script. *This variable must
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-149-Make sure that powerline command that sets prompt appears the very first in
powerline-2.8.1/docs/source/troubleshooting.rst:150:``$PROMPT_COMMAND``. To do this ``powerline.sh`` needs to be sourced the very
powerline-2.8.1/docs/source/troubleshooting.rst:151:last, after all other users of ``$PROMPT_COMMAND``.
powerline-2.8.1/docs/source/troubleshooting.rst-152-
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-155-
powerline-2.8.1/docs/source/troubleshooting.rst:156:Make sure that powerline commands appear in ``$PROMPT_COMMAND``: some users of
powerline-2.8.1/docs/source/troubleshooting.rst:157:``$PROMPT_COMMAND`` have a habit of overwriting the value instead of
powerline-2.8.1/docs/source/troubleshooting.rst-158-prepending/appending to it. All powerline commands start with ``_powerline`` or
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-170-
powerline-2.8.1/docs/source/troubleshooting.rst:171:* There is some other user of ``$PROMPT_COMMAND`` which prepended to this
powerline-2.8.1/docs/source/troubleshooting.rst-172- variable, but did not bother keeping the exit code. For the best experience
powerline-2.8.1/docs/source/troubleshooting.rst:173: powerline must appear first in ``$PROMPT_COMMAND`` which may be achieved by
powerline-2.8.1/docs/source/troubleshooting.rst-174- sourcing powerline bindings the last.
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-177- Resourcing bash bindings will not resolve the problem unless you clear
powerline-2.8.1/docs/source/troubleshooting.rst:178: powerline commands from ``$PROMPT_COMMAND`` first.
powerline-2.8.1/docs/source/troubleshooting.rst-179-
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-183-If you are using ``pip`` based installation do not forget to add pip-specific
powerline-2.8.1/docs/source/troubleshooting.rst:184:executable path to ``$PATH`` environment variable. This path usually looks
powerline-2.8.1/docs/source/troubleshooting.rst:185:something like ``$HOME/.local/bin`` (linux) or
powerline-2.8.1/docs/source/troubleshooting.rst:186:``$HOME/Library/Python/{python_version}/bin`` (OS X). One may check out where
powerline-2.8.1/docs/source/troubleshooting.rst-187-``powerline-config`` script was installed by using ``pip show -f
##############################################
powerline-2.8.1/docs/source/troubleshooting.rst-209-This happens because `z <https://github.com/rupa/z>`_ is launching some jobs in
powerline-2.8.1/docs/source/troubleshooting.rst:210:the background from ``$POWERLINE_COMMAND`` and these jobs fail to finish before
powerline-2.8.1/docs/source/troubleshooting.rst-211-powerline prompt is run.
##############################################
powerline-2.8.1/docs/source/usage/other.rst-96- powerline support. The location of this script may be specified via
powerline-2.8.1/docs/source/usage/other.rst:97: the ``$POWERLINE_CONFIG_COMMAND`` environment variable.
powerline-2.8.1/docs/source/usage/other.rst-98-
##############################################
powerline-2.8.1/docs/source/usage/shell-prompts.rst-118-.. note::
powerline-2.8.1/docs/source/usage/shell-prompts.rst:119: Dash users that already have ``$ENV`` defined should either put the ``.
powerline-2.8.1/docs/source/usage/shell-prompts.rst:120: …/shell/powerline.sh`` line in the ``$ENV`` file or create a new file which
powerline-2.8.1/docs/source/usage/shell-prompts.rst:121: will source (using ``.`` command) both former ``$ENV`` file and
powerline-2.8.1/docs/source/usage/shell-prompts.rst:122: :file:`powerline.sh` files and set ``$ENV`` to the path of this new file.
powerline-2.8.1/docs/source/usage/shell-prompts.rst-123-
powerline-2.8.1/docs/source/usage/shell-prompts.rst-124-.. warning::
powerline-2.8.1/docs/source/usage/shell-prompts.rst:125: Mksh users have to set ``$POWERLINE_SHELL_CONTINUATION`` and
powerline-2.8.1/docs/source/usage/shell-prompts.rst:126: ``$POWERLINE_SHELL_SELECT`` to 1 to get PS2 and PS3 (continuation and
powerline-2.8.1/docs/source/usage/shell-prompts.rst-127- select) prompts support respectively: as command substitution is not
##############################################
powerline-2.8.1/powerline/bindings/bash/powerline.sh-13-_powerline_tmux_pane() {
powerline-2.8.1/powerline/bindings/bash/powerline.sh:14: echo "${TMUX_PANE:-`TMUX="$_POWERLINE_TMUX" tmux display -p "#D"`}" | \
powerline-2.8.1/powerline/bindings/bash/powerline.sh-15- tr -d ' %'
##############################################
powerline-2.8.1/powerline/bindings/shell/powerline.sh-107-_powerline_tmux_pane() {
powerline-2.8.1/powerline/bindings/shell/powerline.sh:108: echo "${TMUX_PANE:-`TMUX="$_POWERLINE_TMUX" tmux display -p "#D"`}" | \
powerline-2.8.1/powerline/bindings/shell/powerline.sh-109- tr -d ' %'
##############################################
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-4-#
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:5:# Guess this relies on `$_` being set as to last argument to previous command
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-6-# which must be `.` or `source` in this case
##############################################
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-32- endif
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:33: set _POWERLINE_TMUX_PANE="`echo $_POWERLINE_TMUX_PANE:q | tr -d '% '`"
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-34- alias _powerline_tmux_set_pwd 'if ( $?TMUX && { tmux refresh -S >&/dev/null } ) tmux setenv -g TMUX_PWD_$_POWERLINE_TMUX_PANE $PWD:q ; if ( $?TMUX ) tmux refresh -S >&/dev/null'
##############################################
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-38- if ! $?POWERLINE_COMMAND then
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:39: set POWERLINE_COMMAND="`$POWERLINE_CONFIG_COMMAND:q shell command`"
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-40- else
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-41- if "$POWERLINE_COMMAND" == "" then
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:42: set POWERLINE_COMMAND="`$POWERLINE_CONFIG_COMMAND:q shell command`"
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-43- endif
##############################################
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-54-
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:55: alias _powerline_set_prompt 'set prompt="`$POWERLINE_COMMAND:q $POWERLINE_COMMAND_ARGS shell left -r .tcsh --renderer-arg=client_id=$$ --last-exit-code=$POWERLINE_STATUS --width=$POWERLINE_COLUMNS`"'
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:56: alias _powerline_set_rprompt 'set rprompt="`$POWERLINE_COMMAND:q $POWERLINE_COMMAND_ARGS shell right -r .tcsh --renderer-arg=client_id=$$ --last-exit-code=$POWERLINE_STATUS --width=$POWERLINE_COLUMNS`"'
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh:57: alias _powerline_set_columns 'set POWERLINE_COLUMNS=`stty size|cut -d" " -f2` ; set POWERLINE_COLUMNS=`expr $POWERLINE_COLUMNS - 2`'
powerline-2.8.1/powerline/bindings/tcsh/powerline.tcsh-58-
##############################################
powerline-2.8.1/powerline/bindings/vim/__init__.py-364- def _last_tab_nr():
powerline-2.8.1/powerline/bindings/vim/__init__.py:365: return int(vim.eval('tabpagenr("$")'))
powerline-2.8.1/powerline/bindings/vim/__init__.py-366-
##############################################
powerline-2.8.1/powerline/bindings/vim/__init__.py-394- def __getitem__(key):
powerline-2.8.1/powerline/bindings/vim/__init__.py:395: return vim.eval('$' + key)
powerline-2.8.1/powerline/bindings/vim/__init__.py-396-
##############################################
powerline-2.8.1/powerline/bindings/vim/__init__.py-398- def get(key, default=None):
powerline-2.8.1/powerline/bindings/vim/__init__.py:399: return vim.eval('$' + key) or default
powerline-2.8.1/powerline/bindings/vim/__init__.py-400-
##############################################
powerline-2.8.1/powerline/lint/spec.py-36- Methods that create the specifications return ``self``, so calls to them
powerline-2.8.1/powerline/lint/spec.py:37: may be chained: ``Spec().type(unicode).re('^\w+$')``. This does not
powerline-2.8.1/powerline/lint/spec.py-38- apply to functions that *apply* specification like :py:meth`Spec.match`.
##############################################
powerline-2.8.1/powerline/segments/common/players.py-630-
powerline-2.8.1/powerline/segments/common/players.py:631:Requires version >= 2.3.0 and ``mocp`` executable in ``$PATH``.
powerline-2.8.1/powerline/segments/common/players.py-632-
##############################################
powerline-2.8.1/powerline/segments/shell.py-89- displayed. If not specified the value is taken from
powerline-2.8.1/powerline/segments/shell.py:90: ``$POWERLINE_DEFAULT_MODE`` variable. This variable is set by zsh
powerline-2.8.1/powerline/segments/shell.py-91- bindings for any mode that does not start from ``vi``.
##############################################
powerline-2.8.1/powerline/segments/vim/__init__.py-257- :param bool shorten_user:
powerline-2.8.1/powerline/segments/vim/__init__.py:258: Shorten ``$HOME`` directory to :file:`~/`. Does not work for files with
powerline-2.8.1/powerline/segments/vim/__init__.py-259- scheme.
##############################################
powerline-2.8.1/tests/shlib/common.sh-1-: ${USER:=`id -un`}
powerline-2.8.1/tests/shlib/common.sh:2:: ${HOME:=`getent passwd $USER | cut -d: -f6`}
powerline-2.8.1/tests/shlib/common.sh-3-
##############################################
powerline-2.8.1/debian/changelog.upstream-12-- Added awesome 4+ support.
powerline-2.8.1/debian/changelog.upstream:13:- Added support for `$pipestatus` in bash.
powerline-2.8.1/debian/changelog.upstream-14-- Recognize terminal-job mode.
##############################################
powerline-2.8.1/debian/changelog.upstream-132-- Added a way to write error log to Vim global variable.
powerline-2.8.1/debian/changelog.upstream:133:- `powerline` script now supports overrides from `$POWERLINE_CONFIG_OVERRIDES`,
powerline-2.8.1/debian/changelog.upstream:134: `$POWERLINE_THEME_OVERRIDES` environment variables, so does `powerline-config`
powerline-2.8.1/debian/changelog.upstream-135- script.
powerline-2.8.1/debian/changelog.upstream-136-- `powerline` and `powerline-config` scripts now support taking paths from
powerline-2.8.1/debian/changelog.upstream:137: `$POWERLINE_CONFIG_PATHS`.
powerline-2.8.1/debian/changelog.upstream-138-- `powerline-lint` is now able to report dictionaries which were merged in to
##############################################
powerline-2.8.1/debian/changelog.upstream-164-- `detect` argument value was renamed to `auto` in network segments.
powerline-2.8.1/debian/changelog.upstream:165:- `$POWERLINE_COMMAND` is now a single path to one executable. No arguments to
powerline-2.8.1/debian/changelog.upstream:166: the executable are allowed inside `$POWERLINE_COMMAND`. Overrides using
powerline-2.8.1/debian/changelog.upstream:167: argument to `$POWERLINE_COMMAND` are now deprecated.
powerline-2.8.1/debian/changelog.upstream:168:- In place of overrides being part of `$POWERLINE_COMMAND` variable all shell
powerline-2.8.1/debian/changelog.upstream:169: and tmux bindings now support overrides from `$POWERLINE_CONFIG_OVERRIDES` and
powerline-2.8.1/debian/changelog.upstream:170: `$POWERLINE_THEME_OVERRIDES` environment variables.
powerline-2.8.1/debian/changelog.upstream:171:- In place of config paths specified as a part of `$POWERLINE_COMMAND` variable
powerline-2.8.1/debian/changelog.upstream:172: paths are now taken from `$POWERLINE_CONFIG_PATHS` environment variable.
powerline-2.8.1/debian/changelog.upstream:173:- `$POWERLINE_CONFIG` was replaced with `$POWERLINE_CONFIG_OVERRIDES` for
powerline-2.8.1/debian/changelog.upstream-174- zpython bindings when talking about overrides.
powerline-2.8.1/debian/changelog.upstream:175:- `$POWERLINE_THEME_CONFIG` was renamed to `$POWERLINE_THEME_OVERRIDES` in
powerline-2.8.1/debian/changelog.upstream-176- zpython bindings.
powerline-2.8.1/debian/changelog.upstream:177:- `$POWERLINE_CONFIG` was replaced with `$POWERLINE_CONFIG_COMMAND` in all shell
powerline-2.8.1/debian/changelog.upstream-178- bindings when talking about path to `powerline-config` executable.