Discussion
Could you open an issue for this on GitHub(https://github.com/r1w1s1/slackfetch) or Slackware Forge? Please include the commands and output you used, so we can track whether slackfetch should detect tmux after su -.
Reported as issue #1.
Hi, it seems the pkgs logic is flawed in slackfetch, all packages with names ended with _slack15.0 are counted as unofficual now, while in fact they are from official repo updates.
Fixed in slackfetch 1.2.2; _slack15.0 and _slack16.0 packages are now correctly recognized as official. Thanks you.
Is it pushed to forge.slackware.nl or somewhere else ? I did not see any commits at nl.
can you check now?
thank you, I will check.
@r1w1s1 My vote for minimalist. I do love the classic logo, but it would make slackfetch another fastfetch. I personally prefer it to be a tad different.
Not a Slack guy, but I'd also say that a minimalist logo complements the minimalist idea of your fetch.
Here's ufetch, for example (attached)
After daily-driving FreeBSD for nearly a year, Devuan feels like Ubuntu to me. 😂
Another bit: in a TMUX session, as a normal user the
shellreports something likebash 5.1.16 (tmux). But if yousu -to switch torootin the same session, thetmuxbit is gone. I check the script where it detects whether theTMUXenv exists, and yes it is gone after su. But I would think there will be another way?