unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: How to search on emacs-devel?
Date: Wed, 09 Mar 2022 07:44:30 -0800	[thread overview]
Message-ID: <87mthznna9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 877d93gsgp.fsf@gmail.com

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Tue, 08 Mar 2022 10:13:59 -0800, Eric Abrahamsen <eric@ericabrahamsen.net> said:
>     >> I sometimes use https://yhetil.org/emacs-devel/,
>     >> e.g. https://yhetil.org/emacs-devel/CACJP=3n854x2w0M-u9ba=e2zT=JUNyRfrqZT11co5_+Up56vMg@mail.gmail.com/
>
>     Eric> Oh! I'd read about public inbox, and then forgot about it again. I
>     Eric> wonder how hard it would be to write a Gnus search engine that used this
>     Eric> for search, then requested the actual message from Gmane...
>
> Would it be harder than downloading the emacs-devel archives locally
> and then just G-f'ing them? Works offline too :-)

I don't know! I've thought about the relative merits of various
approaches here. A remote search server has the advantage that you don't
need to update archives or install any search program. But local search
is faster and more flexible, and you don't occupy any else's resources.

I thought of distributing gmane search indexes via an elpa package --
rather, a package that downloads and updates indexes. Or a version of
'(nntp "news.gmane.io") that simply saves everything to disk, so you can
index it yourself. But if public inbox has some sort of API and doesn't
mind us hitting it, maybe that would be easiest?





  reply	other threads:[~2022-03-09 15:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 15:09 How to search on emacs-devel? dalanicolai
2022-03-08 15:17 ` dalanicolai
2022-03-08 15:57   ` andrés ramírez
2022-03-08 16:06     ` dalanicolai
2022-03-08 17:49 ` Philip Kaludercic
2022-03-08 18:13   ` Eric Abrahamsen
2022-03-09 13:34     ` Robert Pluim
2022-03-09 15:44       ` Eric Abrahamsen [this message]
2022-03-09 17:36       ` Stefan Monnier
2022-03-09 17:43         ` Andreas Schwab
2022-03-10 15:50       ` Felix Dietrich
2022-03-10 16:46         ` Felix Dietrich
2022-03-09 11:41   ` dalanicolai
  -- strict thread matches above, loose matches on Subject: below --
2022-03-09 18:51 Eric Abrahamsen
2022-03-09 18:59 ` Eric Abrahamsen
2022-03-09 19:24   ` Stefan Monnier
2022-03-09 19:49     ` Eric Abrahamsen
2022-03-09 21:46       ` Stefan Monnier
2022-03-09 22:01         ` Eric Abrahamsen
2022-03-09 22:12           ` Stefan Monnier
2022-03-09 22:23             ` Eric Abrahamsen
2022-03-10  5:49   ` Kyle Meyer
2022-03-10  6:51     ` Eli Zaretskii
2022-03-10 17:43       ` Eric Abrahamsen
2022-03-10 17:56         ` Eli Zaretskii
2022-03-10 18:12           ` Eric Abrahamsen
2022-03-10 17:54     ` Eric Abrahamsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mthznna9.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).