Closed aziz closed 9 years ago
Thanks for the suggestion, I'll look into implementing these.
Thinking about this some more, I'd like to extend the ability of the plugin to operate on tables in non-CSV files. For example I'd like to be able to use the expression evaluation and column lineup features in tables or CSV data embedded in Markdown files.
So if I wrote these callbacks they would have to do some heuristic matching, like "is there more than one column parseable from the text the cursor is in", as opposed to just "is this a .csv file".
I understand. It kinda make sense to me a well. I'm gonna close this issue.
Thanks! I'll revisit if I develop this heuristic ability further in the future.
Have you been able to figure out the heuristic?
I think think that the best thing to do is to only enable the commands when the file is either csv or markdown. This way, we won't clutter the sub menu with commands that don't make sense in a specific context.
Try to implement
is_enabled(<args>)
andis_visible(<args>)
is your commands