In response to Kreme earlier. I checked the permissions on\VCTTools using Get Info. I have had & write permissions. Everyone else has read permissions. The same permissions hold for the SH file hdbgsub.sh.
Is there some other way to check permissions other than Get Info? On Sunday, June 27, 2021 at 9:38:16 AM UTC-4 Neill Smith wrote: > > Yes it does exist. I can open that file (and any other SH file) in > AppleScript and edit it. I can open it directly using BBEdit but of course > it looks like garbage. > > This particular setup is from when my former company used Windows. On a > WinPC having VCTTools at c:\VCTTools on every computer meant anyone could > add a new tool (VCTTools was maintained in a SVN repository) to VCTTools > and then everyone could just update their VCTTools copy. No one had to edit > paths for their computer. > > When we moved to MacOS, VCTTools was placed at the ROOT LEVEL to get the > same effect. Files within VCTTools have paths set under this assumption. If > VCTTools were a folder under a USER under MacOS, any one updating to the > newest version would have to go in and edit paths in a bunch of files. > On Sunday, June 27, 2021 at 7:47:55 AM UTC-4 Ulrich Kapp wrote: > >> Hi Neill, >> >> Did you check whether the script file /VCTTools/bat/hdbgsub.sh does exist? >> >> Ulrich >> >> Am 27.06.2021 um 01:10 schrieb Neill Smith <nssmi...@gmail.com>: >> >> I recently upgraded my macOS from High Sierra to Big Sur. A script file >> that has run for years under BBEdit (and TextWrangler before) has quit >> working. The script is invoked from within a file [fname].GEO by picking >> the script from my scripts list in the BBEdit top bar. The script runs a >> program that reads the [fname].GEO file. >> >> Now the script doesn't run. I get the message >> >> A scripting error has occurred: >> >> sh: /VCTTools/bat/hdbgsub.sh: No such file or directory >> >> This directory does exist. I uninstalled BBEdit and did a clean >> reinstall. I had to contact BBEdit tech support in order to install the >> Command Line Tools because old versions of the tools had to be removed >> manually. >> >> I didn't write the original script. It was created by a colleague years >> ago. BBEdit tech support recommended that I contact this group. >> >> Thanks, >> >> Neill Smith >> >> -- >> This is the BBEdit Talk public discussion group. If you have a feature >> request or need technical support, please email "sup...@barebones.com" >> rather than posting here. Follow @bbedit on Twitter: < >> https://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 bbedit+un...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/bbedit/a8fc6e58-41f0-4ea1-9180-efea41378b86n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/bbedit/a8fc6e58-41f0-4ea1-9180-efea41378b86n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email "supp...@barebones.com" rather than posting here. Follow @bbedit on Twitter: <https://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 bbedit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/3ecf1116-80ec-407c-9430-1cd0fa2098d0n%40googlegroups.com.