From: "Sébastien Gendre" <seb@k-7.ch>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: General discussions about Org-mode <emacs-orgmode@gnu.org>,
orgmode@tec.tecosaur.net
Subject: Re: Enhancing the HTML exporter: Create a new backend or contribute to the upstream
Date: Wed, 23 Oct 2024 07:32:48 +0200 [thread overview]
Message-ID: <8734kn1j0f.fsf@k-7.ch> (raw)
In-Reply-To: <87frqbel30.fsf@localhost> (Ihor Radchenko's message of "Sat, 07 Sep 2024 11:53:39 +0000")
[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]
Ihor Radchenko <yantar92@posteo.net> writes:
> Before I continue with my replies, I'd like to add one general comment.
>
> You are suggesting a number of new diverse features.
> Ideally, it is better to discuss and add them separately.
> Especially, when we move ahead and discuss the concrete implementations
> or patches.
>
> I will also provide some links to existing discussions on similar
> features. It is a good idea to continue those discussions, so that we do
> not spread things across the mailing list too much.
>
> Sébastien Gendre <seb@k-7.ch> writes:
It's a good idea.
I have created a first thread to discuss the local search engine here:
https://list.orgmode.org/87a5ev31ul.fsf@k-7.ch/T/#u
> Let me clarify.
> Unless an indexer is very simple, we do not really want it in Org - it
> will put a lot of extra load on maintainers.
>
> On the other side, we do not want to tie things to some project that
> may fade out in 10 years into the future.
>
> The way I see search engine support in Org mode is either:
>
> 1. Using some really established project that we can expect to last for
> many years.
>
> 2. Implementing pluggable search support where users can choose which
> indexer/searcher to use
>
> (2) will be the best.
>
> So, may you please search across available search engines and see what
> they have in common. Then, we can work out some infrastructure that is
> generic enough to plug a custom engine.
>
> Then, pagefind can be the default (it is MIT license - GPL compatible),
> unless someone proposes a better alternative.
I have replied to this part on my first reply to the thread about the
search engine, at "Remarks #1":
https://list.orgmode.org/878quf1ji0.fsf@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b
For the other parts, I have take notes of your replies and will reply on
the specific threads.
Thank you very much for all your replies. :)
Best regards
-------
Gendre Sébastien
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
prev parent reply other threads:[~2024-10-23 5:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 1:29 Enhancing the HTML exporter: Create a new backend or contribute to the upstream Sébastien Gendre
2024-08-28 1:52 ` Sébastien Gendre
2024-09-01 15:58 ` Ihor Radchenko
2024-09-02 5:09 ` Sébastien Gendre
2024-09-07 11:53 ` Ihor Radchenko
2024-09-08 14:46 ` Max Nikulin
2024-09-08 15:55 ` Max Nikulin
2024-09-08 18:36 ` Orm Finnendahl
2024-09-08 18:42 ` Ihor Radchenko
2024-09-08 19:25 ` Orm Finnendahl
2024-09-09 16:40 ` Ihor Radchenko
2024-10-23 5:40 ` Sébastien Gendre
2024-10-23 5:40 ` Sébastien Gendre
2024-10-23 5:39 ` Sébastien Gendre
2024-10-23 5:39 ` Sébastien Gendre
2024-10-23 5:34 ` Sébastien Gendre
2024-10-23 5:32 ` Sébastien Gendre [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734kn1j0f.fsf@k-7.ch \
--to=seb@k-7.ch \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@posteo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).