all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Felician Nemeth <felician.nemeth@gmail.com>
Cc: brownts@troybrown.dev, 71353@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#71353: [PATCH] eglot--format-markup doesn't support MarkedString code-blocks
Date: Sat, 15 Jun 2024 11:12:16 +0300	[thread overview]
Message-ID: <86tthuvd3z.fsf@gnu.org> (raw)
In-Reply-To: <878qzk8pr1.fsf@betli.tmit.bme.hu> (message from Felician Nemeth on Tue, 04 Jun 2024 21:36:02 +0200)

> Cc: 71353@debbugs.gnu.org,
>  João Távora <joaotavora@gmail.com>
> From: Felician Nemeth <felician.nemeth@gmail.com>
> Date: Tue, 04 Jun 2024 21:36:02 +0200
> 
> Troy Brown <brownts@troybrown.dev> writes:
> 
> > I've created a new patch which creates a fenced code block and uses
> > gfm-view-mode,
> 
> I have not tried it, but it looks good.  Maybe a comment would help to
> understand that the new part handles the case when the MarkedString is a
> code-block.
> 
> At any rate, I CC'd the maintainer of Eglot.

João, any comments or suggestions?





  reply	other threads:[~2024-06-15  8:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  2:51 bug#71353: [PATCH] eglot--format-markup doesn't support MarkedString code-blocks Troy Brown
2024-06-04  5:41 ` Felician Nemeth
2024-06-04 10:01   ` Troy Brown
2024-06-04 11:21     ` Felician Nemeth
2024-06-04 12:37       ` Troy Brown
2024-06-04 19:36         ` Felician Nemeth
2024-06-15  8:12           ` Eli Zaretskii [this message]
2024-06-15  9:37             ` João Távora
2024-06-15 12:36               ` Eli Zaretskii
2024-06-18 13:39                 ` João Távora
2024-07-01  3:28                   ` Troy Brown
2024-07-06  8:41                     ` Eli Zaretskii
2024-07-06  9:18                       ` João Távora

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=86tthuvd3z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71353@debbugs.gnu.org \
    --cc=brownts@troybrown.dev \
    --cc=felician.nemeth@gmail.com \
    --cc=joaotavora@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 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.