-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect parsing of compilation-mode buffers #452
Labels
Comments
Just to be clear, made this issue just to get feedback before starting to implement the fix. |
Sorry for the late reply. You're right:
Open a pr and I'll merge your fix, thanks! |
wildwestrom
added a commit
to wildwestrom/dotfiles-archlinux
that referenced
this issue
Aug 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to syl20bnr/spacemacs#15643
Description
The wrong parts of a
compilation-mode
buffer are parsed for certain messages.This isn't just aesthetics. The part highlighted in red is supposed to be the file name. The part highlighted in blue is supposed to be the location in the file.
When I click on the file name, it thinks the red portion is a file, and therefore can't find it, because the actual file is
(dirname/filename\.ext):\d+
not(dirname/filename\.ext:\d+)
.Reproduction guide 🪲
M-x compilation-mode
Observed behaviour:
Here's an example of what I see:
Image here:
Notice that highlighting starts at black at
at
then red atsrc/main.rs:81
then black at:
then blue at14
. When I click on the first or second highlighted files, it tries to navigate tofilename:linenumber
then go to the column-number.On a minimal configuration of GNU Emacs, I see this:
This indicates that something in spacemacs enhances
compilation-mode
.I have no idea what exactly does it or how to search for it.A minimal config of spacemacs will yield the same result, until the rust layer is added.
I also found information dealing with
compilation-mode
in rust-compile.el therefore I assume this bug is in this package.Expected behaviour:
Same thing as above, except the text should be highlighted as follows.
Start red highlight at
src/main.rs
then black at:
then blue after the first colon and navigate to the correct file and go to the correct line number.The text was updated successfully, but these errors were encountered: