Husam Hebaishi
Husam Hebaishi
Just wanted to pitch in - I would love to extend the existing set_breakpoint API to take a custom filename and line number. This would be extremely useful in C++...
The reason atom behaves in this way is to avoid edge cases where you have multiple projects open and linter-gcc can't work out which settings to use for which file...
Edit: the first line should read: the reason linter-gcc behaves in this way not atom
Nice work man. I think a lot of what you've done can be integrated into linter gcc. What do you think about that?
@Arcanemagus Unfortunately, I have not used atom in a long time, and so I am no longer motivated to maintain this package. I shall transfer it over to the @AtomLinter...
Thanks for raising the issue. I've just had a look at your fix, and the solution is simple - add the localized strings to ```.gcc-flags.json```, as optional parameters. If they're...
Yes I see that now. The code in ```config.js``` needs to change to read the localised strings from ```.gcc-flags.json```. Will make the change in the next release. I need to...
This is how linter-gcc works - by compiling your source file. To remove the generated object file file, simply add ```-o /dev/null``` to your command line options for Linux and...
The problem is that if your ```compile-commands.json``` is in your project folder, your path should be relative to the project root. If you have a build folder called ```build-atom``` in...
This issue has already been discussed. Atom does not impose any restriction on the Project folder that a user may open. This means you can open a folder as a...