Usually these files are open to be read, not written, and will most likely have different rules than the ones configured for the project with lazy. That results in warnings that are worse than useless - that actually distract from the act of reading somebody else's source code.
Discuss: how does this influence statistics? If we don't even send the file to analysis then it won't appear at all in lazy but that means that some (future) statistics like "time spent in a file" will be incomplete. On the other hand if we do send it, then we have to make lazy decide to nix the final output and send empty (while still keeping track of the statics). The question is then who is supposed to decide when something is ignored. And to me it seems that it's logical, in our paradigm, to have lazy make all such decisions rather than editor packages. @neboysa ?
Usually these files are open to be read, not written, and will most likely have different rules than the ones configured for the project with lazy. That results in warnings that are worse than useless - that actually distract from the act of reading somebody else's source code.
Discuss: how does this influence statistics? If we don't even send the file to analysis then it won't appear at all in lazy but that means that some (future) statistics like "time spent in a file" will be incomplete. On the other hand if we do send it, then we have to make lazy decide to nix the final output and send empty (while still keeping track of the statics). The question is then who is supposed to decide when something is ignored. And to me it seems that it's logical, in our paradigm, to have lazy make all such decisions rather than editor packages. @neboysa ?