-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
for the wish list: log4j and log4j2 #3990
Comments
Can you please elaborate further and provide an example of the types of file you're looking to be detected by Linguist. AFAICT, log4j and and the newer log4j2 is logging API that was originally written in Java but usable and now implemented in other languages. Accordingly, the detection would be dependent on the implementation language and not log4j and log4j2 specifically. If you're referring to the resulting log files, Linguist won't get support for log file highlighting as that's beyond the scope of the project. |
here is an example: TheCoder4eu/BootsFaces-OSP#903 (comment) Yes, indeed, I wanted to add chosen log messages from the log file. If this is out of your project's scope, that's bad, but I can understand that this might be too heavy to be solved. |
Thanks for the explanation. Yup, this is definitely beyond the scope of Linguist. Linguist detects programming languages and pulls in third party syntax highlighting grammars to do the highlighting of code files in repositories. Log files would also be considered data by Linguist so wouldn't be included in the repo stats. The codeblocks like the one you've referenced are controlled by https://github.com/github/markup not Linguist, so if you want colourful logs in codeblocks, that would be the best place to log your request. As this issue doesn't pertain to Linguist, I'm closing this issue. |
Didn't find log4j or log4j2 in the list of possible code syntax languages. I'm not involved in development and cannot give you anything, but I think logfile results will be used in issues very often. Therefore, this extension would be very welcome.
The text was updated successfully, but these errors were encountered: