GNU bug report logs - #56393
Actually fix the long lines display bug

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: gregory <at> heytings.org
Cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
Subject: bug#56393: Actually fix the long lines display bug
Date: Thu, 21 Jul 2022 12:42:18 +0300

> Cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
> Date: Mon, 18 Jul 2022 21:56:44 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Date: Mon, 18 Jul 2022 18:26:22 +0000
> > From: Gregory Heytings <gregory <at> heytings.org>
> > cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
> > 
> > 
> > >> Thanks, but couldn't we use the existing BUF_CHARS_MODIFF for that?
> > >
> > > I'll have a look, thanks.
> > >
> > 
> > And the answer is no.  (I tried to use it, but did not remember the reason 
> > why it was not usable in this context while writing my previous reply.) 
> > I don't know what BUF_CHARS_MODIFF records
> 
> What BUF_CHARS_MODIFF records is documented in the doc string of
> buffer-chars-modified-tick.
> 
> > but it is for example == 2 before and after C-x i dictionary.json
> > RET.
> 
> It's a bug, plain and simple.

Should now be fixed on the master branch.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.