List of commands to be implemented about commands HOT 9 OPEN

These should only be checked off when they fully match ST3's functionality.

from commands.

I prefer the system we already have, though, which is to separate each command into its own issue, so we can have discussions related to them independently of other commands.

from commands.

I want a place where we can see and say, xyz commands are left. If we keep one issue for each commands, that's fine, because we'll discuss the technical details there, I want the status details of the command list. Since the goal is to implement all ST3 commands, doesn't it make sense to have a place which tells you which is missing?

from commands.

I want a place where we can see and say, xyz commands are left.

This can be resolved by creating a command label and filtering by it.

I'm on the fence, but it doesn't hurt to have both, at least until they get out of sync :).

from commands.

at least until they get out of sync :).

We'll have to make sure we sync it!

How can I create labels? I tried creating, but it doesn't allow me to.

from commands.

You can't without admin rights. I've created one.

from commands.

I've created a report command in limetext/sublime it informs the percentage of sublime text api support and missing functionalities. We need something like that for commands.

from commands.

That's a good idea. Just comparing the registered commands to a list would be a good first step.

from commands.

The report command is perfect, that way we don't have to manually look into anything.

from commands.