Sounds like a reasonable request, and Jody has a point as well.
I prioritize features for the software using a couple of measurements: (1) the size of the TD audience that will benefit from it; (2) how much of a benefit that audience will receive; (3) the amount of work required; (4) whether or not it fits into where I think the software should be going.
So usually I work on things that will help a large segment of the software's users and/or will greatly benefit an appreciable chunk of the users. But sometimes I will add features if they are relatively easy to design, implement, and test, even if they don't benefit a large portion of users. And some things I simply reject (or decide to include) based on my own judgment of whether or not I want it to be in the software. One might argue that that judgment may be right or wrong, but it still ends up being my decision.
I tend to side with Jody on this one in particular, because it would be more than just a small amount of work, and based on never having had this request or anything similar that I can recall, it probably wouldn't benefit a lot of users. But, it's still a good suggestion, and a good reason to post them here is to see if others agree with you and just hadn't ever asked for the feature, or maybe they'll like it and it's just never occurred to them to use the software to do it. Or maybe not.