Enric Meinhardt

The code in this repo produces a point cloud from a single stereo pair (or triplet). There is no logic here for dealing with large series of images, choosing the...

Thanks @oleg-alexandrov, while this may be formally offtopic, your interventions are always very welcome to us! To add to oleg's excellent answer, you may want to look also at https://github.com/centreborelli/sat-bundleadjust....

Closely related, there could be an option also for removing the useless lines ending with "= {};" and "= [];". That would make it even more grepable!

> They're not useless. They may the output correct JSON. Sure, but sometimes you don't care about that. The same option could remove the semicolons, these "empty" lines, and even...

> quoting all of them But wouldn't this make the output *less* greppable in general? I'd rather have all keys without quotes, regardless of whether they are identifiers or not.

> That would violate "The output of `gron` is valid JavaScript" Sure, and because of this reason the simplified output should not be the default behavior of gron. Still, there...

> What if a property name includes the delimiter sequence? Then the output would be slightly ambiguous, but still easily grepable.

Ideally, the comments should be in-band, as a plain file under the version control (that appears in the git repository). Looking at https://github.com/overleaf/overleaf/issues/552#issuecomment-887043176 , it is clear that this file...

> Has anyone found any workarounds to export comments with a pdf/ .tex file for version control while this feature is not available? Not even a workaround, but in my...