unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Visuwesh <visuweshm@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 71909@debbugs.gnu.org, cpardo@imayhem.com
Subject: bug#71909: 30.0.60;
Date: Sun, 20 Oct 2024 13:09:01 +0000	[thread overview]
Message-ID: <87bjzerkeq.fsf@localhost> (raw)
In-Reply-To: <877calh1fs.fsf@gmail.com>

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.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





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

Thread overview: 45+ 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 [this message]
2024-10-20 13:51                       ` Eli Zaretskii
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
2024-11-02  0:23           ` Cecilio Pardo
2024-11-02 10:44             ` Eli Zaretskii
2024-11-02 11:24               ` Cecilio Pardo
2024-11-02 12:09                 ` Eli Zaretskii
2024-11-02 20:30                   ` Cecilio Pardo
2024-11-03 13:14                     ` Eli Zaretskii
2024-11-04 22:19                       ` Cecilio Pardo
2024-11-05 12:30                         ` Eli Zaretskii

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=87bjzerkeq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=71909@debbugs.gnu.org \
    --cc=cpardo@imayhem.com \
    --cc=eliz@gnu.org \
    --cc=visuweshm@gmail.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 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).