all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: cpardo@imayhem.com, 71909@debbugs.gnu.org, visuweshm@gmail.com
Subject: bug#71909: 30.0.60;
Date: Sun, 20 Oct 2024 16:51:34 +0300	[thread overview]
Message-ID: <86sesqj315.fsf@gnu.org> (raw)
In-Reply-To: <87bjzerkeq.fsf@localhost> (message from Ihor Radchenko on Sun, 20 Oct 2024 13:09:01 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, cpardo@imayhem.com, 71909@debbugs.gnu.org
> Date: Sun, 20 Oct 2024 13:09:01 +0000
> 
> Visuwesh <visuweshm@gmail.com> writes:
> 
> >>> where text/html is the most useful.
> >>
> >> no, the most useful is Rich Text, but Emacs cannot yet yank that.
> >
> > Possibly.  But we could at least "hijack" shr to convert text/html to
> > string with text properties on it, or make it insert markup elements.
> > I've done the later as a personal hack and it works fairly well.
> 
> May we utilize tree-sitter?
> Having an AST, it should not be too hard to convert it into something
> Emacs can understand.

You mean, someone has written a tree-sitter grammar for Rich Text?

If not, what do you mean by "utilize tree-sitter" in this context?





  reply	other threads:[~2024-10-20 13:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <865xtnhyn6.fsf@foxmail.com>
2024-10-05 12:28 ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-05 12:33   ` Eli Zaretskii
2024-10-05 12:42     ` Eli Zaretskii
2024-10-05 17:14       ` Cecilio Pardo
2024-10-05 19:31         ` Eli Zaretskii
2024-10-05 21:24           ` Cecilio Pardo
2024-10-06  5:59             ` Eli Zaretskii
     [not found]               ` <87ldz1h5s4.fsf@gmail.com>
2024-10-06 11:50                 ` Eli Zaretskii
2024-10-06 12:15                   ` Visuwesh
2024-10-20 13:09                     ` Ihor Radchenko
2024-10-20 13:51                       ` Eli Zaretskii [this message]
2024-10-20 13:59                         ` Ihor Radchenko
2024-10-20 14:22                           ` Eli Zaretskii
2024-10-20 15:02                             ` Ihor Radchenko
2024-10-20 15:34                               ` Eli Zaretskii
2024-10-20 15:57                                 ` Ihor Radchenko
2024-10-20 17:50                                   ` Visuwesh
2024-10-20 17:59                                     ` Eli Zaretskii
2024-10-20 17:16                       ` Cecilio Pardo
2024-10-20 17:58                         ` Eli Zaretskii
2024-10-07 10:24               ` Cecilio Pardo
2024-10-07 11:58                 ` Eli Zaretskii
2024-10-09 12:52                   ` Cecilio Pardo
2024-10-09 13:40                     ` Eli Zaretskii
2024-10-23 23:13                       ` bug#71909: 30.0.60; yank-media on MS-Windows Cecilio Pardo
2024-10-24  7:18                         ` Eli Zaretskii
2024-10-24  8:39                           ` Cecilio Pardo
2024-10-24  9:38                             ` Eli Zaretskii
2024-10-24 10:43                               ` Cecilio Pardo
2024-10-10 10:04     ` bug#71909: 30.0.60; Cecilio Pardo
2024-10-10 10:49       ` Eli Zaretskii
2024-10-28 21:46   ` Cecilio Pardo
2024-10-29 14:25     ` Eli Zaretskii
2024-10-29 14:55       ` Eli Zaretskii
2024-10-30  9:05       ` Cecilio Pardo
2024-10-30 15:35         ` Eli Zaretskii
2024-10-30 15:49           ` Cecilio Pardo

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=86sesqj315.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71909@debbugs.gnu.org \
    --cc=cpardo@imayhem.com \
    --cc=visuweshm@gmail.com \
    --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 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.