From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Making font-lock handle long lines better
Date: Tue, 15 May 2018 19:50:28 +0300
Message-ID: <831seclv6z.fsf@gnu.org>
References: <CA+caGh_JN9FRi71VjUTwvYBKKygG-KuGGoe3GBgjthPRh00nRg@mail.gmail.com>
	<83wpcy2eun.fsf@gnu.org>
	<CAFXAjY4ED1L=T1zB-v=U-_DWbkOaO8+4cDidejBunS-RC3D7zQ@mail.gmail.com>
	<83lgtc3215.fsf@gnu.org>
	<CABr8ebY_0sUTmv_unYQSdZ4VjrCf3KNH3nnE2SW_sd-xEdU9+A@mail.gmail.com>
	<CA+caGh8DpwKKn3xMQFE+pqbHOVjWPf=Oc1ZJ5x==wCzEts28Aw@mail.gmail.com>
	<CAM-tV-9=pYDHhezOKM40uwC5XMXLsqcOSdAt44UwHsKsi9DHvA@mail.gmail.com>
	<1526371726.2837572.1372427096.22315E49@webmail.messagingengine.com>
Reply-To: Eli Zaretskii <eliz@gnu.org>
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Trace: blaine.gmane.org 1526403256 6835 195.159.176.226 (15 May 2018 16:54:16 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Tue, 15 May 2018 16:54:16 +0000 (UTC)
Cc: npostavs@users.sourceforge.net, public@ryanb.org, emacs-devel@gnu.org
To: jostein@kjonigsen.net
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 15 18:54:11 2018
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([208.118.235.17])
	by blaine.gmane.org with esmtp (Exim 4.84_2)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1fIdDH-0001f2-4S
	for ged-emacs-devel@m.gmane.org; Tue, 15 May 2018 18:54:11 +0200
Original-Received: from localhost ([::1]:48044 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1fIdFO-0001Ki-8I
	for ged-emacs-devel@m.gmane.org; Tue, 15 May 2018 12:56:22 -0400
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35975)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eliz@gnu.org>) id 1fId9w-0006DV-3I
	for emacs-devel@gnu.org; Tue, 15 May 2018 12:50:46 -0400
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eliz@gnu.org>) id 1fId9s-00046h-R5
	for emacs-devel@gnu.org; Tue, 15 May 2018 12:50:44 -0400
Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36904)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@gnu.org>)
	id 1fId9a-0003q1-0X; Tue, 15 May 2018 12:50:22 -0400
Original-Received: from [176.228.60.248] (port=2446 helo=home-c4e4a596f7)
	by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
	(Exim 4.82) (envelope-from <eliz@gnu.org>)
	id 1fId9Z-00034j-Ej; Tue, 15 May 2018 12:50:21 -0400
In-reply-to: <1526371726.2837572.1372427096.22315E49@webmail.messagingengine.com>
	(message from Jostein =?utf-8?Q?Kj=C3=B8nigsen?= on Tue, 15 May 2018
	10:08:46 +0200)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-devel/>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.emacs.devel:225313
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/225313>

> From: Jostein Kjønigsen <jostein@secure.kjonigsen.net>
> Date: Tue, 15 May 2018 10:08:46 +0200
> 
> But if I understand this correctly this is a bug which was filed and debugged in 2013, half a decade ago, with a
> known fix, but the bug is still in the Emacs codebase. 
> 
> Why? Because whoever filed and diagnosed the bug in the first place can't/won't signed copyright
> assignment papers.

That's not my reading of the discussion in that bug.  The copyright
assignment issue is only tangentially related to the bug, it was
mentioned wrt a package shown in the discussion, but that package is
not the solution to the problem.

As the solution to the problem it was proposed to remove support for
omake or disable it by default.  Upon re-reading the discussion, I
didn't perceive any consensus regarding that proposal.  In any case,
deletion of some lines doesn't require any copyright assignment.

> Now that the problem is solved, can't someone else just make the edit, write the patch, and make this terrible
> bug go away? It's a one-line diff after all. We do provide exceptions for such small patches after all.

If there's an agreement to do that, it should be easy.  But I'm not
sure there as an agreement.

> - Are there any systems in place to follow up "solved" bugs which doesn't result in commits?

This is a volunteer project.  Our "system" in place involves a few
motivated individuals, like Noam and a few others, who routinely
review old bug reports.  If you are asking whether we have people
whose assigned job is to do that, then no.

> - Do we know how many such bugs there currently are?

Please define "such bugs".  The bug tracker supports queries, so given
a specification, we could probably provide an answer.

> - And what improvements could we make to Emacs if there was an initiative to get all those issues properly
> closed?

I hope that more people volunteer to take care of bug reports, both
old and new.  Would you like to work on that?

Thanks.