On Thursday, May 7, 2020 at 9:58:55 AM UTC-7, John H Palmieri wrote: > > > > On Thursday, May 7, 2020 at 4:40:52 AM UTC-7, Michael Orlitzky wrote: >> >> On 5/6/20 11:28 PM, John H Palmieri wrote: >> > >> > And to clarify, this is what you expect users to use instead of >> > search_src? ;) >> > >> > > And to clarify, neither you nor Dima understand ";)"? > > > >> It's an improvement to sage-grep. In another message you said, "It was >> reimplemented in Python to make it work across platforms... and to make >> it faster." It's not a fair comparison if you don't write the find-grep >> command in a portable/efficient way. The one I gave is portable (the >> trailing "+" was added to POSIX around Y2K) and as fast as possible. >> >> 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, >> and will be far simpler than a command that needs to work on last week's >> Fedora and last decade's Solaris. In real life, I would "grep -irl" the >> whole directory, because that's what I normally do and is easy for me. >> > And in real life, I tend to use "git grep ..." so I can easily ignore large parts of the directory.
-- 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/454f4def-9286-40c1-b3b1-c8a849d750f3%40googlegroups.com.
