Ah, I see. You want the leaf nodes to behave like actions do now, as far as your context lists are concerned, and the root nodes to behave like projects, even when the leaf and root are the same. That makes much more sense.
I'm with dhm in that I *like* being able to corral my single actions. Otherwise my project list would be terribly cluttered, and I would have to use fake projects to group things (which is maybe what the singleton lists are anyway, but the visual distinction helps me know they're fake and don't need planning).
If I am looking at my context lists and realize that something is a project, I really want a simple way to kick it back to the inbox so I can deal with it properly at an appropriate time (say, by removing its context?). But I don't have that yet. If I need to do something about it immediately, I can jump to planning mode. You're right that it's fairly painful. That's why I really want the "kick to inbox" functionality.
I'm with dhm in that I *like* being able to corral my single actions. Otherwise my project list would be terribly cluttered, and I would have to use fake projects to group things (which is maybe what the singleton lists are anyway, but the visual distinction helps me know they're fake and don't need planning).
If I am looking at my context lists and realize that something is a project, I really want a simple way to kick it back to the inbox so I can deal with it properly at an appropriate time (say, by removing its context?). But I don't have that yet. If I need to do something about it immediately, I can jump to planning mode. You're right that it's fairly painful. That's why I really want the "kick to inbox" functionality.