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
Hi,
I am the author of a csv plugin for VimScreencast (Look for the :ArrangeCol command) and I am considering to use csvlook to render nice column view of the csv file. Currently I am doing this manually using some regexp magic and while this works okay, it can cause problems for huge csv, that cause Vim to allocate so much memory that it will get killed. So I thought about alternatives.
In order to make use of csvlook, I'd suggest a new optional argument, that skips generating the ascii frames around the table and just columnizes the output, but keeps the delimiter so the user can simply edit a nice excel view of the csv file.
Would that be possible?
(Note: My plugin also allows to arrange each column individually, but for now, it would be okay for me, if this is not yet implemented.)
The text was updated successfully, but these errors were encountered:
The implementation of this functionality is moving out of the csvkit repository into its new dependency agate (#515). This is the file that would need to be modified. You may re-open your issue on agate.
Hi,
I am the author of a csv plugin for Vim Screencast (Look for the :ArrangeCol command) and I am considering to use csvlook to render nice column view of the csv file. Currently I am doing this manually using some regexp magic and while this works okay, it can cause problems for huge csv, that cause Vim to allocate so much memory that it will get killed. So I thought about alternatives.
In order to make use of csvlook, I'd suggest a new optional argument, that skips generating the ascii frames around the table and just columnizes the output, but keeps the delimiter so the user can simply edit a nice excel view of the csv file.
Would that be possible?
(Note: My plugin also allows to arrange each column individually, but for now, it would be okay for me, if this is not yet implemented.)
The text was updated successfully, but these errors were encountered: