Skip to content
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

[Feature Request] Additional file path pattern for C++ (MSVC), & Output Autoscroll #86

Open
Logix-Dev opened this issue Mar 1, 2021 · 3 comments

Comments

@Logix-Dev
Copy link

Hi!
This wonderful Atom package is running my C++ build script (a batch file calling MSVC) to build a project.

However, I'm unable to click on errors in the output console (panel), due to MSVC's output formatting for filenames not following any of the available RegEx(?) patterns. MSVC's output for errors is formatted like so (for example):
C:\Path\To\File\SomeFile.cpp(43): error message
where 43 is the line number.

Additionally, I have the output going to a Panel, however said panel does not auto scroll (even with scroll lock disabled). Not sure if I'm missing something obvious or this is just a feature that isn't implemented, but what I do know is that it would be really useful, since the build script outputs a lot of text and it's the text right at the end that's the most important.

@morassman
Copy link
Owner

morassman commented Mar 14, 2021

Sorry for the late reply. I've determined that there is actually a bug that is causing the wrong regular expression to be used on Windows, which prevents the path from being detected. I'll fix this soon and then that path should be detectable.

@morassman
Copy link
Owner

I've deployed the fix. The path should now be detected.

To recognize the line number in your example you can configure the pattern : (path)\((line)\)
Notice how the round brackets around the line number are escaped with \( and \) so that they can be detected as well.

image

Then in the command's configuration, move that pattern to the top of the list :

image

@morassman
Copy link
Owner

Hi @Logix-Dev . Did the latest version fix the issue for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants