| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Updates the border colour on the Nord colour scheme to look less jarring.
|
|
Major update is tui-rs from 0.13 to 0.14. This change allows us to update our tables to make them look nicer!
|
|
For consistency, we now don't automatically jump to the top of the list when using a sort shortcut. This behaviour already occurred with the sort menu and sorting by mouse clicks, so this is just now more consistent (and IMO less annoying, you can also always jump to the top via gg).
|
|
Fixes sorting menus and shortcuts not syncing correctly if the sorting window is open.
|
|
widget (#416)
Fixes grouped mode having different spacing than non-grouped mode.
|
|
Adds mouse support for sorting columns within the process widget. You can now click on the column header to sort (or invert the sort).
|
|
|
|
|
|
|
|
|
|
Ctrl-w deletes one word backwards from the current cursor location. Ctrl-h is just an alias for backspace.
|
|
Allows toggling the advanced kill menu via --advanced_kill or advanced_kill=true.
|
|
Adds colour schemes for Nord, along with a light variant.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(#398)
So it seems that tui-rs doesn't like rendering my CPU bars if the height is exactly 1. It needs at least 2. I have no idea why, this is probably something weird with how I render.
This, of course, breaks when there is only one row to report (i.e. with a dual core setup in #397).
The workaround switches the gap between the CPU and mem/net parts to 0, and increases the CPU's draw height by 1, only when the height is otherwise 1 (so the draw height is now at least 2). This does have the side effect of including an extra line to the side borders, but I think it's fine.
|
|
* docs: update README.md [skip ci]
* docs: update .all-contributorsrc [skip ci]
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
When running without elevated permissions under macOS, sysinfo cannot
query states of processes by root user, which results in 0.0% CPU usage
for all this kind of processes (and state = Unknown).
Here we use `ps`, which has SUID, as a fallback to query CPU usages.
This can be potentially applied to other properties if needed in the
future (we'll need a proper struct and parser).
|
|
* docs: update README.md [skip ci]
* docs: update .all-contributorsrc [skip ci]
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
|
|
|
Fixes a bug where you could make the sorting arrow disappear in the mem column if you did:
1. Go to proc widget
2. Switch to memory values from %
3. Press `m`
|
|
|
|
|
|
|
|
Fixes the `hide_table_gap` option not working with the battery widget.
|
|
|
|
Adds a new option in the config file to filter out network interfaces. Also add the option to filter by whole words.
Interface follows that of the existing ones:
```toml
[net_filter]
is_list_ignored = false
list = ["virbr0.*"]
regex = true
case_sensitive = false
whole_word = false
```
|
|
|
|
|
|
|
|
Adds a `process_command` flag and config option to default to showing the full command in the process widget on startup.
|
|
Just adds uid and gid collection to the process collection step. This does not add GUI changes, that'll come later.
|
|
Comment out some linkers set in `.config/cargo.toml` for ARM targets.
|
|
|
|
|
|
|
|
Fixes the colour order being off in basic mode, and not using the average CPU colour.
|
|
Firstly, note this currently won't affect basic mode. There is code changes due to it, but instead, we'll just display `0.0B/0.0B` instead. I'm personally not really sure if we want to get rid of it in basic mode, since it'll leave an ugly gap in that mode.
Anyways, this change is mainly for the normal mode. All this does is hide the legend entry and chart if the total SWAP drops to 0 KB. It also has a small change to do a unit check on the memory used, as well as slightly adjusting the calculation we use.
|
|
Refactors to use only heim for Linux builds. This is now much easier to do since the 0.1 version of heim works fine for ARM. This is ideal since having to rely on two separate sources of data isn't the greatest if we can avoid it.
Sysinfo is still required for macOS and Windows, though. Temperature sensors do not work for those from heim, and for some reason, networks also don't work on Windows with heim...?
My personal CPU core calculation is also currently Linux-only, and as such, I'll still rely on sysinfo for Windows and macOS for now.
This isn't really a big optimization or anything btw. Just something I wanted to try.
|
|
|
|
|
|
|
|
|
|
Use heim on ARM targets again where appropriate.
|
|
|
