3fa50605b3
There were three bugs: 1. The click bounds calculation was incorrect. I did the silly mistake of checking for <= bounds for the bottom and right sections of a Rect when checking if the mouse intersected - this is WRONG. For example, let's say you want to calculate if an x value of 5 falls between something that starts at 0 and is 5 long. It shouldn't, right? Because it draws from 0 to 4? But if you just did <= Rect.right(), you would get a hit - because it just does (start + width), so you get 5, and 5 <= 5! So, easy fix, change all far bounds checks to <. 2. The second bug is a mistake where I accidentally did not include bounds sets for my memory and net widgets. Instead, they set their bounds to the underlying graph representation, which is WRONG, since that bound gets updated on draw, and gets set to a slightly smaller rect due to borders! 3. A slightly sneakier one. This broke my bounds checks for the CPU widget - and it would have broken my process widget too. The problem lies in the concept of widgets that handle multiple "sub"-blocks internally, and how I was doing click detection internally - I would check if the bounds of the internal Components were hit. Say, the CPU, I would check if the internal graph was hit, then if the internal table was hit. But wait! I said in point 2 that a graph gets its borders updated on draw to something slightly smaller, due to borders! And there's the problem - it affected tables too. I was setting the bounds of components to that of the *internal* representation - without borders - but my click detection *needed* borders included! Solution? Add another trait function to check bordered bounds, and make the default implementation just check the existing bounds. For cases like internal Components that may need it, I add a separate implementation. I also switched over all border bounds checks for Widgets to that, since it's a bit more consistent.
bottom
A cross-platform graphical process/system monitor with a customizable interface and a multitude of features. Supports Linux, macOS, and Windows. Inspired by gtop, gotop, and htop.
--color gruvbox), along with IBM Plex Mono and Kitty
Features
As (yet another) process/system visualization and management application, bottom supports the typical features:
-
Graphical visualization widgets for:
- CPU usage over time, at an average and per-core level
- RAM and swap usage over time
- Network I/O usage over time
with support for zooming in/out the current time interval displayed.
-
Widgets for displaying info about:
-
A process widget for displaying, sorting, and searching info about processes, as well as support for:
- Kill signals
- Tree mode
-
Cross-platform support for Linux, macOS, and Windows, with more planned in the future.
-
Customizable behaviour that can be controlled with command-line flags or a config file, such as:
- Custom and pre-built colour themes
- Changing the default behaviour of some widgets
- Changing the layout of widgets
- Filtering out entries in disk and temperature widgets
-
Some other nice stuff, like:
-
And more!
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
# If required, update Rust on the stable channel
rustup update stable
cargo install bottom
# OR, --locked may be required due to how cargo install works
cargo install bottom --locked
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.3/bottom_0.6.3_amd64.deb
sudo dpkg -i bottom_0.6.3_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 tap clementtsang/bottom
brew install bottom
# If you need to be more specific, use:
brew install clementtsang/bottom/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.3
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
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.
Building
There are a few ways to go about doing this manually. Note that in all cases, you would want to build using the most recent version of stable Rust:
# If required, update Rust on the stable channel
rustup update stable
# Download from releases and install
curl -LO https://github.com/ClementTsang/bottom/archive/0.6.3.tar.gz
tar -xzvf 0.6.3.tar.gz
cargo install --path .
# Clone from master and install manually
git clone https://github.com/ClementTsang/bottom
cd bottom
cargo install --path .
# Clone and install the newest master version 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 them:
- Latest stable release, generated off of the release branch
- Latest nightly version, which is generated daily off of the master branch at 00:00 UTC
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.bashto$XDG_CONFIG_HOME/bash_completion or /etc/bash_completion.d/. - For fish, move
btm.fishto$HOME/.config/fish/completions/. - For zsh, move
_btmto one of your$fpathdirectories. - For PowerShell, add
. _btm.ps1to your PowerShell profile.
Usage
You can run bottom using btm.
- For help on flags, use
btm -hfor a quick overview orbtm --helpfor more details. - For info on key and mouse bindings, refer to the documentation or press
?inside bottom.
You can generally 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 problems, documentation, or code, contribution is always welcome! Please read CONTRIBUTING.md for details on how to contribute to bottom.
Contributors
Thanks to all contributors (emoji key):
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!