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
Thanks for the suggestions. The Settings button on the CSV Lint window kind of makes sense, could be useful so I'll try to add it when I have time.
As for copying specific columns to the clipboard, technically it could be added but I don't quite understand what you would use that for exactly 🤔 Can you explain why you need this?
There is already a menu option Count unique values which does this functionality almost but not quite. It's kind of similar except it deduplicates the values of the column(s), the result is only the unique values.
If you want to copy separate column(s), the way I do it is Reformat it to TAB separated, then copy all ctrl+A ctrl+C and paste it into a new empty spreadsheet (Excel, LibreOffice Calc etc.), and from there you can copy any individual column. CSV Lint is mainly a quality control tool or dataset validator tool, so I don't quite see the use-case for a "Copy column(s)" function, can you clarify it?
As you explained, if user want to share/copy specific columns fom the master file. Its a direct and quick option instead of going via excel route, which is one more dependency.
If its too much work/will add additional overhead for the plug in, you can discard this request.
"If you want to copy separate column(s), the way I do it is Reformat it to TAB separated, then copy all ctrl+A ctrl+C and paste it into a new empty spreadsheet (Excel, LibreOffice Calc etc.), and from there you can copy any individual column."
Hi, can you please provide option to copy specific column data into clipboard in "CSV Lint Window"?
Similar feature is available here, but I mostly use CSV lint for my work. (https://github.com/daddel80/notepadpp-multireplace?tab=readme-ov-file#csv-processing-functions)
Also, a shortcut to settings window in "CSV Lint Window" will be helpful.
Thanks.
The text was updated successfully, but these errors were encountered: