bug#46400: [BISECTED] Sporadically breaking newline-indentation in c-mode

[Alan Mackenzie]

Hello again, Konstantin.

On Thu, Feb 18, 2021 at 11:21:50 +0000, Alan Mackenzie wrote:
> On Thu, Feb 18, 2021 at 00:59:08 +0300, Konstantin Kharlamov wrote:
> > Hey! Sorry: I'm replying to the wrong email because it seems I stopped
> > receiving notifications for the report since the last time I sent an
> > email here. I didn't even know there was a discussion ongoing till I
> > occasionally looked through the web interface ☺ The web-interface
> > doesn't allow to reply a specific comment, so I had to reply to an
> > arbitrary email, last one I got in my mailbox. Sorry. (on a side-note,
> > Idk what happened to notifications. I looked through spam and other
> > folders, tried using built-in search on my email-provider in case some
> > filter put them into a random folder, but emails are nowhere to be
> > seen. Looks like I just wasn't getting any notifications).

> I kept getting rejections from you mail server (something to do with my
> ISP's server not sending a STARTTLS operator), so in the end I stopped
> adding your address to the To: or Cc: headers.

Apologies: I got your email address confused with another one beginning
with 'k'.  Your address works just fine, and I never deliberately
omitted it from a Cc:.

> It might well be I messed something up when I merged this bug with the
> other one.  I've not done merging of bugs very often.

> Sorry you didn't get the posts from debbugs.gnu.org.

> > Alan Mackenzie wrote:

> > > A pleasure!  I intend to commit the patch below in a few days time,
> > > if I don't hear back from anybody that it's giving trouble.  This
> > > patch fixes the bug when applied to that commit from December
> > > (9022df70270243f211c54ccd66800320148b8434).  It should apply cleanly
> > > to master.

> > Oh, this is amazing! I'll give the patch a try as well. I assume though
> > there will be nothing to report (well, other than "Thank you for fixing
> > the bug" 😉), but if I happen to find some other problem, I'll make
> > sure to drop an email either here or to a new report :)

> Thank you, indeed!  I haven't committed the patch, yet, and I'll leave
> off a few days yet.  It's surprising just how often asking people to
> check patches for their bugs gets a reply that things aren't properly
> fixed.

I have now committed the patch to all relevant places, and I'm going to
close bug #45375 (which has been merged with bug #46400) next.

-- 
Alan Mackenzie (Nuremberg, Germany).