> A script that we ship to end users has to be portable, which is why that > command is a mouthful even though most of that syntax has been in "man > find" forever. But individual users only need something that works on > their machines. So POSIX trivia aside, "do whatever you would normally > do to search a bunch of files for a string" is still the best answer, > Again, I think it is not necessarily the case that users of Sage-the-software - say, in a CoCalc-provided notebook as a student - necessarily know how to "search a bunch of files for a string" or even know that there is such a thing. On Mac most ordinary users probably just use the Spotlight function, which searches the entire system. If you've ever searched for Sage stuff using that, you will know it is not super friendly (and then you have to wait for the system to open up Xcode to read the files, and it finds .c files, .py, .pyc, .pyx with the same string...).
And even that doesn't work in a notebook you aren't hosting or on Sage cell server, obviously, and again many users may not even know there is a directory structure at all. This is not a "highly peculiar set of disabilities" - rather, the skill set of people on sage-devel is a "highly peculiar set of abilities", even among people doing math on a regular basis. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/4a6f6817-4a3d-4249-97f3-74337e783047%40googlegroups.com.
