POWERLINE-CONFIG(1)

🌸 NAME 🌸

okay so this is POWERLINE-CONFIG(1), aka the powerline-config manual page, and it's literally the script used to obtain powerline configuration. That's the whole NAME moment, bestie β€” short, iconic, no filler. πŸ’…


✨ SYNOPSIS ✨

powerline-config [-pPATH]… tmux ACTION ( [-s |n )]
powerline-config [-pPATH]… shell ACTION [COMPONENT] [-sSHELL]

This synopsis is short and has main character energy, fr fr. πŸ‘‘


πŸ’… DESCRIPTION πŸ’…

Alright bestie, here's the tea on how this script gets configured. Lowkey all the flags are here, no cap.

  • -p, --config-path PATH β€” path to the configuration directory. If it is present then configuration files will only be sought in the provided path. May be provided multiple times to search in a list of directories. multiple paths, multiple chances to find your config β€” iykyk.
  • -h, --help β€” display help and exit. short, sweet, slay.

πŸŽ€ Arguments specific to tmux subcommand πŸŽ€

okay so if you're in the tmux subcommand era, these are the arguments that matter:

  • ACTION β€” if action is source then version-specific tmux configuration files are sourced; if it is setenv then special (prefixed with _POWERLINE) tmux global environment variables are filled with data from powerline configuration. Action setup is just doing setenv then source. that's the whole pipeline, periodt.
  • -s, --source β€” when using setup: always use configuration file sourcing. By default this is determined automatically based on tmux version: this is the default for tmux 1.8 and below. auto-pick energy, but you can force the source vibe.
  • -n, --no-source β€” when using setup: in place of sourcing directly execute configuration files. That is, read each needed powerline-specific configuration file, substitute $_POWERLINE_… variables with appropriate values and run tmux config line. This is the default behaviour for tmux 1.9 and above. that's the 1.9-and-above default, no cap.
  • -h, --help β€” display help and exit.

πŸ¦‹ Arguments specific to shell subcommand πŸ¦‹

  • ACTION β€” if action is command then preferred powerline command is output, if it is uses then powerline-config script will exit with 1 if specified component is disabled and 0 otherwise.
  • COMPONENT β€” only applicable for uses subcommand: makes powerline-config exit with 0 if specific component is enabled and with 1 otherwise. tmux component stands for tmux bindings (e.g. those that notify tmux about current directory changes), prompt component stands for shell prompt.
  • -s, --shell SHELL β€” shell for which query is run. tell it which shell you're querying, bestie.
  • -h, --help β€” display help and exit.

πŸ‘‘ AUTHOR πŸ‘‘

Written by Kim Silkebækken, Nikolay Pavlov, Kovid Goyal and contributors. The glyphs in the font patcher are created by Fabrizio Schiavi. iconic credits, honestly.


🚨 REPORTING BUGS 🚨

Report powerline-config bugs to ‐ https://github.com/powerline/powerline/issues. don't suffer in silence, bestie.


πŸ”— SEE ALSO πŸ”—

powerline(1) β€” go read that one too, it's giving related-manual energy.


This POWERLINE-CONFIG(1) page is rockin’ Powerline beta, dated Mar 11, 2025 β€” mwah, bye bestie πŸ«ΆπŸ’–

πŸ“¦ where this page comes from