On Fri, 1 May 2020 at 13:10, Michael Orlitzky <mich...@orlitzky.com> wrote:
>
> On 5/1/20 3:54 AM, John Cremona wrote:
> > I agree with David.  I use grep 1000 times a day and I do know how to
> > use a computer (and do not appreciate being patronised)
>
> I'm poking fun at the reasoning behind adding these functions to sage,
> not the people who use them. I've been on the wrong side of a spacebar
> heating[0] argument enough times to appreciate not wanting to change
> what works. But we should have had some faith in people and suggested
> grep from the start to avoid that problem.

Maybe.   Does the !grep method work for non-linux systems such as Windows?

It took me a few minutes to work out what to put on the line after
!grep.  I now see that to get essentially the same output as
search_src("has_cm")
 I can type
!grep -r  has_cm $SAGE_ROOT/src
and for search_def("has_cm"),
!grep -r "def has_cm" $SAGE_ROOT/src

I don't know whether python functions can call the ! things but I
think it would help users to keep search_src(s) as a shorthand for
!grep -r s $SAGE_ROOT/src and search_def(s) for search_src("def "+s).

John

>
>
> [0] https://xkcd.com/1172/

I'm a fan of xkcd, especially the ones that mention emacs customization!

>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "sage-devel" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/sage-devel/Q61rOkZ303M/unsubscribe.
> To unsubscribe from this group and all its topics, 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/824b0ba6-0743-cefe-3230-c2366ef02389%40orlitzky.com.

-- 
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/CAD0p0K5W0_xqOKXqBWJk%3Drk6gNzqe-h4-4_5tpsBWzz_McVmhQ%40mail.gmail.com.

Reply via email to