Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Process tree rendering #945

Open
Denizantip opened this issue Oct 3, 2024 · 0 comments · May be fixed by #948
Open

[BUG] Process tree rendering #945

Denizantip opened this issue Oct 3, 2024 · 0 comments · May be fixed by #948
Assignees
Labels
bug Something isn't working

Comments

@Denizantip
Copy link

Denizantip commented Oct 3, 2024

Read the README.md and search for similar issues before posting a bug report!

Any bug that can be solved by just reading the prerequisites section of the README will likely be ignored.

Describe the bug

In BTOP, the process tree rendering works incorrectly. Redundant pipe characters.
btop_tree

In bpytop, it works correctly
bpytop_tree

To Reproduce

Turn tree view in btop.

Expected behavior

Expectation is exact like in bpython:
After last child no continuation of pipe characters

Screenshots

[If applicable, add screenshots to help explain your problem.]

Info (please complete the following information):

  • btop++ version: 1.3.0
  • Binary: self compiled
  • Architecture: x86_64
  • Platform: Linux
  • (Linux) Kernel: 6.8.0-45-generic
  • (OSX/FreeBSD) Os release version: Ubuntu 24.04
  • Terminal used: GNOME Terminal 3.52.0 using VTE 0.76.0 +BIDI +GNUTLS +ICU +SYSTEMD
  • Font used: Terminuss Nerd
@Denizantip Denizantip added the bug Something isn't working label Oct 3, 2024
@Denizantip Denizantip changed the title [BUG] [BUG] Process tree rendering Oct 3, 2024
@Denizantip Denizantip linked a pull request Oct 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants