From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71353@debbugs.gnu.org, Troy Brown <brownts@troybrown.dev>,
Felician Nemeth <felician.nemeth@gmail.com>
Subject: bug#71353: [PATCH] eglot--format-markup doesn't support MarkedString code-blocks
Date: Sat, 15 Jun 2024 10:37:48 +0100 [thread overview]
Message-ID: <CALDnm53HCcEO=+7vX=_HaGRGEaRyzYgJhXBShs0g4zS0gYQV-w@mail.gmail.com> (raw)
In-Reply-To: <86tthuvd3z.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Can you please resend the patch for inspection?
On Sat, Jun 15, 2024, 09:12 Eli Zaretskii <eliz@gnu.org> wrote:
> > 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?
>
[-- Attachment #2: Type: text/html, Size: 1394 bytes --]
next prev parent reply other threads:[~2024-06-15 9:37 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
2024-06-15 9:37 ` João Távora [this message]
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='CALDnm53HCcEO=+7vX=_HaGRGEaRyzYgJhXBShs0g4zS0gYQV-w@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=71353@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=eliz@gnu.org \
--cc=felician.nemeth@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.