all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 69647@debbugs.gnu.org
Subject: bug#69647: [PATCH 1/2] Delete trailing whitespace when formatting LSP documentation
Date: Fri, 8 Mar 2024 20:41:48 +0000	[thread overview]
Message-ID: <CALDnm51eY6O6n0x96vE9XL8pLqbZ1azCE+h4z_x2BAcovX5Z=g@mail.gmail.com> (raw)
In-Reply-To: <87cys4enc4.fsf@posteo.net>

On Fri, Mar 8, 2024 at 3:49 PM Philip Kaludercic <philipk@posteo.net> wrote:
>
> Tags: patch
>
> LSP servers like clangd generate trailing whitespace, that when rendered
> as markdown causes parts of the buffer to be underlined.  Unless there
> is a reason for this, I'd suggest helping out by deleting trailing
> whitespace before continuing to process the documentation.

Go ahead and push. But be warned I've been bitten by bugs when doing what
I thought were innocent changes to this function, so keep an eye out.

Ideally though the formatting (including these fixups) should be done
entirely by
entities other than Eglot.  I think markdown.el has something for that trailing
whitespace.  Anyway I don't have time for that, so go ahead and push.

João





  reply	other threads:[~2024-03-08 20:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 15:48 bug#69647: [PATCH 1/2] Delete trailing whitespace when formatting LSP documentation Philip Kaludercic
2024-03-08 20:41 ` João Távora [this message]
2024-03-08 20:54 ` Jim Porter
2024-03-08 21:02   ` João Távora
2024-03-08 21:36     ` Jim Porter
2024-03-09  3:08       ` Jim Porter
2024-03-09  9:02         ` Philip Kaludercic
2024-03-09 18:28           ` Jim Porter
2024-03-09 18:46             ` Philip Kaludercic
2024-03-11  3:50             ` Jim Porter
2024-03-22  8:49               ` Philip Kaludercic

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='CALDnm51eY6O6n0x96vE9XL8pLqbZ1azCE+h4z_x2BAcovX5Z=g@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=69647@debbugs.gnu.org \
    --cc=philipk@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.