Yet another cross-platform graphical process/system monitor.
Go to file
ClementTsang 2401e583fb refactor: consolidate time graph components
This consolidates all the time graph drawing to one main location, as well
as some small improvements. This is helpful in that I don't have to
reimplement the same thing across three locations if I have to make one
change that in theory should affect them all. In particular, the CPU
graph, memory graph, and network graph are all now using the same,
generic implementation for drawing, which we call (for now) a component.

Note this only affects drawing - it accepts some parameters affecting style
and labels, as well as data points, and draw similarly to how it used to
before. Widget-specific actions, or things affecting widget state,
should all be handled by the widget-specific code instead. For example,
our current implementation of x-axis autohide is still controlled by the
widget, not the component, even if some of the code is shared. Components
are, again, only responsible for drawing (at least for now). For that
matter, the graph component does not have mutable access to any form of
state outside of tui-rs' `Frame`. Note this *might* change in the
future, where we might give the component state.

Note that while functionally, the graph behaviour for now is basically
the same, a few changes were made internally other than the move to
components. The big change is that rather than using tui-rs' `Chart`
for the underlying drawing, we now use a tweaked custom `TimeChart`
tui-rs widget, which also handles all interpolation steps and some extra
customization. Personally, I don't like having to deviate from the
library's implementation, but this gives us more flexibility and allows
greater control. For example, this allows me to move away from the old
hacks required to do interpolation (where I had to mutate the existing
list to avoid having to reallocate an extra vector just to insert one
extra interpolated point). I can also finally allow customizable
legends (which will be added in the future).
2022-04-28 23:36:53 -04:00
.cargo other: Comment out cross ARM targets (#376) 2020-12-26 16:24:06 -05:00
.cargo-husky/hooks refactor: Clean up some parts of data harvesting (#336) 2020-12-03 23:45:54 -05:00
.github ci: lock cargo-llvm-cov install in script (#715) 2022-04-28 01:39:58 -04:00
assets docs: migrate documentation over to mkdocs (#506) 2021-06-21 01:40:58 -04:00
deployment ci: add extra field to choco template 2022-02-02 23:31:35 -05:00
docs docs: add some search features to mkdocs config (#704) 2022-04-11 03:54:21 -04:00
sample_configs other: update default config file (#561) 2021-07-25 20:17:03 -04:00
src refactor: consolidate time graph components 2022-04-28 23:36:53 -04:00
tests refactor: remove some simple as-casts (#697) 2022-03-27 22:01:06 -04:00
.all-contributorsrc docs: add shurizzle as a contributor for code (#677) 2022-02-22 06:29:48 -05:00
.gitignore docs: Fix some missing text in docs 2021-06-21 02:03:10 -04:00
.markdownlint.json docs: Touch up some photos (#511) 2021-06-21 22:35:19 -04:00
build.rs other: add manpage file to cargo deb config, move back to build script (#693) 2022-03-11 06:45:05 -05:00
Cargo.lock refactor: consolidate time graph components 2022-04-28 23:36:53 -04:00
Cargo.toml refactor: consolidate time graph components 2022-04-28 23:36:53 -04:00
CHANGELOG.md bug: change as_ref() to build in Rust beta 1.61.0 (#711) 2022-04-27 18:34:49 -04:00
clippy.toml refactor: rewrite column algorithm (#227) 2020-09-09 21:51:52 -04:00
codecov.yml ci: increase codecov threshold to 5% (#712) 2022-04-27 18:19:48 -04:00
CONTRIBUTING.md docs: revert CFP for now (#633) 2021-12-19 15:42:22 -05:00
LICENSE Initial commit 2019-08-28 19:43:30 -04:00
README.md ci: use locked builds in deploy and nightly (#700) 2022-04-10 01:11:10 -04:00
rustfmt.toml other: remove redundant line in rustfmt 2021-10-02 21:32:27 -04:00

bottom

A customizable cross-platform graphical process/system monitor for the terminal.
Supports Linux, macOS, and Windows. Inspired by gtop, gotop, and htop.

CI status Codecov crates.io link Nightly documentation Stable documentation

Quick demo recording showing off bottom's searching, expanding, and process killing.

Demo GIF using the Gruvbox theme (--color gruvbox), along with IBM Plex Mono and Kitty

Features

As (yet another) process/system visualization and management application, bottom supports the typical features:

You can find more details in the documentation.

Support

bottom officially supports the following operating systems and corresponding architectures:

  • macOS (x86_64)
  • Linux (x86_64, i686, aarch64)
  • Windows (x86_64, i686)

These platforms are tested to work for the most part and issues on these platforms will be fixed if possible. Furthermore, binaries are expected to be built and tested using the most recent version of stable Rust.

For more details on known problems and unsupported platforms, feel free to check out the documentation page on support.

Installation

Cargo

Installation via cargo is done by installing the bottom crate:

# If required, update Rust on the stable channel
rustup update stable

cargo install bottom --locked

# Alternatively, --locked may be omitted if you wish to not used locked dependencies:
cargo install bottom

Arch Linux

There is an official package that can be installed with pacman:

sudo pacman -Syu bottom

Debian/Ubuntu

A .deb file is provided on each release:

curl -LO https://github.com/ClementTsang/bottom/releases/download/0.6.8/bottom_0.6.8_amd64.deb
sudo dpkg -i bottom_0.6.8_amd64.deb

Fedora/CentOS

Available in COPR:

sudo dnf copr enable atim/bottom -y
sudo dnf install bottom

Gentoo

Available in GURU and dm9pZCAq overlays:

sudo eselect repository enable guru
sudo emerge --sync guru
echo "sys-process/bottom" | sudo tee /etc/portage/package.accept_keywords/10-guru
sudo emerge sys-process/bottom::guru

or

sudo eselect repository enable dm9pZCAq
sudo emerge --sync dm9pZCAq
sudo emerge sys-process/bottom::dm9pZCAq

Nix

nix-env -i bottom

Solus

sudo eopkg it bottom

Homebrew

brew install bottom

MacPorts

sudo port selfupdate
sudo port install bottom

Scoop

scoop install bottom

Chocolatey

Choco package located here. Since validation of the package takes time, it may take a while to become available after a release.

choco install bottom

# The version number may be required for newer releases during the approval process:
choco install bottom --version=0.6.8

winget

You can find the packages here. Since validation of the package takes time, it may take a while to become available after a release.

winget install bottom

# Alternatively
winget install Clement.bottom

You can also manually do the same thing by going to the latest release and installing via the .msi file.

You can uninstall via Control Panel, Options, or winget --uninstall bottom.

Manually

There are a few ways to go about doing this manually. Note that you probably want to do so using the most recent version of stable Rust, which is how the binaries are built:

# If required, update Rust on the stable channel first
rustup update stable

# Option 1 - Download from releases and install
curl -LO https://github.com/ClementTsang/bottom/archive/0.6.8.tar.gz
tar -xzvf 0.6.8.tar.gz
cargo install --path .

# Option 2 - Clone from master and install manually
git clone https://github.com/ClementTsang/bottom
cd bottom
cargo install --path .

# Option 3 - Clone and install directly from the repo all via Cargo
cargo install --git https://github.com/ClementTsang/bottom

Binaries

You can also try to use the generated release binaries and manually install on your system:

Auto-completion

The release binaries are packaged with shell auto-completion files for bash, fish, zsh, and Powershell. To install them:

  • For bash, move btm.bash to $XDG_CONFIG_HOME/bash_completion or /etc/bash_completion.d/.
  • For fish, move btm.fish to $HOME/.config/fish/completions/.
  • For zsh, move _btm to one of your $fpath directories.
  • For PowerShell, add . _btm.ps1 to your PowerShell profile.

Usage

You can run bottom using btm.

  • For help on flags, use btm -h for a quick overview or btm --help for more details.
  • For info on key and mouse bindings, press ? inside bottom or refer to the documentation.

You can find more information on usage in the documentation.

Configuration

bottom accepts a number of command-line arguments to change the behaviour of the application as desired. Additionally, bottom will automatically generate a configuration file on the first launch, which one can change as appropriate.

More details on configuration can be found in the documentation.

Contribution

Whether it's reporting bugs, suggesting features, maintaining packages, or submitting a PR, contribution is always welcome! Please read CONTRIBUTING.md for details on how to contribute to bottom.

Contributors

Thanks to all contributors:


Marcin Wojnarowski

💻 📦

Mahmoud Al-Qudsi

💻

Andy

💻

Kim Brose

💻

Sven-Hendrik Haase

📖

Artem Polishchuk

📦 📖

Trung Lê

📦 🚇

dm9pZCAq

📦 📖

Lukas Rysavy

💻

Erlend Hamberg

💻

Frederick Zhang

💻

pvanheus

💻

Zeb Piasecki

💻

georgybog

📖

Brian Di Palma

📖

Lasha Kanteladze

📖

Herby Gillot

📖

Greg Brown

💻

TotalCaesar659

📖

George Rawlinson

📖 📦

adiabatic

📖

Randy Barlow

💻

Patrick Jackson

🤔 📖

Mateusz Mikuła

💻

Guillaume Gomez

💻

shura

💻

Thanks

  • This project is very much inspired by gotop, gtop, and htop.

  • This application was written with many, many libraries, and built on the work of many talented people. This application would be impossible without their work. I used to thank them all individually but the list got too large...

  • And of course, another round of thanks to all contributors and package maintainers!