Disable CSV commands when syntax is not CSV

Question

Disable CSV commands when syntax is not CSV

Closed this issue 10 years ago · 6 comments

Try to implement is_enabled(<args>) and is_visible(<args>) is your commands

Answer 1 · 2015-01-26T20:43:09.000Z

Thanks for the suggestion, I'll look into implementing these.

Answer 2 · 2015-04-02T02:10:05.000Z

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.

Answer 3 · 2015-04-02T02:11:14.000Z

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".

Answer 4 · 2015-04-02T02:12:55.000Z

I understand. It kinda make sense to me a well. I'm gonna close this issue.

Answer 5 · 2015-04-02T02:14:10.000Z

Thanks! I'll revisit if I develop this heuristic ability further in the future.

Answer 6 · 2018-12-04T20:21:37.000Z

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.