Ashar
Ashar
Making structured warning/error still requires parsing so that clicking on an error jumps cursor to error line. Turns out first step towards making it structured is the parse, but to...
> Check if the parser works with different locales. We can check if geany does it correctly. > We can have an option to use `-fdiagnostics-format=json`. Yes, we can perform...
@tuwuna Please take some time to provide a description for the issue. It will help others to understand and try to contribute to it.
Prior to CF tool 1.0 the syntax to submit to codeforces required us to parse `problemCode` and `ContestID` from url provided by competitive companion and pass it on to CF...
@allcontributors please add @jaysampartak for bugs
@salmakhaled74 #1050 is a Pull request that adds a new translation. It would be good if at least 2 people can translate together or someone can review after your translation...
@all-contributors please add @sonulohani for ideas
> Let me know if you agree with the suggestions. I could work on this feature. Yes, that will be a nice addition. How do you plan to achieve it?
"qcodeeditor" is a new label applies to issues that can be fixed if changes are required in QCodeEditor. You can easily filter on this label to see all issues/enhancement for...
"Check and Submit" should be inside the Action menu as submit button will be removed in #681, it still needs confirmation for problem ID and URL. The submission asks for...