dmitriy.kazimirov/inxi
1
0
Fork 0
mirror of https://github.com/smxi/inxi.git synced 2024-11-16 16:21:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fixed changelog typos

Browse source
This commit is contained in:
Harald Hope 2018-12-31 22:02:06 -08:00
parent 1976702562
commit 1b9dab01d1
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
inxi.changelog
View file

@ -20,19 +20,19 @@ when Ansible or MOTD started inxi. This is because they are not tty so trip the
non tty flag, which assumes it's in IRC in that case. The fix was to add a non tty flag, which assumes it's in IRC in that case. The fix was to add a
whitelist of known clients based on the parent name inxi discovers while running whitelist of known clients based on the parent name inxi discovers while running
inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file
issue reports then not follow them? Who knows. issue reports then not follow up on them? Who knows.
Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi
which disables the tty test as well. To handle that scenario, that is, when inxi is which disables the tty test as well. To handle that scenario, that is, when inxi is
not first in the pipe, I added many known terminal client names to the whitelists. not first in the pipe, I added many known terminal client names to the whitelists.
This works in my tests, though the possible terminals, or programs with embedded This works in my tests, though the set of possible terminals, or programs with
terminals, is quite large, but inxi handles most of them automatically. When it embedded terminals, is quite large, but inxi handles most of them automatically. When
doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty it doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
in the meantime. in the meantime.
2. Issue #171 by Vascom finally pinned down the wide character issue which manifests 2. Issue #171 by Vascom finally pinned down the wide character issue which manifests
in some character sets, like greek or russian utf8. The fix was more of a work-around in some character sets, like greek or russian utf8. The fix was more of a work-around
than a true fix, but inxi now simply checks the weather local time output for wide than a true fix, but inxi now simply checks the weather local time output for wide
characters, and if detected, switches the local date/time format to iso standard, characters, and if detected, switches the local date/time format to iso standard,
which is does not contain non ascii characters as far as I can tell. This seemed to which does not contain non ascii characters as far as I can tell. This seemed to
fix the issue. fix the issue.
3. Added iso9660 from excluded file systems for partitions, not sure how inxi 3. Added iso9660 from excluded file systems for partitions, not sure how inxi
missed that one for so long. missed that one for so long.