[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10239: compilation-auto-jump-to-first-error vs. giant binary executa
|
From: |
Andreas Schwab |
|
Subject: |
bug#10239: compilation-auto-jump-to-first-error vs. giant binary executables |
|
Date: |
Sun, 29 Sep 2019 19:43:49 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
On Sep 29 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> diff --git a/lisp/progmodes/compile.el b/lisp/progmodes/compile.el
> index d80fef3103..a29dc5cc47 100644
> --- a/lisp/progmodes/compile.el
> +++ b/lisp/progmodes/compile.el
> @@ -58,6 +58,16 @@ compilation-window-height
> :type '(choice (const :tag "Default" nil)
> integer))
>
> +(defcustom compilation-transform-file-match-alist
> + '(("/bin/[a-z]*sh\\'" nil)
> + ("\\*+ \\[\\(Makefile\\)" "\\1"))
That doesn't make sense. "Makefile" can be anything.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."