Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grand command-name unification #23

Open
linuxcaffe opened this issue Nov 26, 2013 · 0 comments
Open

grand command-name unification #23

linuxcaffe opened this issue Nov 26, 2013 · 0 comments
Assignees

Comments

@linuxcaffe
Copy link

One of the things I like about vim-taskwarrior, is that it has adopted a command-name convention so that all of it's commands start with ":TW.." and that makes the commands a) easier to remember, and b) makes all of the related, applicable commands instantly available with tab-completion. :TW-tab and you see before you the whole set of related command options, it's a beautiful thing :)

Now vimwiki-tasks has a smaller-but-growing set of commands, and in experimenting with them, I sometimes forget exactly what commands exists for a given context, and what they're called exactly.

So I'd like to put forth a potentially controversial idea that vimwiki-tasks and vim-taskwarrior could both use that same command prefix: TW! The two applications are both "taskwarrior-in-vim" and there is plenty of "namespace" to go around. This could be done in a complimentary way.

:TWCmd (TaskCmd)
:TWInsert (InsertTasks)
:TWModify (TaskModify)
:TWNote (OpenTaskNotes)
:TWUpdate (UpdateTaskLists)
:TWCopyUuid (CopyTaskUUID)
:TWDisplayUuid (DisplayTaskUUID)
:TWCopyId (CopyTaskID)
:TWDisplayId (DisplayTaskID)

(have a look at the command-wish-list, embedded as comments, at the bottom of this file; https://github.com/farseer90718/vim-taskwarrior/blob/master/plugin/taskwarrior.vim, many of the suggested (wished for) commands will never be incorporated in vim-taskwarrior, but several are more perfectly suited to vimwiki-tasks)

The upshot, if we (you ;-) were to adopt this command-name convention, is that whether using vimwiki-tasks or vim-tw, or back-and-forth between the two, all taskwarrior-related commands would be at hand. most just available for that filetype, some local to the buffer, and a few global commands from each, and you could see them all, instantly, with tab-completion.

Even if (especially if) the :TWAnnotate command were used by both programs, for similar intent, using entirely different code, there's actually no conflict, because each is acting locally, on it's own filtetype. Global-commands would have to be unique, but there aren't that many of them. Otherwise, it's just re-enforcement of the same behavior, the path of least surprise, and the overlap simplifies things. All you really have to know then is :TW-tab.

@ghost ghost assigned teranex Dec 1, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants