tower@AI.MIT.EDU (Leonard H. Tower Jr.) (10/11/90)
Date: 10 Oct 90 21:42:41 GMT From: hagerman@o.gp.cs.cmu.edu (John Hagerman) Organization: Carnegie Mellon University Sender: help-gnu-emacs-request@prep.ai.mit.edu P.S. So is this now the correct group in which to advance for discussion suggested improvements to GNU Emacs? If a consensus is reached, how should the suggestion be forwarded to the developer? -- hagerman@ece.cmu.edu If you have a simple suggestion for an improvement, just send it to bug-gnu-emacs@prep.ai.mit.edu (aka newsgroup gnu.emacs.bug). It will help if you also include working code. Code proves your idea out and will increase the chance that your idea will be adopted sooner. Be careful about free-ranging discussions. If the volume on this list gets too high, people (too often the most qualified to help) will stop reading it. If you feel an idea will need a lot of discussion, it would be best to ask people to e-mail you their thoughts, and conduct the discussion via e-mail outside this list. In effect, setting up a short-term temporary mailing list. When the group has come to a consensus, send a report into bug-gnu-emacs. If the idea changes enough to need input from more people, you can post a summary of what's happened, and ask if anyone else wants to join in via e-mail outside this list. thanx -len (aka help-gnu-emacs-request@prep.ai.mit.edu) The charter (or purpose) of the list is: ---------------------------------------------------------------------- * help-gnu-emacs-request@prep.ai.mit.edu to subscribe to help-gnu-emacs ** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs) ** Send contributions to: help-gnu-emacs@prep.ai.mit.edu This list is the place for users and installers of GNU Emacs to ask for help. Please send bug reports to bug-gnu-emacs instead of posting them here. Since help-gnu-emacs a very large list, send it only those items that are seriously important to many people. If source or patches that were previously posted or a simple fix is requested in help-gnu-emacs, please mail it to the requester. Do NOT repost it. If you also want something that is requested, send mail to the requester asking him to forward it to you. This kind of traffic is best handled by e-mail, not a broadcast medium that reaches thousands of sites. This list is also gated one way to USENET's newsgroup comp.emacs (once known as net.emacs). This one-way gating is done for users whose sites get comp.emacs, but not gnu.emacs.help. Users at non-USENET sites may receive all articles from comp.emacs by making their request to: unix-emacs-request@bbn.com If Emacs crashes, or if you build Emacs following the standard procedure on a system which Emacs is supposed to work on (see etc/MACHINES) and it does not work at all, or if an editing command does not behave as it is documented to behave, this is a bug. Don't send bug reports to help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to bug-gnu-emacs instead. * General Information about help-* lists These lists (and their newsgroups) exist for anyone to ask questions about the GNU software that the list deals with. The lists are read by people who are willing to take the time to help other users. * General Information about all lists Please keep each message under 45,000 characters. Some mailers bounch messages that are longer than this. Most of the time, when you reply to a message sent to a list, the reply should not go to the list. But most mail reading programs supply, by default, all the recipients of the original as recipients of the reply. Make a point of deleting the list address from the header when it does not belong. This prevents bothering all readers of a list, and reduces network congestion. ---------------------------------------------------------------------- thanx -len