Re: SixPack mods for Linux users

--- In [email protected], "bh_mayor" <stuart@...> wrote:
>
> Paul,
> 
> Indeed I know that "SLASH=/" does not work in windows, as the script was written for Linux and designated in my post as such. However, notwithstanding the foregoing, the absence of a definition for "SLASH" (in say the Windows world) would leave the config file using the default as defined as "\".
> 

Blake, I recall your post:

"3) Amendment of the "SixPack.conf" so that it is more Linux friendly using
substitution for the "\". If no "SLASH" variable is defined (as would be with
the startup file inclusive herein above), then it would use the Windows "\"
instead of the Linux "/" and startup normally."

If no SLASH variable is defined your config file simply doesn't work under Windows.....(and also if SLASH variable is defined BTW:)

> Now, I had not realized that Windows would deal with "/", figuring why would someone define it otherwise if a more standard solution was available? Besides, it is not unlike Mr. Gates and his minyans to stand in absolute contradiction to standards existing long behofe he was ever a player on the IT scene.
> 

It's not Windows that deals with "/", but it's Hercules (a program)
that reads the config file and accepts both "\"  and "/".

Windows by itself doesn't support "/".
 
> Yet still, using my solution does make the file paths more readable for the Windows user that is used to that style, while provisioning the flexibility for the Linux user by running my script.
> 
> 

Your solution works only in Linux.

I think a right solution should work both in Windows and Linux.....

Regards.

Paul

> Blake
> 
>