Skip to content

Conversation

@aaronkollasch
Copy link
Contributor

Occurs with lines too long that get truncated, causing unclosed parentheses and breaking the sed regex, leading to an empty output. The -l option fixes this.

The -T option is for removing unnecessary PIDs (thread PIDs) from pstree output and may remove the duplicate PIDs seen in #321.

May fix #321

Occurs with lines too long that get truncated, causing unclosed
parentheses and breaking the sed regex. The -l option fixes this.
-T is for removing unnecessary PIDs (thread PIDs) from pstree output.
@ethancedwards8
Copy link
Member

I'll review this later today when I'm at a PC.

As a side note, I saw your profile says you're a postdoc at Harvard. I'll be starting my undergrad there in the fall. Was that where your undergrad was as well?

@aaronkollasch
Copy link
Contributor Author

Thanks @ethancedwards8, and congrats!

I did my undergrad at Northwestern and PhD at Harvard Medical School (and stayed on for about a year as a postdoc) 🙂

@ethancedwards8 ethancedwards8 merged commit 2e176ef into dracula:master May 17, 2025
1 check passed
@ethancedwards8
Copy link
Member

Thanks for the contribution.

And thanks! Congrats on the PhD and postdoc.

@aaronkollasch aaronkollasch deleted the fix-tmux-ram-info branch May 17, 2025 20:50
@aaronkollasch
Copy link
Contributor Author

Thanks!

Also, just checked with a neovim instance and pstree -T does indeed remove the excess thread pids (though I actually didn't see the double-counting bug for some reason, even with all the thread pids).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Bug: [Excessive RAM usage reported by tmux_ram_info.sh plugin]

2 participants