From: Nathan Eagleson <nate@nateeag.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 16820@debbugs.gnu.org
Subject: bug#16820: 24.3; nxml comment block indentation issue
Date: Thu, 22 Oct 2020 22:43:16 -0400 [thread overview]
Message-ID: <CA+vbweYJJWeMrq+31MVeOCgW7t8tK7rFOJKrZOmZo-2OrfLe4Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmpv9EXKQL91BWyurnsZXg9aqn0rBYH=kpPpO-UnMbkcA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Sure thing. I'm sorry for completely missing your first request for info.
On Tue, Oct 20, 2020 at 12:03 PM Stefan Kangas <stefan@marxist.se> wrote:
> reopen 16820
> tags 16820 confirmed
> thanks
>
> Nathan Eagleson <nate@nateeag.com> writes:
>
> > Sorry, I missed your original request.
> >
> > This seems like a bug to me because multi-paragraph comment bodies are
> > usually indented to align with the comment start token.
> >
> > If you strip trailing whitespace on save, this behavior results in bad
> > comment indentation, something like:
> >
> > <!-- First line of comment is here. It may go on for
> > several lines in a format something like you'd expect.
> >
> > After the blank line, the comment is outdented relative to the
> > comment start/end markers.
> >
> > -->
> >
> > This is all from distant memory, so apologies if I'm describing it
> > incorrectly.
>
> Oh, right. Yes, that indeed does seem like a bug. Reopening.
>
> Thanks for writing back.
>
[-- Attachment #2: Type: text/html, Size: 1490 bytes --]
prev parent reply other threads:[~2020-10-23 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 4:44 bug#16820: 24.3; nxml comment block indentation issue Nate Eagleson
2020-08-12 22:01 ` Stefan Kangas
2020-10-01 12:12 ` Stefan Kangas
2020-10-06 3:09 ` Nathan Eagleson
2020-10-20 16:03 ` Stefan Kangas
2020-10-23 2:43 ` Nathan Eagleson [this message]
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=CA+vbweYJJWeMrq+31MVeOCgW7t8tK7rFOJKrZOmZo-2OrfLe4Q@mail.gmail.com \
--to=nate@nateeag.com \
--cc=16820@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).