all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 39595@debbugs.gnu.org, jidanni@jidanni.org, pogonyshev@gmail.com,
	monnier@iro.umontreal.ca
Subject: bug#39595: #39595: M-x compile still very line-length weak
Date: Sat, 15 Feb 2020 09:35:42 +0200	[thread overview]
Message-ID: <83k14onvzl.fsf@gnu.org> (raw)
In-Reply-To: <7A842DF4-BACB-4CB2-A9DD-40AA57CA8DF0@acm.org> (message from Mattias Engdegård on Fri, 14 Feb 2020 23:47:43 +0100)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 14 Feb 2020 23:47:43 +0100
> Cc: jidanni@jidanni.org, monnier@iro.umontreal.ca, pogonyshev@gmail.com,
>         39595@debbugs.gnu.org
> 
> > Is there some forum where the relevant people could be asked about
> > this?
> 
> Not sure where to go for that. The problem is really in Emacs's hacky implementation: when 'omake' is included in compilation-error-regexp-alist, many other regexps are rewritten in a way that makes them potentially slower. This is why it's not an ideal feature to have enabled by default.

I'm okay with disabling 'omake' if we have nowhere else to ask.

Thanks.





  reply	other threads:[~2020-02-15  7:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  5:51 bug#39595: M-x compile still very line-length weak 積丹尼 Dan Jacobson
2020-02-14 11:18 ` bug#39595: #39595: " Mattias Engdegård
2020-02-14 16:27   ` Mattias Engdegård
2020-02-14 17:00     ` Eli Zaretskii
2020-02-14 22:47       ` Mattias Engdegård
2020-02-15  7:35         ` Eli Zaretskii [this message]
2020-02-15 16:45           ` Mattias Engdegård
2020-02-16 12:15             ` Mattias Engdegård
2020-02-15  1:28 ` 積丹尼 Dan Jacobson
2020-02-15 13:57   ` Stefan Monnier
2020-02-16 15:37 ` 積丹尼 Dan Jacobson
2020-02-17 11:07   ` Mattias Engdegård

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=83k14onvzl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39595@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pogonyshev@gmail.com \
    /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.