> On Jan 7, 2023, at 6:35 PM, Godfrey DiGiorgi <[email protected]> wrote: > > > > I have no idea, Larry. I am no expert in UNIX/Linux command-line interface or > scripting systems, they have been irrelevant to my use of Apple computer > systems. > > My work was in writing, debugging, and documenting macOS native apps, IO > drivers, and the Xcode development system, not manipulating the system and > apps via a Terminal-based, command-line interface. When I was working (either > for my job or at my home for my personal stuff), I almost never found myself > using the command-line interfaces at all for anything other than the most > trivial of operations.
Therein lies a difference, because some things are trivial in a command line, for example if I want to edit all of a particular set of source files in a directory tree, it's simple in a command line: emacs foo_comm*[ch] `find . | grep foo_comm_test | grep [.][ch]$`& I have absolutely no idea how to do that from finder. One of the things that I have appreciated about MacOS, since I started using it about 20 years ago was that if I couldn't do something through their confusing GUI, at least I could get to the nice intuitive bash prompt in terminal. One thing I have found about Apple products is that it is trivially easy to do the things that they think that you should want to do, but as soon as you go off script they can make Linux seem well documented. > > The problem is almost certainly a change in the command-line interface > library that came in via one of the operating system updates … which one, > when, is a question you have to determine, and then you should contact > Apple's support groups to discover what changed, why, and how to use the > interface the way you need now. I did just use a bigger hammer and just put export PATH=/Applications/Emacs.app/Contents/MacOS:$PATH into my .bashrc > > And also, be aware that I retired nearly a decade ago. Whatever the details > of the OS that has changed at that level is nothing that has any impact or > interest for me at all. And certainly nothing whatever to do with Rich > Womer's original question that initiated this discussion thread. It is somewhat related because even though multiple people may have the same issue, if it isn't part of your experience, then you have a tendency (and not just on this one issue) to insist that it doesn't happen. You've used Apple products for decades, from within Apple, and the Apple culture. Your default use case is to do things the apple way. Unfortunately, the easier that Apple makes it to do things "the apple way" the harder it generally makes it to do things differently. Apple has good reasons to want to save everything to iCloud. Not the least of which is that it makes it easier for people who use iOS products (their major money maker) to access their files, and not lose them. This page: https://appletoolbox.com/how-to-remove-your-icloud-storage-plan/ says: On a Mac, open the System Preferences and click on Apple ID. Go to Overview to Sign Out, or go to iCloud to disable certain parts of iCloud. In other words if you don't do anything, things will be stored on iCloud. When I wanted to modify iCloud settings my instinct was to go to System Preferences and look for iCloud, but there isn't an iCloud in SysPref. Since I'm not steeped in Apple culture, it isn't intuitively obvious that the iCloud settings are hidden under Apple ID. Again, like many things Apple, if you want to do it their way, or think like they do, it's relatively straightforward, but if not, you usually have to go to a third party to find the relevant documentation. -- Larry Colen [email protected]. sent from Mirkwood -- %(real_name)s Pentax-Discuss Mail List To unsubscribe send an email to [email protected] to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
