Good morning,
On 12 Feb 2019, at 2:33, Bruce Van Allen wrote:
Agreed. I did this several years ago - I forget which OS X version -
and had multiple troubles whose origin was obscure until I noticed
that an error message had an executable named in all caps but the same
word was in /usr/bin except in lower case.
Unless someone with detailed knowledge of macOS as it is now says this
isn't a problem any more (somehow), making the system case-insensitive
is NOT recommended.
Really getting OT now, but I wouldn't make blanket statements about
whether case (in)sensitive is better. I switched to case-sensitive 10
years ago to __fix__ problems**, and I haven't had new problems with
case-sensitive for most of that time. I presume all mainstream apps are
tested on both case-(insensitive) filesystems these days. My suggestion
is make a clone of your boot disk, reformat, and test. If you have
problems, then switch back.
** I needed two CLI tools with conflicting names if used on
case-insensitive filesystem; `head` and `HEAD` - two very different
tools. Due to frequent updates; switching filesystem was easier than
repeatedly fixing the tool paths/names.
Attempting to stay on topic - BBEdit never had any problems with
case-sensitive filesystem (at least none that I experienced).
-cng
--
Charlie Garrison <[email protected]>
Garrison Computer Services <http://www.garrison.com.au>
PO Box 380
Tumbarumba NSW 2653 Australia
--
This is the BBEdit Talk public discussion group. If you have a
feature request or need technical support, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <https://www.twitter.com/bbedit>
---
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/bbedit.
