clarify names of add and delete subcommands

[rberenguel]

Add/remove sounds more natural than add/delete, but I'm not sure if it is just to me. If I'm not the only one, I guess having remove to alias internally to delete would be helpful

[propensive]

I'm against having multiple alternative names for the same command (even if one is hidden), but I'm not against changing delete to remove or del.

But first, what do other people thing? Does anyone prefer delete to remove (i.e. the current behavior)?

[leifwickland]

I agree that remove is the natural complement to add, analogous to create/delete. "Add" and "remove" suggest membership.

However, reading the docs, it appears that perhaps you don't want membership.

[add] may be used to create new projects and modules respectively.

I'm tempted to offer a third opinion and say that it is add which should be changed to create and that delete is just fine. :-)

(Am I doing bikeshedding right?)

[propensive]

Yes, that's totally the correct way to do it. I hope some other bikeshedding experts will add (or create) some more suggestions. Anyway, I also wondered whether create would have been a better choice, so it's not a bad suggestion.

[ianp]

remove makes more sense to me, although personally I'd go with summon and banish 😈

[jeffrey-aguilera]

unadd

[gabro]

Embrace the bash way and use dda?

[tobias-johansson]

add/drop?

[marklister]

So in your talk you said something like "git like workflow"

Git's equivalent is probably rm

[propensive]

Ok, I'm going with add/remove. I'm not going to use rm, because it suggests (to me, at least) working with files.