mirror of
https://github.com/smxi/inxi.git
synced 2025-02-23 21:42:18 +00:00
cleanup of stuff, nothing.
This commit is contained in:
parent
96d14dc762
commit
fcf19553dd
11
inxi
11
inxi
|
@ -3724,6 +3724,15 @@ get_cmdline()
|
||||||
##print_screen_output "Marker"
|
##print_screen_output "Marker"
|
||||||
##print_screen_output "\$ppid='$ppid' -=- $(< /proc/$ppid/cmdline)"
|
##print_screen_output "\$ppid='$ppid' -=- $(< /proc/$ppid/cmdline)"
|
||||||
unset A_CMDL
|
unset A_CMDL
|
||||||
|
# http://transnum.blogspot.com/2008/11/bashs-read-built-in-supports-0-as.html
|
||||||
|
# Because BASH internally uses C-style strings, in which '\0' is the terminator,
|
||||||
|
# read -d $'\0' is essentially equivalent to read -d ''. This is why I believed
|
||||||
|
# read did not accept null-delimited strings. However, it turns out that BASH
|
||||||
|
# actually handles this correctly.
|
||||||
|
# I checked BASH’s source code and found the delimiter was simply determined by
|
||||||
|
# delim = *list_optarg; (bash-3.2/builtins/read.def, line 296) where list_optarg
|
||||||
|
# points to the argument following -d. Therefore, it makes no difference to the
|
||||||
|
# value of delim whether $'\0' or '' is used.
|
||||||
## note: need to figure this one out, and ideally clean it up and make it readable
|
## note: need to figure this one out, and ideally clean it up and make it readable
|
||||||
while read -d $'\0' L && [[ $i -lt 32 ]]
|
while read -d $'\0' L && [[ $i -lt 32 ]]
|
||||||
do
|
do
|
||||||
|
@ -3897,7 +3906,7 @@ get_irc_client_version()
|
||||||
# the hexchat author decided to make --version/-v return a gtk dialogue box, lol...
|
# the hexchat author decided to make --version/-v return a gtk dialogue box, lol...
|
||||||
# so we need to read the actual config file for hexchat. Note that older hexchats
|
# so we need to read the actual config file for hexchat. Note that older hexchats
|
||||||
# used xchat config file, so test first for default, then legacy. Because it's possible
|
# used xchat config file, so test first for default, then legacy. Because it's possible
|
||||||
# for this file to be use edited, doing some extra checks here.
|
# for this file to be user edited, doing some extra checks here.
|
||||||
if [[ -f ~/.config/hexchat/hexchat.conf ]];then
|
if [[ -f ~/.config/hexchat/hexchat.conf ]];then
|
||||||
file_data="$( cat ~/.config/hexchat/hexchat.conf )"
|
file_data="$( cat ~/.config/hexchat/hexchat.conf )"
|
||||||
elif [[ -f ~/.config/hexchat/xchat.conf ]];then
|
elif [[ -f ~/.config/hexchat/xchat.conf ]];then
|
||||||
|
|
Loading…
Reference in a new issue