From: "Mattias Engdegård" <mattiase@acm.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 39595@debbugs.gnu.org
Subject: bug#39595: #39595: M-x compile still very line-length weak
Date: Fri, 14 Feb 2020 12:18:29 +0100 [thread overview]
Message-ID: <9D8A11CB-9ABE-4A66-87D0-2E445499B74F@acm.org> (raw)
In-Reply-To: <87wo8rjapu.8.fsf@jidanni.org>
> aaa:; perl -we 'print " " x 9999;' #finishes right away.
> bbb:; perl -we 'print "\n" x 9999;' #takes several seconds, even on the latest hardware.
(The comments seem to have been swapped around, but we get the idea.)
This is not a rare edge case. Long lines are not uncommon in compilation output, and a sluggish M-x compile reflects badly on Emacs since it is a commonly used function.
The main culprit seems to be 'omake' -- try removing it from compilation-error-regexp-alist. There is still an annoying delay; further investigation is needed. (For instance, 'msft' occurs twice; this must be a mistake.)
next prev parent reply other threads:[~2020-02-14 11:18 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 ` Mattias Engdegård [this message]
2020-02-14 16:27 ` bug#39595: #39595: " 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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9D8A11CB-9ABE-4A66-87D0-2E445499B74F@acm.org \
--to=mattiase@acm.org \
--cc=39595@debbugs.gnu.org \
--cc=jidanni@jidanni.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).