Dmitry Ignatovich

@boeningc You are welcome!

@robertlugg No, it is not possible with current version. But you can substitute whitespaces with tabs in your file globally: `s/ */\t/g` and use TSV syntax. If you want a...

OK, I think it would make sense to add more grammars, there is no point to wait for Microsoft/vscode#1800 First candidate is obviously "pipe-separated" files. I won't be able to...

@harvest316 Thanks, this is interesting! I don't want to add .DAT -> 'pipe' association on the extension level, but turns out there is a way to add this mapping manually...

@Lercher I didn't know about this feature, but I think it will give too many false positives: a lot of non-csv files can contain commas or semicolons in the first...

I've published updated version, the only change is that now Rainbow CSV supports pipe `|` separator. I probably should have done it long ago, but better late than never I...

Hello, @GrisPetitDragon , Thanks for feedback! It will be possible once content-based auto-detection is implemented. It is trivial to implement, but I need VSCode API call, which is currently missing,...

Good news: Microsoft/vscode#1800 is complete. I even took a part in writing the API implementation :sunglasses: So this allows to add auto-detection functionality and possibly more CSV dialects, since their...

I've just published version 0.7.0 which has content-based separator autodetection logic. The new functionality will work only with VSCode 1.28, for older VSCode versions there should be no change in...

@GrisPetitDragon you are welcome! Actually there is an issue with current implementation: separator autodetection will only work for "plaintext" files with unassigned language. i.e. if a table file has '.txt'...