If you're on windows, there is no case-sensitivity, so when using git, for
example, there are issues with "file" and "FILE" because they're the same
to windows. Then there are the names thou shalt never use (con, prn, aux,
nul, com1, com2, com3, com4, com5, com6, com7, com8, com9, com0, lpt1,
On Mon, Sep 24, 2018 at 8:26 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I know you know, but it bears repeating, you can never go wrong following
> that old IT adage, no special characters in a filename, no spaces or caps
> in a SQL column name. In fact I don't
Unfortunately, the tao of lc isn't documented everywhere, and things that
work on one os don't work on another, see "All the filenames that work on
every platform but not on Windows". There seems to be another issue with
single-quotes in paths, even though LC specifically substitutes them into
I know you know, but it bears repeating, you can never go wrong following that
old IT adage, no special characters in a filename, no spaces or caps in a SQL
column name. In fact I don't even like spaces in a filename because if at some
point I want to share it over FTP, and the FTP server has a
NM. This is related to having double-quotes in a foldername.
On Sat, Sep 22, 2018 at 3:47 PM Mike Kerner
wrote:
> Is anyone having issues with creating and assigning SOS's as behaviors in
> 9.0.1?
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created
