smxi
smxi
Closing this issue, no response. Why spend your time posting an issue without confirming the fix is correct? Makes no sense to me.
Issue #170 helped explain what is going on here. A sample of the generated line Info (inxi -Ixxx) would have been useful since I have zero samples from ansible/chef type...
Note that pinxi contains a guess at a fix for ansible / chef, but it requires seeing the data from the Info: line when run in ansible, that will show...
Yes, the --tty option isn't going anywhere, it's an easy to use/remember fallback option. However handling many cases automatically isn't a bad thing to do, so that's why inxi does...
That's an interesting scenario, thanks for taking the time to find a similar issue. I had not considered what happens to inxi when running as a cron job, hadn't seen...
Note that in order to actually update to handle more scenarios automatically, the debugger must be run in order to learn what inxi 'sees' about what is running it. You...
Is the F: value the full version output? If that is the full version, pinxi 3.0.21-7 should show compton v:, but show: pinxi -SGxxx just to be sure. I forgot...
I forgot about gala, I have a deepin wm so I can test that one. Oh, no, wait, I see why gala isn't in there, comment says, super slow result...
The original idea for compositor detection was something along those lines, but I don't know anything like that in Perl I can use. this is a library, I checked for...
The compton v: glitch is fixed now in pinxi 3.0.21-10