all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: outline-minor-mode: Did something change
Date: Fri, 12 Jan 2024 09:29:22 +0200	[thread overview]
Message-ID: <86bk9rnlst.fsf@mail.linkov.net> (raw)
In-Reply-To: <p91zfxb4yk3.fsf@google.com> (T. V. Raman's message of "Thu, 11 Jan 2024 08:36:28 -0800")

>>>> Using headers is the right idea an the regexp is a hack, but sadly
>>>> the entire Web is a hack that forgot the meaning of structure a long,
>>>> long time ago!
>>>
>>> Only think to add: could we have a half-way house solution that at least
>>> for a while uses both ie outline-level and outline-regexp?
>>
>> outline-regexp is too unreliable: in eww need not to mismatch HTML headers,
>> in emacs-lisp-mode not to match the open parenthesis in the docstring, etc.
>> For the same reason tree-sitter is preferable to regexp-based font-lock.
>
> I' not disagreeing with you; what I was pointing out is that the HTML
> Web rejected all notions of structured markup a long time ago, so hoping
> that structure alone will give us something useful remains  a dream --
> one  that I too dremt  a long time ago

Alas, the idea of the Semantic Web has failed, so to get useful information
from a Web page the remaining way is to resort to Web scraping using regexps.



      reply	other threads:[~2024-01-12  7:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  2:39 outline-minor-mode: Did something change T.V Raman
2024-01-08  7:12 ` Juri Linkov
2024-01-08 15:42   ` T.V Raman
2024-01-08 16:56 ` T.V Raman
2024-01-10  7:16   ` Juri Linkov
2024-01-10 15:26     ` T.V Raman
2024-01-10 18:09       ` T.V Raman
2024-01-11  7:03         ` Juri Linkov
2024-01-11 16:36           ` T.V Raman
2024-01-12  7:29             ` Juri Linkov [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

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

  git send-email \
    --in-reply-to=86bk9rnlst.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.