Open Bug 253017 Opened 17 years ago Updated 9 years ago
enh: A way to "Insert file
..." into the compose window
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 It could be useful (at least for me...) to be able to insert a file into the message body while composing a new message. Sylpheed (my previous client) has this feature, and I used it many times. Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** Bug 253700 has been marked as a duplicate of this bug. ***
OS -> All
OS: Linux → All
Other clients do this as well. It is the only real problem many users have with thunderbird. I know several who use tbird for everyday mail but then revert to something else (ie /bin/mail) to send patches to their open source projects where the developers get up in arms about attachments. So we should be able to insert plain text files into plain text messages (currently the insert menu disappears in plain text composition) and we should not perform any text conversion (ie tabs to spaces), at least not when in plain text mode.
This is a perfect candidate for an extension, if someone's so inclined.
I have to send lots of prewritten messages (*.txt) and I used to insert them within 2 secondes in MS Outlook. If possible how can I do this with ThunderBird? Else I guess, I have to go back using Outlook.
There's another bug about patches, but for most other cases (like prewritten messages) I don't see why copy-paste wouldn't work?
(In reply to comment #6) > There's another bug about patches, but for most other cases (like prewritten > messages) I don't see why copy-paste wouldn't work? Hmm. Copy and paste is surely less comfortable (more steps) than inserting (text) files directly. I think this would be a nice feature to have - if we can insert images, why not text (which should be much easier codewise...)?. On the other hand, looking at other bugs that are far more disturbing and probably more frequent than this one, this is very unlikely to get developers' attention. So I tend to agree with comment 4: nice thing to do in an extension. So the right resolution for this bug would probably be "Wontfix: needs extension". Unfortunately, due to bug 522873 which got blasted before the idea even sank into developers minds, we have no way of resolving a bug that shows both a) we will not fix this ourselves (wontfix) AND b) this is a nice idea, and we would gladly take an addon So I propose this bug be marked as NEW (to appreciate the goodness of the idea). And add your vote and comment to bug 522873 if you agree that "Wontfix: needs extension" would be the better resolution.
Per comment 7 and in lack of objections, I'll mark this NEW to get it off the "Unconfirmed" radar. Feel free to disagree.
You need to log in before you can comment on or make changes to this bug.