From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: emacs-devel@gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>,
Ryan B <public@ryanb.org>
Subject: Re: Making font-lock handle long lines better
Date: Tue, 15 May 2018 10:08:46 +0200 [thread overview]
Message-ID: <1526371726.2837572.1372427096.22315E49@webmail.messagingengine.com> (raw)
In-Reply-To: <CAM-tV-9=pYDHhezOKM40uwC5XMXLsqcOSdAt44UwHsKsi9DHvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
On Tue, May 15, 2018, at 2:05 AM, Noam Postavsky wrote:
> On 13 May 2018 at 15:44, Ryan B <public@ryanb.org> wrote:
>> for the record, i narrowed this down to the maven element of
>> `compilation-error-regexp-alist'. if i remove that element,
>> `compilation-mode' is fast on the minimal test case in
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25682 .
>
> Sounds like Bug#13369, although that report specifically mentions the> 'omake' element as the major culprit.
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13369
>
I know this isn't directly related to the original issue raised, and not
to sound awfully negative...
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.
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.
But seeing bugs like this, makes me ask some other questions:
- Are there any systems in place to follow up "solved" bugs which
doesn't result in commits?- Do we know how many such bugs there currently are?
- And what improvements could we make to Emacs if there was an
initiative to get all those issues properly closed?
--
Regards
Jostein Kjønigsen
jostein@kjonigsen.net 🍵 jostein@gmail.com
https://jostein.kjonigsen.net
[-- Attachment #2: Type: text/html, Size: 2930 bytes --]
next prev parent reply other threads:[~2018-05-15 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:44 Making font-lock handle long lines better Ryan B
2017-02-10 15:57 ` joakim
2017-02-10 16:24 ` Eli Zaretskii
2017-02-11 20:10 ` Wilfred Hughes
2017-02-11 20:28 ` Eli Zaretskii
2017-02-11 23:06 ` Anders Lindgren
2018-05-13 19:44 ` Ryan B
2018-05-15 0:05 ` Noam Postavsky
2018-05-15 8:08 ` Jostein Kjønigsen [this message]
2018-05-15 16:50 ` Eli Zaretskii
2018-05-15 18:32 ` Stefan Monnier
2017-02-11 22:06 ` Ryan B
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1526371726.2837572.1372427096.22315E49@webmail.messagingengine.com \
--to=jostein@secure.kjonigsen.net \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=npostavs@users.sourceforge.net \
--cc=public@ryanb.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.