[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#2048: Flymake Enhancement
From: |
Stefan Monnier |
Subject: |
bug#2048: Flymake Enhancement |
Date: |
Sun, 25 Jan 2009 21:05:53 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
severity 2048 wishlist
thanks
> lines. To remedy this, I introduced a buffer-local variable named
> flymake-split-output-pattern and modified the function
> flymake-split-output to use it when splitting the output into individual
> error/warning messages. The default value of
> flymake-split-output-pattern is "[\n\r]+"; this matches the value
> previously hard-coded in flymake-split-output. For bigloo, I added in
> my .emacs file a hook to bee-mode-hook to set the value
> flymake-split-ouput-pattern to "^[\r\n][\r\n]". This enabled flymake to
> display the full error/warning messages provided bigloo. The patch for
> this modification is attached. If there are any questions and or
> comments, I would appreciate hearing them.
I'd hope that flymake.el can be improved to match multi-line regexps
without having to tell it how to cut the output into chunks.
In any case, this change is too late for Emacs-23.1 which is in feature
freeze, but otherwise the goal is right. I remember someone else
needing/implementing support for multiline error messages in flymake.el
a while back.
Stefan