WeeChat is mispelled as "Weechat" and weechat binary isn't recognized about inxi HOT 6 CLOSED

Assuming weechat-curses and weechat work exactly the same, this should now be 
corrected.

Confirm that it's correct with inxi output and then I'll close this issue.

08:20:18 <@Mikaela> CPU(s)~2 Hexa core Intel Xeon CPU X5675s (-HT-MCP-SMP-) 
clocked at 3067.056 Mhz Kernel~3.2.54-grbfs-kapsi x86_64 Up~36 days 
Mem~50984.7/145121.9MB HDD~146.8GB(36.6% used) Procs~16 Client~Unknown : 
.nfs00000000144ae2df00113b2c inxi~2.1.3  

Then weechat has changed more than its name.

Tracking down this stuff requires explicit tests with custom test data 
collectors.

I won't do this via this here issue thing because it takes forever to get 
feedback, so if you want it tracked down, you'll have to find me on 
irc.oftc.net channel #smxi as h2 then we can do some data collecting.

However weechat certainly changed something more than its name.

Just to confirm: weechat -v 
show that output.

However, that probably won't matter because it looks like some internal weechat 
process is being returned as the actual process name, but again, we can only 
confirm that via custom data collection.

I'll post one you can run to collect output.

Getting irc clients identified is highly non trivial, they don't have a 
'--what-client-is-this' type query in irc.

% weechat -v
0.4.4-dev

I'll connect to OFTC soon.

08:57:53 Starting client version debugger
08:57:53 ------------------------------------------------------
08:57:53 EXISTS PPID: 13323
08:57:53 EXISTS: /proc/13323/exe
08:57:53 PPID PATH: /bin/dash
08:57:53 NAME LOWER: dash
08:57:53 CONTAINER PPPID: 14253
08:57:53 PPPID PATH: /home/users/mkaysi/.local/bin/.nfs00000000015abdfd0011d9be
08:57:53 PPPID PATH LOWER: 
/home/users/mkaysi/.local/bin/.nfs00000000015abdfd0011d9be
08:57:53 PPPID CLIENT WORKING NAME: .nfs00000000015abdfd0011d9be
08:57:53 ------------------------------------------------------
08:57:53 End client version debugger
08:57:53 exec: end of command 0 ("debuggercv"), return code: 0

This was a user setup/path issue, there is no current failure with weechat, the 
initial fixes corrected the problem.