Consider adding files created with "New File" in the file tree to working set

[njx]

I just realized that I hit this workflow glitch pretty often:

1. Create a new file in the file tree (because I want to put it in a particular location quickly, instead of using Save As) - file opens in editor but not in working set
2. Click on another file I want to copy initial contents from (since I want to get the copyright header, define boilerplate, etc. and delete out the content)
3. Copy the contents
4. Cmd-W to close the file

At this point I want to be back in the new file I created in step 1, but I'm not because we never added it to the working set. I wonder if it would make sense to automatically add new files created in the file tree to the working set, since it's very likely you're going to continue working with them instead of just leaving them empty.

[njx]

Edited to clarify that I'm talking about new files created in the file tree (we already add files from File > New to the working set obviously :))

[peterflynn]

This bugs me pretty frequently too -- I could swear I'd filed a bug on it a long time ago, but now I can't find it. (All I can find is the ancient bug #1028, which was fixed, so at some point long ago it apparently was working this way).

[dangoor]

I believe this would be a very small change.

[njx]

Cool, seems fixed.