You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not 100% sure if this issue is related to the Atom package or to the ccls itself.
I'm using gcc with its specific flags. I configured the ccls to use it (tried both .ccls and compile_commands.json) and it works fine in the case of indexing, hyperclicking etc.
However, the issue is that the "Linter part" seemly still uses clang and not gcc, which results in highlighting many "errors", that I know that do not appear at gcc.
I also tried to configure Linter to blacklist ccls or ide-ccls, but it does not work at the moment.
Ideally, I'd like to be able to configure the "Linter part" to use gcc too, which I did not figure out how to do it (I suppose that from Atom it is impossible to configure the --init option for the ccls).
Well, I'm not sure if completely abandoning clang is possible in ccls at all, but I would be glad if the "Linter part" could be, at least, just disabled in the package, so I can just keep on using linter-gcc package.
The text was updated successfully, but these errors were encountered:
Hi - sorry I haven't been using Atom in a while so haven't been following up here. As far as I understand ccls would still be using clang under the hood for linting since it's built on top of the clang framework, but folks over at the ccls project would have a better understanding there.
As for passing the --init option, that was added in #2. If a particular option is missing it would be possible to add it there. Unfortunately since I no longer use Atom I won't be able to test it. But feel free to fork the project/submit PRs.
I'm not 100% sure if this issue is related to the Atom package or to the
ccls
itself.I'm using
gcc
with its specific flags. I configured theccls
to use it (tried both.ccls
andcompile_commands.json
) and it works fine in the case of indexing, hyperclicking etc.However, the issue is that the "Linter part" seemly still uses
clang
and notgcc
, which results in highlighting many "errors", that I know that do not appear atgcc
.I also tried to configure Linter to blacklist
ccls
oride-ccls
, but it does not work at the moment.Ideally, I'd like to be able to configure the "Linter part" to use
gcc
too, which I did not figure out how to do it (I suppose that from Atom it is impossible to configure the--init
option for theccls
).Well, I'm not sure if completely abandoning
clang
is possible inccls
at all, but I would be glad if the "Linter part" could be, at least, just disabled in the package, so I can just keep on usinglinter-gcc
package.The text was updated successfully, but these errors were encountered: