From: ldo@nz.invalid   
      
   On Wed, 31 Dec 2025 18:42:45 +0000, bart wrote:   
      
   > In any case, it is easy enough to do a check on argc's value in your   
   > applications. (And on Windows, if it is 0 and you really need the   
   > path, you can get it with GetModuleFileNameA().)   
      
   Remember that, on *nix systems, the contents of argv are arbitrary and   
   caller-specified. And none of them need bear any relation to the   
   actual filename of the invoked executable.   
      
   In fact, it is quite common for utilities to behave differently based   
   on the name, as passed in argv[0], by which they are invoked.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)