emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Gendre" <seb@k-7.ch>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de>,
	emacs-orgmode@gnu.org
Subject: Re: Enhancing the HTML exporter: Create a new backend or contribute to the upstream
Date: Wed, 23 Oct 2024 07:40:34 +0200	[thread overview]
Message-ID: <874j53z8a5.fsf@k-7.ch> (raw)
In-Reply-To: <878qw0rd9s.fsf@localhost> (Ihor Radchenko's message of "Mon, 09 Sep 2024 16:40:47 +0000")

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

Hello,

I have replied to your message, and the previous one, on the new thread
dedicated to the search engine feature, at "Remarks #6":

https://list.orgmode.org/878quf1ji0.fsf@k-7.ch/T/#m2425dcfc7665e88aefcbd81800d2d83aef98cd5b

Best regards

-------
Gendre Sébastien


Ihor Radchenko <yantar92@posteo.net> writes:

> Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de> writes:
>
>>> It should probably work for single page as well. I do not see why
>>> not.
>>
>>  sure it works. I just question the raison d'etre, when single page
>> search is already integrated into webbrowsers. But as always there
>> will be people arguing that it is necessary to have a search bar with
>> pop up results integrated into the page and of course there is nothing
>> wrong with that. I use pagefind myself, but the site I'm working on
>> (built with the multipage exporter BTW) currently contains more than
>> 400 files where the browser search can't help.
>
> Agree. So, having search functionality probably makes more sense within
> ox-publish, where we may also run post-processing to generate search
> terms or whatever extra work is needed to make the indexer work.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2024-10-23  5:40 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 [this message]
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

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=874j53z8a5.fsf@k-7.ch \
    --to=seb@k-7.ch \
    --cc=emacs-orgmode@gnu.org \
    --cc=orm.finnendahl@selma.hfmdk-frankfurt.de \
    --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).