From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Max Chernoff <mseven@telus.net>
Subject: Re: searching in the source browser
Date: Mon, 05 Sep 2022 15:53:43 -0600 [thread overview]
Message-ID: <d08029bc85146495c52f1ee288b3fc81373756cf.camel@telus.net> (raw)
In-Reply-To: <c5893bc4-d8ce-9d4d-8ed0-d1f731c622cf@fiee.net>
Hi Hraban,
> Am 05.09.22 um 21:07 schrieb Pablo Rodriguez via ntg-context:
> > has it to be the source browser?
> >
> > I mean, I use grep in Linux (MSYS2 in Windows [and brew.sh is available
> > for macOS]) and it works perfectly fine with ConTeXt.
> >
> > $ grep -irl fi[eë][eë] context
> > context/tex/texmf-context/tex/context/base/mkiv/char-def.lua
> > context/tex/texmf-modules/tex/context/third/lilypond/t-lilypond.tex
> >
> > Althought regular expressions are fine, I don’t know why "fi[eë]+"
> > doesn’t work in this case.
> >
> > Just in case it might help,
>
> Thank you – I found
>
> grep -R "regex" ~/context
>
> to be most easy.
>
> But I like the source browser with its syntax highlighting, and it’s a
> pity that the search is so limited.
I usually use the new GitHub "Code Search". This works pretty well,
although you need a (free) account to use it:
https://cs.github.com/contextgarden/context-mirror?q=%5Cstarttext
Sourcegraph should work pretty much the same way. I don't usually use
it, but it has the advantage of not requiring an account:
https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/contextgarden/context-mirror%24+%5Cstarttext&patternType=standard
Both of these have syntax highlighting and work with literal strings or
regexes.
-- Max
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-09-05 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 18:28 Henning Hraban Ramm via ntg-context
2022-09-05 18:59 ` Wolfgang Schuster via ntg-context
2022-09-05 20:50 ` Henning Hraban Ramm via ntg-context
2022-09-05 19:07 ` Pablo Rodriguez via ntg-context
2022-09-05 19:34 ` Hans Hagen via ntg-context
2022-09-05 20:46 ` Henning Hraban Ramm via ntg-context
2022-09-05 21:53 ` Max Chernoff via ntg-context [this message]
2022-09-06 6:41 ` Taco Hoekwater via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d08029bc85146495c52f1ee288b3fc81373756cf.camel@telus.net \
--to=ntg-context@ntg.nl \
--cc=mseven@telus.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).