Re: Using Find with Shell on Mac

2017-08-10 Thread Warren Samples via use-livecode
On 08/10/2017 10:46 AM, Bob Sneidar via use-livecode wrote: But I beg to be excused. :D It's okay, Bob. Stay curious! Warren ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage

Re: Using Find with Shell on Mac

2017-08-10 Thread Bob Sneidar via use-livecode
Well it's case sensitive for one. echo $home produces a blank line. $HOME produces my home folder. But I beg to be excused. I got into computers at first because of the Macintosh. I cannot remember hundreds of commands along with their varied arguments and flags and nuances. I will probably

Re: Using Find with Shell on Mac

2017-08-10 Thread Warren Samples via use-livecode
On 08/10/2017 09:36 AM, Bob Sneidar via use-livecode wrote: OH RIGHT. I thought you were talking about using this in the terminal. I know about the LC environment variables. Bob S What does this do in Terminal? 'echo $HOME' ___ use-livecode

Re: Using Find with Shell on Mac

2017-08-10 Thread Bob Sneidar via use-livecode
OH RIGHT. I thought you were talking about using this in the terminal. I know about the LC environment variables. Bob S > On Aug 9, 2017, at 18:51 , Sannyasin Brahmanathaswami via use-livecode > wrote: > > @ bob > > try it in msg > > put $HOME > > see the

Re: Using Find with Shell on Mac

2017-08-09 Thread Sannyasin Brahmanathaswami via use-livecode
@ bob try it in msg put $HOME see the dictionary for $ but this is one more of those "Alice in wonderland features" of LC that you will only discover after you fall into the hole (hehe) like the long owner of the target "why index" to locate and find return the long paths to the

Re: Using Find with Shell on Mac

2017-08-09 Thread Alex Tweedly via use-livecode
On 10/08/2017 01:10, Alex Tweedly via use-livecode wrote: You should put quotes around the "*.livecode", because find ~/ -iname "*.livecode" -print will do what I think you want to do. Whereas if you do, find ~/ -iname *.livecode -print the *.livecode is seen by, and interpreted by,

Re: Using Find with Shell on Mac

2017-08-09 Thread Alex Tweedly via use-livecode
You should put quotes around the "*.livecode", because find ~/ -iname "*.livecode" -print will do what I think you want to do. Whereas if you do, find ~/ -iname *.livecode -print the *.livecode is seen by, and interpreted by, shell - and so expands to the livecode files in your home

Re: Using Find with Shell on Mac

2017-08-09 Thread Bob Sneidar via use-livecode
Not sure what $Home is. I didn't know you could refer to your home folder that way. But keep in mind that you can change what Spotlight does and does not index. you home folder typically is not a place you would create new folders and files for. What would be the point to indexing it? Bob S

Using Find with Shell on Mac

2017-08-09 Thread Sannyasin Brahmanathaswami via use-livecode
I'm pretty much fed up with Spotlight. On Linux apps I use Locate, which is really efficient. but setting up and keep the locate dbase on mac is also frought with issues. it will not index $Home which is weird. FIND is slower of course, but perfectly effective. this: find ~/ -iname