about summary refs log tree commit diff stats
path: root/widgets/compose.go
Commit message (Expand)AuthorAgeFilesLines
* Use go-message implementation of GenerateMessageIDBen Burwell2019-07-041-2/+1
* Reopening mailcontent file to fix #166Stefan Rakel2019-06-271-1/+7
* Fix Cc & Bcc handling in repliesDrew DeVault2019-06-211-7/+7
* Execute the editor with the shellDrew DeVault2019-06-071-1/+1
* Use SetAddressList for From headerDrew DeVault2019-06-051-2/+10
* Enumerate Cc and Bcc lists in composerDrew DeVault2019-06-021-1/+20
* Implement :edit in compose screenDrew DeVault2019-05-261-27/+51
* Fix special characters in address.PersonalNameDrew DeVault2019-05-251-6/+9
* s/aerc2/aerc/gDrew DeVault2019-05-171-4/+4
* Fix date header on outgoing emailsDrew DeVault2019-05-171-1/+1
* Decode email when reading it for quotingDrew DeVault2019-05-161-0/+1
* Implement :reply -q and :reply -aDrew DeVault2019-05-161-0/+9
* Implement (basic form) of :replyDrew DeVault2019-05-161-3/+11
* Let caller pass in custom headers to composeDrew DeVault2019-05-161-6/+32
* Copy sent emails to the Sent folderDrew DeVault2019-05-151-1/+9
* Update tab name as subject changesDrew DeVault2019-05-141-0/+12
* Add $EDITOR, internal config for composeDrew DeVault2019-05-141-5/+12
* Add distinct keybindings for each compose viewDrew DeVault2019-05-141-0/+10
* Implement sending emails /o/Drew DeVault2019-05-141-18/+42
* Add :send-message, prepares & writes email to /tmpDrew DeVault2019-05-141-0/+79
* Spec out review message screenDrew DeVault2019-05-131-6/+58
* Populate "From" header from config for new emailsDrew DeVault2019-05-131-12/+20
* Implement :{next,prev}-field in compose viewDrew DeVault2019-05-121-1/+16
* Expand compose focus handling a bitDrew DeVault2019-05-121-19/+30
* Add initial compose widgetDrew DeVault2019-05-121-0/+122
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2025-02-20 07:58:22 +0000
>="image/x-icon" /> <meta charset="utf-8" /> </head> <body class="indent"> <h1><code>andrewyu.org</code> Mailing List Guidelines</h1> <p>The following guidelines apply to most <a href="https://mail.andrewyu.org/mailman/listinfo">public mailing lists on <code>andrewyu.org</code></a>. Different lists may have different specific guidelines.</p> <ul> <li> Be considerate of other subscribers on the mailing lists. </li> <li> Plain text, preferrably 72 characters per line. <br /> Many subscribers and maintainers read their mail on text-based mailers like mail(1), emacs, mutt, etc., and they often find HTML-formatted messages (or lines that stretch beyond 72 characters) unreadable. Many mailing lists strip messages of MIME content before sending them out to the rest of the list. If you don't use plain text, your messages will be reformatted. If they cannot be reformatted, they will be summarily rejected. Use attachments with care, they will be removed from messages on some lists. </li> <li> Include a useful Subject line. <br /> Messages with an empty Subject will get bounced to the list manager and will take longer to show up. Including a relevant Subject in the message will ensure that more people actually read what you've written. Also, avoid Subject lines with excessive uppercase and exclamations. "Help!" or "I can't get it to work!" are not useful subject lines. Do not change the subject line while on the same topic. You may know what it is regarding, the rest of us who get several hundred messages a day will have no idea. </li> <li> Trim your signature. <br /> Keep the signature lines at the bottom of your mail to a reasonable length. PGP signatures should be attachments rather than inline. </li> <li> Stay on topic. <br /> Please keep the subject of the post relevant to the topic of the mailing list. </li> <li> Include important information for questions. <br /> Don't waste everyone's time with a hopelessly incomplete question. No one other than you has the information needed to resolve your problem, it is better to provide more information than needed than not enough detail. </li> <li> Respect differences in opinion and philosophy. <br /> Intelligent people may look at the same set of facts and come to very different conclusions. Repeating the same points that didn't convince someone previously rarely changes their mind, and irritates all the other readers. </li> <li> No spam. </li> <li> Interweave quoted original messages with replies. <br /> Post inline, and trim quotes. This means that your replies are interspersed with the original mail, and any irrelevant content is removed (trimmed): <pre>From: A Subject: Re: S To: B CC: list B wrote: &gt; ... &gt; Do you think that this is correct? Yes, I believe so. &gt; How about iterating through the items and applying the function to each of them? Sounds good.</pre> </li> <li> Reply to the list. <br /> For most discussions that are not going wildly off-topic and still may be of interest to those in the list, CC the list so others can follow up. However, as it suggests, if things are going to be irrelevant to the list's topic, reply in private. </li> </ul> <div id="footer"> <hr /> <p><a href="/">Andrew Yu's Website</a></p> </div> </body> </html>