From: Boruch Baum <boruch_baum@gmx.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46364@debbugs.gnu.org
Subject: bug#46364: regression in lm-commentary
Date: Sun, 7 Feb 2021 13:55:02 -0500 [thread overview]
Message-ID: <20210207185502.6lx67ptuysg3nflu@E15-2016.optimum.net> (raw)
In-Reply-To: <87lfbzzpsm.fsf@gnus.org>
On 2021-02-07 19:38, Lars Ingebrigtsen wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
>
> > In emacs 26, lm-commentary functions fine.
> > In the emacs-snapshot that I'm using from ~2020-09, it does not
> > correctly indent sub headings.
> >
> > This was observed for the lisp file[1], as processed by MELPA[2], and
> > reproduced by me locally. I don't know what version MELPA is using.
>
> I'm not sure how Melpa is involved here?
I thought I was clear about that. They produced the problem. I gave you
links to the file, and the MELPA URL of the erroneous output, and the
URL of the github discussion.
> Is the problem that (lm-commentary "/that/file") doesn't return the
> correct result on some particular file?
Isn't that what I wrote? What was't clear about what I wrote? I'm
looking at it now and I don't see any ambiguity.
> If so, can you include the file here in the bug tracker, as well as
> instructions for how to reproduce the bug?
You know what, Lars, just forget it. Just forget I ever reported this
bug. Go ahead and close it. I'm not in the mood today for this. Let
someone else report it sometime in the future and deal with
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2021-02-07 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 14:01 bug#46364: regression in lm-commentary Boruch Baum
2021-02-07 18:38 ` Lars Ingebrigtsen
2021-02-07 18:55 ` Boruch Baum [this message]
2021-02-07 20:35 ` Basil L. Contovounesios
2021-02-08 0:19 ` Matt Armstrong
2021-02-08 6:39 ` Lars Ingebrigtsen
2021-02-08 18:59 ` Matt Armstrong
2021-02-08 20:51 ` Basil L. Contovounesios
2021-02-09 0:11 ` Matt Armstrong
2021-02-09 8:11 ` Lars Ingebrigtsen
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=20210207185502.6lx67ptuysg3nflu@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=46364@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).