|
0
|
1
|
|
|
2 XEmacs Electronic Mailing Lists. Last Modified: 3-Feb-95.
|
|
|
3
|
|
|
4 XEmacs has its own mailing list and newsgroup which are distinct from
|
|
|
5 the FSF GNU Emacs mailing lists and newsgroups. The mailing list is:
|
|
|
6
|
|
|
7 xemacs@xemacs.org For reporting all bugs in XEmacs, including bugs
|
|
|
8 in the compilation and installation procedures.
|
|
|
9 Also for all random questions and conversation
|
|
|
10 about XEmacs.
|
|
|
11
|
|
|
12 This mailing list is bidirectionally gatewayed into the USENET newsgroup
|
|
|
13 comp.emacs.xemacs.
|
|
|
14
|
|
|
15 To be added or removed from this mailing list, send mail to
|
|
|
16 xemacs-request@xemacs.org (If it is possible for you to read the
|
|
|
17 messages via the newsgroup, we would prefer that; the fewer people there
|
|
|
18 are on the mailing list, the less trouble it is to maintain.)
|
|
|
19
|
|
|
20 Please do NOT send messages about problems with XEmacs to the FSF GNU
|
|
|
21 Emacs newsgroups and mailing lists (listed below) unless you are sure
|
|
|
22 that the problem you are reporting is a problem with both versions of
|
|
|
23 GNU Emacs. People who aren't subscribed to the XEmacs mailing list most
|
|
|
24 likely are not interested in hearing about problems with it.
|
|
|
25
|
|
|
26 The XEmacs mailing list is archived at ftp.xemacs.org in the directory
|
|
|
27 /pub/mlists/.
|
|
|
28
|
|
|
29 IMPORTANT IMPORTANT IMPORTANT:
|
|
|
30
|
|
|
31 Aside from the names of the mailing lists and newsgroups corresponding
|
|
|
32 to this version of Emacs, the guidelines enumerated below still apply.
|
|
|
33 Please read them before sending a message.
|
|
|
34
|
|
|
35 -----------------------------------------------------------------------
|
|
|
36
|
|
|
37 GNU Project Electronic Mailing Lists. Last Updated 23 Feb 94
|
|
|
38
|
|
|
39 Please report improvements to: gnu@prep.ai.mit.edu
|
|
|
40
|
|
|
41 * GNU mailing lists are also distributed as USENET news groups
|
|
|
42
|
|
|
43 The mailing lists are gated both ways with the gnu.all newsgroups at
|
|
|
44 ohio-state.edu. The one-to-one correspondence is indicated below. If
|
|
|
45 you don't know if your site is on USENET, ask your system administrator.
|
|
|
46 If you are a USENET site and don't get the gnu.all newsgroups, please
|
|
|
47 ask your USENET administrator to get them. If he has your feeds ask
|
|
|
48 their feeds, you should win. And everyone else wins: newsgroups make
|
|
|
49 better use of the limited bandwidth of the computer networks and your
|
|
|
50 home machine than mailing list traffic; and staying off the mailing
|
|
|
51 lists make better use of the people who maintain the lists and the
|
|
|
52 machines that the GNU people working with rms use (i.e. we have more
|
|
|
53 time to produce code!!). Thanx.
|
|
|
54
|
|
|
55 * Getting the mailing lists directly
|
|
|
56
|
|
|
57 If several users at your site or local network want to read a list and
|
|
|
58 you aren't a USENET site, Project GNU would prefer that you would set up
|
|
|
59 one address that redistributes locally. This reduces overhead on our
|
|
|
60 people and machines, your gateway machine, and the network(s) used to
|
|
|
61 transport the mail from us to you.
|
|
|
62
|
|
|
63 * How to subscribe to and report bugs in mailing lists
|
|
|
64
|
|
|
65 Send messages ABOUT these lists, such as reports of mail problems, or
|
|
|
66 requests to be added or removed, to help-gnu-emacs-request (or
|
|
|
67 info-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (or
|
|
|
68 info-gnu, etc.). These <LIST_NAME>-request addresses go only to the
|
|
|
69 people who can do something about your requests or problems, and thus
|
|
|
70 avoids disturbing everyone else.
|
|
|
71
|
|
|
72 Note that all GNU mailing lists are maintained by volunteers. They get
|
|
|
73 behind occasionally. Wait at least 3 or 4 days before asking again.
|
|
|
74 Thanks!
|
|
|
75
|
|
|
76 Many of the GNU mailing lists are very large and are received by many
|
|
|
77 people. Please don't send them anything that is not seriously important
|
|
|
78 to all their readers. All GNU mailing lists are unmoderated, mail
|
|
|
79 reflectors, except info-gnu, info-gnu-emacs, info-gcc, info-g++,
|
|
|
80 info-gnu-fortran, info-gnu-utils, info-gnu-chess and info-gnu-shogi.
|
|
|
81
|
|
|
82 All addresses below are in internet format. Consult the mail guru for
|
|
|
83 your computer to figure out address syntaxes from other networks. From
|
|
|
84 UUCP machines:
|
|
|
85 ..!ucbvax!prep.ai.mit.edu!ADDRESS
|
|
|
86 ..!uunet!prep.ai.mit.edu!ADDRESS
|
|
|
87
|
|
|
88 If a message you mail to a list is returned from a MAILER-DAEMON (often
|
|
|
89 with the line:
|
|
|
90 ----- Transcript of session follows -----
|
|
|
91 don't resend the message to the list. All this return means is that
|
|
|
92 your original message failed to reach a few addresses on the list. Such
|
|
|
93 messages are NEVER a reason to resend a piece of mail a 2nd time. This
|
|
|
94 just bothers all (less the few delivery failures (which will probably
|
|
|
95 just fail again!)) of the readers of the list with a message they have
|
|
|
96 already seen. It also wastes computer and network resources.
|
|
|
97
|
|
|
98 It is appropriate to send these to the -request address for a list, and
|
|
|
99 ask them to check the problem out.
|
|
|
100
|
|
|
101 * Send Specific Requests for Information to: gnu@prep.ai.mit.edu
|
|
|
102
|
|
|
103 Specific requests for information about obtaining GNU software, or GNU
|
|
|
104 activities in Cambridge and elsewhere can be directed to:
|
|
|
105 gnu@prep.ai.mit.edu
|
|
|
106
|
|
|
107 * General Information about all lists
|
|
|
108
|
|
|
109 Please keep each message under 25,000 characters. Some mailers bounce
|
|
|
110 messages that are longer than this. If your message is long, it is
|
|
|
111 generally better to send a message offering to make the large file
|
|
|
112 available to only those people who want it (e.g. mailing it to people
|
|
|
113 who ask, or putting it up for FTP). In the case of gnu.emacs.sources,
|
|
|
114 somewhat larger postings (up to 10 parts of no more than 25,000
|
|
|
115 characters each) are acceptable (assuming they are likely to be of
|
|
|
116 interest to a reasonable number of people); if it is larger than that
|
|
|
117 have it added to archive.cis.ohio-state.edu (the GNU Emacs Lisp ftp and
|
|
|
118 uucp archive on and announce) its location there. Good bug reports are
|
|
|
119 short. See section '* General Information about bug-* lists and ...'
|
|
|
120 for further details.
|
|
|
121
|
|
|
122 Most of the time, when you reply to a message sent to a list, the reply
|
|
|
123 should not go to the list. But most mail reading programs supply, by
|
|
|
124 default, all the recipients of the original as recipients of the reply.
|
|
|
125 Make a point of deleting the list address from the header when it does
|
|
|
126 not belong. This prevents bothering all readers of a list, and reduces
|
|
|
127 network congestion.
|
|
|
128
|
|
|
129 The GNU mailing lists and newsgroups, like the GNU project itself, exist
|
|
|
130 to promote the freedom to share software. So don't use these lists to
|
|
|
131 promote or recommend non-free software. (Using them to post ordering
|
|
|
132 information is the ultimate faux pas.) If there is no free program to
|
|
|
133 do a certain task, then somebody should write one!
|
|
|
134
|
|
|
135 * General Information about info-* lists
|
|
|
136
|
|
|
137 These lists and their newsgroups are meant for important announcements.
|
|
|
138 Since the GNU project uses software development as a means for social
|
|
|
139 change, the announcements may be technical or political.
|
|
|
140
|
|
|
141 Most GNU projects info-* lists (and their corresponding gnu.*.announce
|
|
|
142 newsgroups) are moderated to keep their content significant and
|
|
|
143 relevant. If you have a bug to report, send it to the bug-* list. If
|
|
|
144 you need help on something else and the help-* list exists, ask it.
|
|
|
145
|
|
|
146 See section '* General Information about all lists'.
|
|
|
147
|
|
|
148 * General Information about help-* lists
|
|
|
149
|
|
|
150 These lists (and their newsgroups) exist for anyone to ask questions
|
|
|
151 about the GNU software that the list deals with. The lists are read by
|
|
|
152 people who are willing to take the time to help other users.
|
|
|
153
|
|
|
154 When you answer the questions that people ask on the help-* lists, keep
|
|
|
155 in mind that you shouldn't answer by promoting a proprietary program as
|
|
|
156 a solution. The only real solutions are the ones all the readers can
|
|
|
157 share.
|
|
|
158
|
|
|
159 If a program crashes, or if you build it following the standard
|
|
|
160 procedure on a system on which it is supposed to work and it does not
|
|
|
161 work at all, or if an command does not behave as it is documented to
|
|
|
162 behave, this is a bug. Don't send bug reports to a help-* list; mail
|
|
|
163 them to the bug-* list instead.
|
|
|
164
|
|
|
165 See section '* General Information about all lists'.
|
|
|
166
|
|
|
167 * General Information about bug-* lists and reporting program bugs
|
|
|
168
|
|
|
169 If you think something is a bug in a program, it might be one; or, it
|
|
|
170 might be a misunderstanding or even a feature. Before beginning to
|
|
|
171 report bugs, please read the section ``Reporting Emacs Bugs'' toward the
|
|
|
172 end of the GNU Emacs reference manual (or node Emacs/Bugs in Emacs's
|
|
|
173 built-in Info system) for a discussion of how and when to send in bug
|
|
|
174 reports. For GNU programs other than GNU Emacs, also consult their
|
|
|
175 documentation for their bug reporting procedures. Always include the
|
|
|
176 version number of the GNU program, as well as the operating system and
|
|
|
177 machine the program was ran on (if the program doesn't have a version
|
|
|
178 number, send the date of the latest entry in the file ChangeLog). For
|
|
|
179 GNU Emacs bugs, type "M-x emacs-version". A debugger backtrace of any
|
|
|
180 core dump, can also be useful. Be careful to separate out hypothesis
|
|
|
181 from fact! For bugs in GNU Emacs lisp, set variable debug-on-error to
|
|
|
182 t, and re-enter the command(s) that cause the error message; Emacs will
|
|
|
183 pop up a debug buffer if something is wrong; please include a copy of
|
|
|
184 the buffer in your bug report. Please also try to make your bug report
|
|
|
185 as short as possible; distill the problem to as few lines of code and/or
|
|
|
186 input as possible. GNU maintainers give priority to the shortest, high
|
|
|
187 quality bug reports.
|
|
|
188
|
|
|
189 Please don't send in a patch without a test case to illustrate the
|
|
|
190 problem the patch is supposed to fix. Sometimes the patches aren't
|
|
|
191 correct or aren't the best way to do the job, and without a test case
|
|
|
192 there is no way to debug an alternate fix.
|
|
|
193
|
|
|
194 The purpose of reporting a bug is to enable the bug to be fixed for the
|
|
|
195 sake of the whole community of users. You may or may not receive a
|
|
|
196 response; the maintainers will send one if that helps them find or
|
|
|
197 verify a fix. Most GNU maintainers are volunteers and all are
|
|
|
198 overworked; they don't have time to help individuals and still fix the
|
|
|
199 bugs and make the improvements that everyone wants. If you want help
|
|
|
200 for yourself in particular, you may have to hire someone. The GNU
|
|
|
201 project maintains a list of people providing such services. It is
|
|
|
202 distributed with GNU Emacs in file etc/SERVICE, and can be requested
|
|
|
203 from gnu@prep.ai.mit.edu.
|
|
|
204
|
|
|
205 Anything addressed to the implementors and maintainers of a GNU program
|
|
|
206 via a bug-* list, should NOT be sent to the corresponding info-* or
|
|
|
207 help-* list.
|
|
|
208
|
|
|
209 Please DON'T post your bug reports on the gnu.*.bug newsgroups! Mail
|
|
|
210 them to bug-*@prep instead! At first sight, it seems to make no
|
|
|
211 difference: anything sent to one will be propagated to the other; but:
|
|
|
212 - if you post on the newsgroup, the information about how to
|
|
|
213 reach you is lost in the message that goes on the mailing list. It
|
|
|
214 can be very important to know how to reach you, if there is anything
|
|
|
215 in the bug report that we don't understand;
|
|
|
216 - bug reports reach the GNU maintainers quickest when they are
|
|
|
217 sent to the bug-* mailing list submittal address;
|
|
|
218 - mail is much more reliable then netnews; and
|
|
|
219 - if the internet mailers can't get your bug report delivered,
|
|
|
220 they almost always send you an error message, so you can find another
|
|
|
221 way to get the bug report in. When netnews fails to get your message
|
|
|
222 delivered to the maintainers, you'll never know about it and the
|
|
|
223 maintainers will never see the bug report.
|
|
|
224
|
|
|
225 And please DON'T post your GNU bug reports to comp.* or other gnu.*
|
|
|
226 newsgroups, they never make it to the GNU maintainers at all. Please
|
|
|
227 mail them to bug-*@prep instead!
|
|
|
228
|
|
|
229 See section '* General Information about all lists'.
|
|
|
230
|
|
|
231 * info-gnu-request@prep.ai.mit.edu to subscribe to info-gnu
|
|
|
232 ** gnUSENET newsgroup: gnu.announce
|
|
|
233 ** Send announcements to: info-gnu@prep.ai.mit.edu
|
|
|
234
|
|
|
235 This list distributes progress reports on the GNU Project. It is also
|
|
|
236 used by the GNU Project to ask people for various kinds of help. It is
|
|
|
237 NOT for general discussion.
|
|
|
238
|
|
|
239 The list is filtered to remove items meant for info-gnu-request, that
|
|
|
240 can be answered by the moderator without bothering the list, or should
|
|
|
241 have been sent to another list.
|
|
|
242
|
|
|
243 See section '* General Information about info-* lists'.
|
|
|
244
|
|
|
245 * gnu-misc-discuss-request@prep.ai.mit.edu to subscribe to gnu-misc-discuss
|
|
|
246 ** gnUSENET newsgroup: gnu.misc.discuss
|
|
|
247 ** Send contributions to: gnu-misc-discuss@prep.ai.mit.edu
|
|
|
248
|
|
|
249 This list is for serious discussion of freed software, the GNU
|
|
|
250 Project, the GNU Manifesto and their implications. It's THE place for
|
|
|
251 discussion that is not appropriate in the other GNU mailing lists and
|
|
|
252 gnUSENET newsgroups.
|
|
|
253
|
|
|
254 Flaming is out of place. Tit-for-tat is not welcome. Repetition
|
|
|
255 should not occur.
|
|
|
256
|
|
|
257 Good READING and writing are expected. Before posting, wait a while,
|
|
|
258 cool off, and think.
|
|
|
259
|
|
|
260 Don't use this group for complaints about GNU software!
|
|
|
261 The maintainers don't read this group; they won't see your complaint.
|
|
|
262 Use the appropriate bug-reporting mailing list instead, so that people
|
|
|
263 who can do something about the problem will see it.
|
|
|
264
|
|
|
265 Don't trust pronouncements made on gnu-misc-discuss about what GNU is,
|
|
|
266 what FSF position is, what the GNU General Public License is, etc.,
|
|
|
267 unless they are made by someone you know is well connected with GNU and
|
|
|
268 are sure the message is not forged.
|
|
|
269
|
|
|
270 USENET and gnUSENET readers are expected to have read ALL the articles
|
|
|
271 in news.announce.newusers before posting. If news.announce.newusers is
|
|
|
272 empty at your site, wait (the articles are posted monthly), your posting
|
|
|
273 isn't that urgent! Readers on the Internet can anonymous ftp these
|
|
|
274 articles from wsmr-simtel20.army.mil under directory
|
|
|
275 PD2:<UNIX-C.USENET>.
|
|
|
276
|
|
|
277 Someone from the Free Software Foundation will attempt to follow this
|
|
|
278 group as time and volume permits.
|
|
|
279
|
|
|
280 Remember, "GNUs Not Unix" and "gnUSENET is Not USENET". We have
|
|
|
281 higher standards!
|
|
|
282
|
|
|
283 Note that sending technical questions about specific GNU software to
|
|
|
284 gnu-misc-discuss is likely to be less useful than sending them to the
|
|
|
285 appropriate mailing list or gnUSENET newsgroup, since more technical
|
|
|
286 people read those.
|
|
|
287
|
|
|
288 * hurd-ann-request@prep.ai.mit.edu to subscribe to hurd-ann
|
|
|
289 ** gnUSENET newsgroup: gnu.hurd.announce
|
|
|
290 ** Send announcements to: hurd-ann@prep.ai.mit.edu
|
|
|
291
|
|
|
292 This list distributes progress reports on the GNU Hurd. It is also to
|
|
|
293 ask people for various kinds of help on the Hurd. It is NOT for general
|
|
|
294 discussion.
|
|
|
295
|
|
|
296 The list is filtered to remove items meant for hurd-ann-request, that
|
|
|
297 can be answered by the moderator without bothering the list, or should
|
|
|
298 have been sent to another list.
|
|
|
299
|
|
|
300 See section '* General Information about info-* lists'.
|
|
|
301
|
|
|
302 * bug-gnu-emacs-request@prep.ai.mit.edu to subscribe to bug-gnu-emacs
|
|
|
303 ** gnUSENET newsgroup: gnu.emacs.bug
|
|
|
304 ** Gnu Emacs bug reports to: bug-gnu-emacs@prep.ai.mit.edu
|
|
|
305
|
|
|
306 This list distributes, to the active maintainers of GNU Emacs, bug
|
|
|
307 reports and fixes for, and suggestions for improvements in GNU Emacs.
|
|
|
308
|
|
|
309 Send bugs in the GNU Emacs Lisp reference manual to:
|
|
|
310 lisp-manual-bugs@prep.ai.mit.edu
|
|
|
311
|
|
|
312 lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.
|
|
|
313 It's just a bug-reporting address.
|
|
|
314
|
|
|
315 Subscribers to bug-gnu-emacs get all info-gnu-emacs messages.
|
|
|
316
|
|
|
317 See section '* General Information about bug-* lists and reporting
|
|
|
318 program bugs'.
|
|
|
319
|
|
|
320 * gnu-emacs-sources-request@prep.ai.mit.edu to subscribe to gnu-emacs-sources
|
|
|
321 ** gnUSENET newsgroup: gnu.emacs.sources
|
|
|
322 ** Gnu Emacs source code to: gnu-emacs-sources@prep.ai.mit.edu
|
|
|
323
|
|
|
324 This list/newsgroup will be for the posting, by their authors, of lisp
|
|
|
325 and C sources and patches that improve GNU Emacs. Its contents will
|
|
|
326 be reviewed by FSF for inclusion in future releases of GNU Emacs.
|
|
|
327
|
|
|
328 Please do NOT discuss or request source code here. Use
|
|
|
329 help-gnu-emacs/gnu.emacs.help for those purposes. This allows the
|
|
|
330 automatic archiving of sources posted to this list/newsgroup.
|
|
|
331
|
|
|
332 Please do NOT post such sources to any other GNU mailing list (e.g
|
|
|
333 help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's up
|
|
|
334 to each poster to decide whether to cross-post to any non-gnUSENET
|
|
|
335 newsgroup (e.g. comp.emacs or vmsnet.sources).
|
|
|
336
|
|
|
337 Please do NOT announce that you have posted source code to
|
|
|
338 gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or
|
|
|
339 gnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep up
|
|
|
340 with sources will read this list/newsgroup. It's up to each poster to
|
|
|
341 decide whether to announce a gnu.emacs.sources article in any
|
|
|
342 non-gnUSENET newsgroup (e.g comp.emacs or comp.sources.d).
|
|
|
343
|
|
|
344 If source or patches that were previously posted or a simple fix is
|
|
|
345 requested in help-gnu-emacs, please mail it to the requester. Do NOT
|
|
|
346 repost it. If you also want something that is requested, send mail to
|
|
|
347 the requester asking him to forward it to you. This kind of traffic is
|
|
|
348 best handled by e-mail, not by a broadcast medium that reaches thousands
|
|
|
349 of sites.
|
|
|
350
|
|
|
351 If the source is very long (>10k bytes) send mail offering to send it.
|
|
|
352 This prevents the requester from getting many redundant copies and saves
|
|
|
353 network bandwidth.
|
|
|
354
|
|
|
355 * help-gnu-emacs-request@prep.ai.mit.edu to subscribe to help-gnu-emacs
|
|
|
356 ** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs)
|
|
|
357 ** Send contributions to: help-gnu-emacs@prep.ai.mit.edu
|
|
|
358
|
|
|
359 This list is the place for users and installers of GNU Emacs to ask for
|
|
|
360 help. Please send bug reports to bug-gnu-emacs instead of posting them
|
|
|
361 here.
|
|
|
362
|
|
|
363 Since help-gnu-emacs is a very large list, send it only those items that
|
|
|
364 are seriously important to many people.
|
|
|
365
|
|
|
366 If source or patches that were previously posted or a simple fix is
|
|
|
367 requested in help-gnu-emacs, please mail it to the requester. Do NOT
|
|
|
368 repost it. If you also want something that is requested, send mail to
|
|
|
369 the requester asking him to forward it to you. This kind of traffic is
|
|
|
370 best handled by e-mail, not a broadcast medium that reaches thousands of
|
|
|
371 sites.
|
|
|
372
|
|
|
373 This list is also gated one way to USENET's newsgroup comp.emacs (once
|
|
|
374 known as net.emacs). This one-way gating is done for users whose sites
|
|
|
375 get comp.emacs, but not gnu.emacs.help. Users at non-USENET sites may
|
|
|
376 receive all articles from comp.emacs by making their request to:
|
|
|
377 unix-emacs-request@bbn.com
|
|
|
378
|
|
|
379 If Emacs crashes, or if you build Emacs following the standard procedure
|
|
|
380 on a system which Emacs is supposed to work on (see etc/MACHINES) and it
|
|
|
381 does not work at all, or if an editing command does not behave as it is
|
|
|
382 documented to behave, this is a bug. Don't send bug reports to
|
|
|
383 help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to
|
|
|
384 bug-gnu-emacs@prep.ai.mit.edu instead.
|
|
|
385
|
|
|
386 See section '* General Information about help-* lists'.
|
|
|
387
|
|
|
388 * info-gnu-emacs-request@prep.ai.mit.edu to subscribe to info-gnu-emacs
|
|
|
389 ** gnUSENET newsgroup: gnu.emacs.announce (and one-way into comp.emacs)
|
|
|
390 ** Send announcements to: info-gnu-emacs@prep.ai.mit.edu
|
|
|
391
|
|
|
392 This list distributes announcements and progress reports on GNU Emacs.
|
|
|
393 It is NOT for general discussion; please use help-gnu-emacs for that.
|
|
|
394
|
|
|
395 The list is filtered to remove items meant for info-gnu-emacs-request,
|
|
|
396 that can be answered by the moderator without bothering the list, or
|
|
|
397 should have been sent to another list.
|
|
|
398
|
|
|
399 info-gnu-emacs is also gated one way to USENET's newsgroup comp.emacs
|
|
|
400 (once known as net.emacs). This one-way gating is done for users whose
|
|
|
401 sites get comp.emacs, but not gnu.emacs.announce. Users at non-USENET
|
|
|
402 sites may receive all articles from comp.emacs by making their request
|
|
|
403 to: unix-emacs-request@bbn.com
|
|
|
404
|
|
|
405 Do not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, instead
|
|
|
406 mail them to bug-gnu-emacs@prep.ai.mit.edu.
|
|
|
407
|
|
|
408 See section '* General Information about info-* lists'.
|
|
|
409
|
|
|
410 * vms-gnu-emacs-request@prep.ai.mit.edu to subscribe
|
|
|
411 ** gnUSENET newsgroup: gnu.emacs.vms
|
|
|
412 ** Send contributions to: vms-gnu-emacs@prep.ai.mit.edu
|
|
|
413
|
|
|
414 This list was a working group who did the initial port of GNU Emacs to
|
|
|
415 the VMS operating system. It still discusses problems and solutions to
|
|
|
416 the VMS port and the distribution of it.
|
|
|
417
|
|
|
418 * bug-bash-request@prep.ai.mit.edu to subscribe to bug-bash
|
|
|
419 ** gnUSENET newsgroup: gnu.bash.bug
|
|
|
420 ** BASH bug reports to: bug-bash@prep.ai.mit.edu
|
|
|
421
|
|
|
422 This list distributes, to the active maintainers of BASH (the Bourne
|
|
|
423 Again SHell), bug reports and fixes for, and suggestions for
|
|
|
424 improvements in BASH. User discussion of BASH also occurs here.
|
|
|
425
|
|
|
426 Always report the version number of the operating system, hardware, and
|
|
|
427 bash (flag -version on startup or check the variable $BASH_VERSION in a
|
|
|
428 running bash).
|
|
|
429
|
|
|
430 There are no other GNU mailing lists or gnUSENET newsgroups for BASH.
|
|
|
431
|
|
|
432 See section '* General Information about bug-* lists and reporting
|
|
|
433 program bugs'.
|
|
|
434
|
|
|
435 * bug-gdb-request@prep.ai.mit.edu to subscribe to bug-gdb
|
|
|
436 ** gnUSENET newsgroup: gnu.gdb.bug
|
|
|
437 ** GDB bug reports to: bug-gdb@prep.ai.mit.edu
|
|
|
438
|
|
|
439 This list distributes, to the active maintainers of GDB (Gnu's
|
|
|
440 DeBugger), bug reports and fixes for, and suggestions for improvements
|
|
|
441 in GDB.
|
|
|
442
|
|
|
443 There are no other GNU mailing lists or gnUSENET newsgroups for GDB.
|
|
|
444
|
|
|
445 See section '* General Information about bug-* lists and reporting
|
|
|
446 program bugs'.
|
|
|
447
|
|
|
448 * bug-octave-request@che.utexas.edu to subscribe to bug-octave
|
|
|
449 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
450 ** Octave bug reports to: bug-octave@che.utexas.edu
|
|
|
451
|
|
|
452 This list distributes, to the active maintainers of Octave (a system
|
|
|
453 for numerical computations), bug reports and fixes for, and
|
|
|
454 suggestions for improvements to Octave.
|
|
|
455
|
|
|
456 The help-octave mailing list is for user discussion of Octave.
|
|
|
457
|
|
|
458 See section '* General Information about bug-* lists and reporting
|
|
|
459 program bugs'.
|
|
|
460
|
|
|
461
|
|
|
462 * help-octave-request@che.utexas.edu to subscribe to help-octave
|
|
|
463 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
464 ** Send contributions to: help-octave@che.utexas.edu
|
|
|
465
|
|
|
466 This list is the place for users and installers of Octave to ask for
|
|
|
467 help. Please send bug reports to bug-octave instead of posting them
|
|
|
468 here.
|
|
|
469
|
|
|
470 If Octave crashes, or if you build Octave following the standard
|
|
|
471 procedure on a system on which Octave is supposed to work on and it
|
|
|
472 does not work at all, or if a command does not behave as it is
|
|
|
473 documented to behave, this is a bug. Don't send bug reports to
|
|
|
474 help-octave; mail them to bug-octave@che.utexas.edu instead.
|
|
|
475
|
|
|
476 See section '* General Information about help-* lists'.
|
|
|
477
|
|
|
478 * bug-gcc-request@prep.ai.mit.edu to subscribe to bug-gcc
|
|
|
479 ** gnUSENET newsgroup: gnu.gcc.bug
|
|
|
480 ** GCC bug reports to: bug-gcc@prep.ai.mit.edu
|
|
|
481
|
|
|
482 This list distributes bug reports for, fixes for bugs in, and
|
|
|
483 suggestions for improvements in the GNU C Compiler to its active
|
|
|
484 developers.
|
|
|
485
|
|
|
486 Please don't send in a patch without a test case to illustrate the
|
|
|
487 problem the patch is supposed to fix. Sometimes the patches aren't
|
|
|
488 correct or aren't the best way to do the job, and without a test case
|
|
|
489 there is no way to debug an alternate fix.
|
|
|
490
|
|
|
491 The most convenient form of test case is a piece of cpp output that can
|
|
|
492 be passed directly to cc1. Preferably written in C, not C++ or
|
|
|
493 Objective C.
|
|
|
494
|
|
|
495 Subscribers to bug-gcc get all info-gcc messages.
|
|
|
496
|
|
|
497 See section '* General Information about bug-* lists and reporting
|
|
|
498 program bugs'.
|
|
|
499
|
|
|
500 * help-gcc-request@prep.ai.mit.edu to subscribe to help-gcc
|
|
|
501 ** gnUSENET newsgroup: gnu.gcc.help
|
|
|
502 ** Send contributions to: help-gcc@prep.ai.mit.edu
|
|
|
503
|
|
|
504 This list is the place for users and installers of the GNU C Compiler to
|
|
|
505 ask for help.
|
|
|
506
|
|
|
507 If gcc crashes, or if you build gcc following the standard procedure on
|
|
|
508 a system which gcc is supposed to work on (see config.sub) and it does
|
|
|
509 not work at all, or if an command line option does not behave as it is
|
|
|
510 documented to behave, this is a bug. Don't send bug reports to help-gcc
|
|
|
511 (gnu.gcc.help); mail them to bug-gcc@prep.ai.mit.edu instead.
|
|
|
512
|
|
|
513 See section '* General Information about help-* lists'.
|
|
|
514
|
|
|
515 * info-gcc-request@prep.ai.mit.edu to subscribe to info-gcc
|
|
|
516 ** gnUSENET newsgroup: gnu.gcc.announce
|
|
|
517 ** Send announcements to: info-gcc@prep.ai.mit.edu
|
|
|
518
|
|
|
519 This list distributes announcements and progress reports on the GNU C
|
|
|
520 Compiler. It is NOT for general discussion; please use help-gcc for
|
|
|
521 that.
|
|
|
522
|
|
|
523 The list is filtered to remove items meant for info-gcc-request, that
|
|
|
524 can be answered by the moderator without bothering the list, or should
|
|
|
525 have been sent to another list.
|
|
|
526
|
|
|
527 See section '* General Information about info-* lists'.
|
|
|
528
|
|
|
529 * bug-gnu960-request@ichips.intel.com to subscribe to bug-gnu960
|
|
|
530 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
531 ** Intel 960 Port bug reports to: bug-gnu960@ichips.intel.com
|
|
|
532
|
|
|
533 This list distributes bug reports for, fixes for bugs in, and
|
|
|
534 suggestions for improvements in Intel's port of GNU software to the
|
|
|
535 Intel 960 microprocessor.
|
|
|
536
|
|
|
537 You can also fax to: GNU/960 - 1-503-696-4930.
|
|
|
538
|
|
|
539 There are no other GNU mailing lists or gnUSENET newsgroups for Intel's
|
|
|
540 port of GNU software to the Intel 960 microprocessor.
|
|
|
541
|
|
|
542 See section '* General Information about bug-* lists and reporting
|
|
|
543 program bugs'.
|
|
|
544
|
|
|
545 * bug-glibc-request@prep.ai.mit.edu to subscribe to bug-glibc
|
|
|
546 ** gnUSENET newsgroup: gnu.glibc.bug
|
|
|
547 ** GNU C Library bug reports to: bug-glibc@prep.ai.mit.edu
|
|
|
548
|
|
|
549 This list distributes, to the active maintainers of glibc (GNU's C
|
|
|
550 library), bug reports and fixes for, and suggestions for improvements in
|
|
|
551 glibc. User discussion of glibc also occurs here.
|
|
|
552
|
|
|
553 Announcements of new releases of glibc are made on both info-gcc and
|
|
|
554 bug-glibc.
|
|
|
555
|
|
|
556 There are no other GNU mailing lists or gnUSENET newsgroups for the GNU
|
|
|
557 C Library.
|
|
|
558
|
|
|
559 See section '* General Information about bug-* lists and reporting
|
|
|
560 program bugs'.
|
|
|
561
|
|
|
562 * bug-g++-request@prep.ai.mit.edu to subscribe to bug-g++
|
|
|
563 ** gnUSENET newsgroup: gnu.g++.bug
|
|
|
564 ** G++ bug reports to: bug-g++@prep.ai.mit.edu
|
|
|
565
|
|
|
566 This list distributes bug reports for, fixes for bugs in, and
|
|
|
567 suggestions for improvements in the GNU C++ Compiler to its active
|
|
|
568 developers.
|
|
|
569
|
|
|
570 G++ uses the GNU C-Compiler back end. Active developers may wish to
|
|
|
571 subscribe to bug-gcc@prep.ai.mit.edu as well.
|
|
|
572
|
|
|
573 Subscribers to bug-g++ get all info-g++ messages.
|
|
|
574
|
|
|
575 See section '* General Information about bug-* lists and reporting
|
|
|
576 program bugs'.
|
|
|
577
|
|
|
578 * help-g++-request@prep.ai.mit.edu to subscribe to help-g++
|
|
|
579 ** gnUSENET newsgroup: gnu.g++.help (and one-way into comp.lang.c++)
|
|
|
580 ** Send contributions to: help-g++@prep.ai.mit.edu
|
|
|
581
|
|
|
582 This list is the place for users and installers of the GNU C++ Compiler
|
|
|
583 to ask for help. Please send bug reports to bug-g++@prep.ai.mit.edu
|
|
|
584 instead of posting them here.
|
|
|
585
|
|
|
586 help-g++ is also gated one way to USENET's newsgroup comp.lang.c++.
|
|
|
587 This one-way gating is done for users whose sites get comp.lang.c++, but
|
|
|
588 not gnu.g++.help.
|
|
|
589
|
|
|
590 See section '* General Information about help-* lists'.
|
|
|
591
|
|
|
592 * info-g++-request@prep.ai.mit.edu to subscribe to info-g++
|
|
|
593 ** gnUSENET newsgroup: gnu.g++.announce (and one-way into comp.lang.c++)
|
|
|
594 ** Send announcements to: info-g++@prep.ai.mit.edu
|
|
|
595
|
|
|
596 This list distributes announcements and progress reports on the GNU C++
|
|
|
597 Compiler. It is NOT for general discussion; please use help-g++ for
|
|
|
598 that.
|
|
|
599
|
|
|
600 The list is filtered to remove items meant for info-g++-request, that
|
|
|
601 can be answered by the moderator without bothering the list, or should
|
|
|
602 have been sent to another list.
|
|
|
603
|
|
|
604 It is also gated one way to USENET's newsgroup comp.lang.c++. This
|
|
|
605 one-way gating is done for users whose sites get comp.lang.c++, but not
|
|
|
606 gnu.g++.announce.
|
|
|
607
|
|
|
608 Do not report g++ bugs to info-g++ or comp.lang.c++, mail them to
|
|
|
609 bug-g++@prep.ai.mit.edu instead.
|
|
|
610
|
|
|
611 See section '* General Information about info-* lists'.
|
|
|
612
|
|
|
613 * bug-lib-g++-request@prep.ai.mit.edu to subscribe to bug-lib-g++
|
|
|
614 ** gnUSENET newsgroup: gnu.g++.lib.bug
|
|
|
615 ** lib-g++ bug reports to: bug-lib-g++@prep.ai.mit.edu
|
|
|
616
|
|
|
617 This list distributes, to the active maintainers of libg++ (GNU's
|
|
|
618 library for C++), bug reports and fixes for, and suggestions for
|
|
|
619 improvements in lib-g++. User discussion of libg++ also occurs here.
|
|
|
620
|
|
|
621 Announcements of new releases of libg++ are made on both info-g++ and
|
|
|
622 bug-lib-g++.
|
|
|
623
|
|
|
624 There are no other GNU mailing lists or gnUSENET newsgroups for GNU's
|
|
|
625 G++ Library.
|
|
|
626
|
|
|
627 See section '* General Information about bug-* lists and reporting
|
|
|
628 program bugs'.
|
|
|
629
|
|
|
630 * info-gnu-fortran-request@prep.ai.mit.edu to subscribe to info-gnu-fortran
|
|
|
631 ** gnUSENET newsgroup: NONE YET
|
|
|
632 ** Send announcements to: info-gnu-fortran@prep.ai.mit.edu
|
|
|
633
|
|
|
634 This list is for progress reports about the GNU Fortran compiler. In
|
|
|
635 the future it will also be used for release notices.
|
|
|
636
|
|
|
637 The list is filtered to remove items meant for info-gnu-fortran-request,
|
|
|
638 that can be answered by the moderator without bothering the list, or
|
|
|
639 should have been sent to another list.
|
|
|
640
|
|
|
641 People on the Internet can get a current status report by fingering the
|
|
|
642 address fortran@gnu.ai.mit.edu.
|
|
|
643
|
|
|
644 See section '* General Information about info-* lists'.
|
|
|
645
|
|
|
646 There are no other GNU mailing lists or gnUSENET newsgroups for GNU
|
|
|
647 Fortran (yet).
|
|
|
648
|
|
|
649 * bug-oleo-request@prep.ai.mit.edu to subscribe to bug-oleo
|
|
|
650 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
651 ** Oleo bug reports to: bug-oleo@prep.ai.mit.edu
|
|
|
652
|
|
|
653 This list distributes, to the active maintainers of Oleo (the GNU
|
|
|
654 spreadsheet), bug reports and fixes for, and suggestions for
|
|
|
655 improvements to Oleo. User discussion of Oleo also occurs here.
|
|
|
656
|
|
|
657 There are no other GNU mailing lists or gnUSENET newsgroups for Oleo .
|
|
|
658
|
|
|
659 See section '* General Information about bug-* lists and reporting
|
|
|
660 program bugs'.
|
|
|
661
|
|
|
662 * bug-gmp-request@prep.ai.mit.edu to subscribe to bug-gmp
|
|
|
663 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
664 ** gmp bug reports to: bug-gmp@prep.ai.mit.edu
|
|
|
665
|
|
|
666 This list distributes, to the active maintainers of gmp (the GNU
|
|
|
667 Multiple Precision Library), bug reports and fixes for, and suggestions
|
|
|
668 for improvements to gmp. User discussion of gmp also occurs here.
|
|
|
669
|
|
|
670 There are no other GNU mailing lists or gnUSENET newsgroups for gmp .
|
|
|
671
|
|
|
672 See section '* General Information about bug-* lists and reporting
|
|
|
673 program bugs'.
|
|
|
674
|
|
|
675 * bug-cfengine-request@prep.ai.mit.edu to subscribe to bug-cfengine
|
|
|
676 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
677 ** cfengine bug reports to: bug-cfengine@prep.ai.mit.edu
|
|
|
678
|
|
|
679 This list distributes, to the active maintainers of cfengine (configure
|
|
|
680 BSD and System-5-like operating systems attached to a TCP/IP network),
|
|
|
681 bug reports and fixes for, and suggestions for improvements to cfengine.
|
|
|
682 User discussion of cfengine also occurs here.
|
|
|
683
|
|
|
684 There are no other GNU mailing lists or gnUSENET newsgroups for cfengine .
|
|
|
685
|
|
|
686 See section '* General Information about bug-* lists and reporting
|
|
|
687 program bugs'.
|
|
|
688
|
|
|
689 * bug-guile-request@prep.ai.mit.edu to subscribe to bug-guile
|
|
|
690 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
691 ** GUILE BUG reports to: bug-guile@prep.ai.mit.edu
|
|
|
692
|
|
|
693 This list distributes, to the active maintainers of GUILE (GNU's
|
|
|
694 Ubiquitous Extension Language), bug reports and fixes for, and suggestions for
|
|
|
695 improvements to GUILE. User discussion of GUILE also occurs here.
|
|
|
696
|
|
|
697 There are no other GNU mailing lists or gnUSENET newsgroups for GUILE .
|
|
|
698
|
|
|
699 See section '* General Information about bug-* lists and reporting
|
|
|
700 program bugs'.
|
|
|
701
|
|
|
702 * bug-gnu-smalltalk-request@prep.ai.mit.edu to subscribe to bug-gnu-smalltalk
|
|
|
703 ** gnUSENET newsgroup: gnu.smalltalk.bug
|
|
|
704 ** GNU Smalltalk bug reports to: bug-gnu-smalltalk@prep.ai.mit.edu
|
|
|
705
|
|
|
706 GNU Smalltalk is the GNU project implementation of the Smalltalk language.
|
|
|
707
|
|
|
708 This list distributes, to the active maintainers of GNU Smalltalk, bug
|
|
|
709 reports and fixes for, and suggestions for improvements to GNU
|
|
|
710 Smalltalk. User discussion of GNU Smalltalk also occurs here.
|
|
|
711
|
|
|
712 For now, new releases of GNU Smalltalk will also be announced on this list.
|
|
|
713
|
|
|
714 There are no other GNU mailing lists or gnUSENET newsgroups for GNU
|
|
|
715 Smalltalk.
|
|
|
716
|
|
|
717 See section '* General Information about bug-* lists and reporting
|
|
|
718 program bugs'.
|
|
|
719
|
|
|
720 * st-next-request@laplace.eng.sun.com to subscribe to st-next
|
|
|
721 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
722 ** Send contributions to: st-next@laplace.eng.sun.com
|
|
|
723
|
|
|
724 For people interested in working on GNU Smalltalk on the NeXT.
|
|
|
725
|
|
|
726 * bug-groff-request@prep.ai.mit.edu to subscribe to bug-groff
|
|
|
727 ** gnUSENET newsgroup: gnu.groff.bug
|
|
|
728 ** GNU groff bug reports to: bug-groff@prep.ai.mit.edu
|
|
|
729
|
|
|
730 groff is the GNU project implementation, in C++, of the traditional Unix
|
|
|
731 document formatting tools.
|
|
|
732
|
|
|
733 This list distributes, to the active maintainers of groff, bug reports
|
|
|
734 and fixes for, and suggestions for improvements to groff (and it
|
|
|
735 component programs). User discussion of groff also occurs here.
|
|
|
736
|
|
|
737 For now, new releases of groff will also be announced on this list.
|
|
|
738
|
|
|
739 There are no other GNU mailing lists or gnUSENET newsgroups for groff.
|
|
|
740
|
|
|
741 See section '* General Information about bug-* lists and reporting
|
|
|
742 program bugs'.
|
|
|
743
|
|
|
744 * bug-ghostscript-request@prep.ai.mit.edu to subscribe to bug-ghostscript
|
|
|
745 ** gnUSENET newsgroup: gnu.ghostscript.bug
|
|
|
746 ** Ghostscript bug reports to: bug-ghostscript@prep.ai.mit.edu
|
|
|
747
|
|
|
748 GhostScript is the GNU project implementation of a language and graphics
|
|
|
749 library with a remarkable similarity to PostScript.
|
|
|
750
|
|
|
751 This list distributes, to the active maintainers of Ghostscript, bug
|
|
|
752 reports and fixes for, and suggestions for improvements in Ghostscript.
|
|
|
753
|
|
|
754 For now, new releases of Ghostscript will also be announced on this list.
|
|
|
755
|
|
|
756 There are no other GNU mailing lists or gnUSENET newsgroups for
|
|
|
757 GhostScript.
|
|
|
758
|
|
|
759 See section '* General Information about bug-* lists and reporting
|
|
|
760 program bugs'.
|
|
|
761
|
|
|
762 * bug-gnu-utils-request@prep.ai.mit.edu to subscribe to bug-gnu-utils
|
|
|
763 ** gnUSENET newsgroup: gnu.utils.bug
|
|
|
764 ** GNU Utilities bug reports to: bug-gnu-utils@prep.ai.mit.edu
|
|
|
765
|
|
|
766 This list distributes, to the active maintainers of these programs, bug
|
|
|
767 reports and fixes for, and suggestions for improvements in GNU programs
|
|
|
768 not covered by other bug-* mailing lists/gnu.*.bug newsgroups.
|
|
|
769
|
|
|
770 Subscribers to bug-gnu-utils get all info-gnu-utils messages.
|
|
|
771
|
|
|
772 See section '* General Information about bug-* lists and reporting
|
|
|
773 program bugs'.
|
|
|
774
|
|
|
775 * help-gnu-utils-request@prep.ai.mit.edu to subscribe to help-gnu-utils
|
|
|
776 ** gnUSENET newsgroup: gnu.utils.help
|
|
|
777 ** Send contributions to: help-gnu-utils@prep.ai.mit.edu
|
|
|
778
|
|
|
779 This list is the place for users and installers of GNU programs not
|
|
|
780 covered by other GNU mailing lists/gnu.* newsgroups to ask for help.
|
|
|
781
|
|
|
782 Don't send bug reports to help-gnu-utils (gnu.utils.help); mail them to
|
|
|
783 bug-gnu-utils@prep.ai.mit.edu instead.
|
|
|
784
|
|
|
785 See section '* General Information about help-* lists'.
|
|
|
786
|
|
|
787 * info-gnu-utils-request@prep.ai.mit.edu to subscribe to info-gnu-utils
|
|
|
788 ** gnUSENET newsgroup: gnu.utils.announce
|
|
|
789 ** Send announcements to: info-gnu-utils@prep.ai.mit.edu
|
|
|
790
|
|
|
791 This list distributes announcements and progress reports on GNU programs
|
|
|
792 not covered by other GNU mailing lists/gnu.* newsgroups. It is NOT for
|
|
|
793 general discussion; please use help-gnu-utils for that.
|
|
|
794
|
|
|
795 The list is filtered to remove items meant for info-gnu-utils-request,
|
|
|
796 that can be answered by the moderator without bothering the list, or
|
|
|
797 should have been sent to another list.
|
|
|
798
|
|
|
799 See section '* General Information about info-* lists'.
|
|
|
800
|
|
|
801 * info-cvs-request@prep.ai.mit.edu to subscribe to info-cvs.
|
|
|
802 ** USENET newsgroup: (none)
|
|
|
803 ** CVS discussions/questions to: info-cvs@prep.ai.mit.edu
|
|
|
804
|
|
|
805 This list is for discussion and dissemination of information about
|
|
|
806 CVS. Please check the FAQ before posting questions, however.
|
|
|
807
|
|
|
808 * bug-cvs-request@prep.ai.mit.edu to subscribe to bug-cvs.
|
|
|
809 ** USENET newsgroup: (none)
|
|
|
810 ** CVS bug reports to: bug-cvs@prep.ai.mit.edu
|
|
|
811
|
|
|
812 This list distributes bug reports, fixes, and suggestions for
|
|
|
813 improvements to the maintainers of CVS. It also feeds directly into a
|
|
|
814 GNATS database, so it's best if bug reports are sent in the from of
|
|
|
815 GNATS Problem Reports.
|
|
|
816
|
|
|
817 * bug-fortran-mode-request@erl.mit.edu to subscribe to bug-fortran-mode
|
|
|
818 ** USENET newsgroup: (none)
|
|
|
819 ** Fortran mode bug reports to: bug-fortran-mode@erl.mit.edu
|
|
|
820
|
|
|
821 This list collects bug reports, fixes for bugs, and suggestions for
|
|
|
822 improvements in GNU Emacs's Fortran mode (a major mode to support
|
|
|
823 editing Fortran source code).
|
|
|
824
|
|
|
825 It is the place to report Fortran mode bugs by all users of Fortran
|
|
|
826 mode.
|
|
|
827
|
|
|
828 Always report the version number Fortran mode reports on startup as well
|
|
|
829 as the version of Emacs.
|
|
|
830
|
|
|
831 There is no info-fortran-mode list. There are no USENET gateways to
|
|
|
832 bug-fortran-mode at this time.
|
|
|
833
|
|
|
834 * info-gnus-request@flab.fujitsu.co.jp to subscribe
|
|
|
835 ** gnUSENET newsgroup: NONE YET
|
|
|
836 ** Send contributions to: info-gnus@flab.fujitsu.co.jp
|
|
|
837
|
|
|
838 The list is intended to exchange useful information about GNUS, such as
|
|
|
839 bug reports, useful hooks, and extensions of GNUS. GNUS is an NNTP-base
|
|
|
840 network news reader for GNU Emacs (which also works with a news spool).
|
|
|
841 English and Japanese are the official languages of the list. GNUS is
|
|
|
842 quite different than gnews.
|
|
|
843
|
|
|
844 * info-gnus-english-request@prep.ai.mit.edu to subscribe
|
|
|
845 ** gnUSENET newsgroup: gnu.emacs.gnus
|
|
|
846 ** Send contributions to: info-gnus-english@prep.ai.mit.edu
|
|
|
847
|
|
|
848 The list has the same charter as info-gnus. The difference is that
|
|
|
849 English is the only official language of the list.
|
|
|
850
|
|
|
851 info-gnus-english/gnu.emacs.gnus is forward to info-gnus, but NOT
|
|
|
852 vice-versa.
|
|
|
853
|
|
|
854 * info-gnews-request@ics.uci.edu to subscribe to info-gnews
|
|
|
855 ** gnUSENET newsgroup: gnu.emacs.gnews
|
|
|
856 ** Send contributions to: info-gnews@ics.uci.edu
|
|
|
857
|
|
|
858 This newsgroup is intended to exchange useful information about gnews,
|
|
|
859 such as bug reports, useful hooks, and extensions of gnews. gnews is an
|
|
|
860 NNTP-base network news reader for GNU Emacs (which also works a news
|
|
|
861 spool). It is quite different than GNUS.
|
|
|
862
|
|
|
863 * gnu-emacs-ada-request@grebyn.com to subscribe to gnu-emacs-ada
|
|
|
864 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
865 ** Gnu Emacs Ada support bug reports to: gnu-emacs-ada@grebyn.com
|
|
|
866
|
|
|
867 This list distributes bug reports for, fixes for bugs in, and
|
|
|
868 suggestions for improvements in GNU Emacs' editing support of the Ada
|
|
|
869 programming language.
|
|
|
870
|
|
|
871 There are no other GNU mailing lists or gnUSENET newsgroups for GNU
|
|
|
872 Emacs' editing support of Ada.
|
|
|
873
|
|
|
874 See section '* General Information about bug-* lists and reporting
|
|
|
875 program bugs'.
|
|
|
876
|
|
|
877 * bug-vm-request@uunet.uu.net to subscribe to bug-vm
|
|
|
878 ** gnUSENET newsgroup: gnu.emacs.vm.bug
|
|
|
879 ** VM mail reader bug reports to: bug-vm@uunet.uu.net
|
|
|
880
|
|
|
881 This list discusses bugs in View Mail mode for GNU Emacs, with an
|
|
|
882 emphasis on beta and prerelease versions.
|
|
|
883
|
|
|
884 Always report the version number of VM you are using, as well as the
|
|
|
885 version of Emacs you're running. If you believe it is significant,
|
|
|
886 report the operating system used and the hardware.
|
|
|
887
|
|
|
888 Subscribers to bug-vm get all info-vm messages.
|
|
|
889
|
|
|
890 * info-vm-request@uunet.uu.net to subscribe to info-vm
|
|
|
891 ** gnUSENET newsgroup: gnu.emacs.vm.info
|
|
|
892 ** Send contributions to: info-vm@uunet.uu.net
|
|
|
893
|
|
|
894 This list discusses the View Mail mode for GNU Emacs, an alternative to
|
|
|
895 rmail mode.
|
|
|
896
|
|
|
897 * supercite-request@warsaw.nlm.nih.gov to subscribe to supercite
|
|
|
898 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
899 ** Send articles to: supercite@warsaw.nlm.nih.gov
|
|
|
900 *** UUCP: ..!uunet!warsaw.nlm.nih.gov!supercite-request
|
|
|
901
|
|
|
902 The supercite mailing list covers issues related to the advanced
|
|
|
903 mail/news citation package called Supercite for GNU Emacs.
|
|
|
904
|
|
|
905 * auc-tex-request@iesd.auc.dk to subscribe
|
|
|
906 ** USENET newsgroup: NONE YET
|
|
|
907 ** Send contributions to: auc-tex@iesd.auc.dk
|
|
|
908
|
|
|
909 The list is intended to exchange information about AUC TeX, such as
|
|
|
910 bug reports, request for help, and information on current
|
|
|
911 developments. AUC TeX is a much enhanced LaTeX mode for GNU Emacs.
|
|
|
912
|
|
|
913 The list is unmoderated.
|
|
|
914
|
|
|
915 * bug-gnu-chess-request@prep.ai.mit.edu to subscribe to bug-gnu-chess
|
|
|
916 ** gnUSENET newsgroup: gnu.chess.bug
|
|
|
917 ** GNU Chess bug reports to: bug-gnu-chess@prep.ai.mit.edu
|
|
|
918
|
|
|
919 This list directly accesses the GNU Chess developer's group. If you
|
|
|
920 have a *BUG* to report about the program, which can also include a
|
|
|
921 feature enhancement request, please send it to this list.
|
|
|
922
|
|
|
923 Subscribers to bug-gnu-chess get all info-gnu-chess messages.
|
|
|
924
|
|
|
925 See section '* General Information about bug-* lists and reporting
|
|
|
926 program bugs'.
|
|
|
927
|
|
|
928 * help-gnu-chess-request@prep.ai.mit.edu to subscribe to help-gnu-chess
|
|
|
929 ** gnUSENET newsgroup: gnu.chess
|
|
|
930 ** Send contributions to: help-gnu-chess@prep.ai.mit.edu
|
|
|
931
|
|
|
932 This list is the place for users and installers of GNU Chess to ask for
|
|
|
933 help. This list is also used for games played by people or other
|
|
|
934 entities against the program, and other generalized non-bug,
|
|
|
935 non-enhancement data. Please send bug reports to bug-gnu-chess instead
|
|
|
936 of posting them here.
|
|
|
937
|
|
|
938 Since help-gnu-chess is a large list, send it only those items that
|
|
|
939 are seriously important to many people.
|
|
|
940
|
|
|
941 If source or patches that were previously posted or a simple fix is
|
|
|
942 requested in help-gnu-chess, please mail it to the requester. Do NOT
|
|
|
943 repost it. If you also want something that is requested, send mail to
|
|
|
944 the requester asking him to forward it to you. This kind of traffic is
|
|
|
945 best handled by e-mail, not a broadcast medium that reaches thousands of
|
|
|
946 sites.
|
|
|
947
|
|
|
948 See section '* General Information about help-* lists'.
|
|
|
949
|
|
|
950 * info-gnu-chess-request@prep.ai.mit.edu to subscribe to info-gnu-chess
|
|
|
951 ** gnUSENET newsgroup: gnu.chess.announce
|
|
|
952 ** Send contributions to: info-gnu-chess@prep.ai.mit.edu
|
|
|
953
|
|
|
954 This list is used for announcements about GNU Chess and related
|
|
|
955 programs, and small but important patches.
|
|
|
956
|
|
|
957 The list is filtered to remove items meant for info-gnu-chess-request,
|
|
|
958 that can be answered by the moderator without bothering the list, or
|
|
|
959 should have been sent to another list.
|
|
|
960
|
|
|
961 See section '* General Information about info-* lists'.
|
|
|
962
|
|
|
963 * bug-gnu-shogi-request@prep.ai.mit.edu to subscribe to bug-gnu-shogi
|
|
|
964 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
965 ** GNU Shogi bug reports to: bug-gnu-shogi@prep.ai.mit.edu
|
|
|
966
|
|
|
967 This list directly accesses the GNU Shogi developer's group. If you
|
|
|
968 have a *BUG* to report about the program, which can also include a
|
|
|
969 feature enhancement request, please send it to this list.
|
|
|
970
|
|
|
971 Subscribers to bug-gnu-shogi get all info-gnu-shogi messages.
|
|
|
972
|
|
|
973 See section '* General Information about bug-* lists and reporting
|
|
|
974 program bugs'.
|
|
|
975
|
|
|
976 Shogi is a game something like chess. There are several different types
|
|
|
977 of pieces, a board that is 9 by 9 squares, and the modification that a
|
|
|
978 captured piece can be reintroduced on the board by the capturing player
|
|
|
979 (and used). Due to this last difference from Western chess, a Shogi
|
|
|
980 game never simplifies.
|
|
|
981
|
|
|
982 * help-gnu-shogi-request@prep.ai.mit.edu to subscribe to help-gnu-shogi
|
|
|
983 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
984 ** Send contributions to: help-gnu-shogi@prep.ai.mit.edu
|
|
|
985
|
|
|
986 This list is the place for users and installers of GNU Shogi to ask for
|
|
|
987 help. This list is also used for games played by people or other
|
|
|
988 entities against the program, and other generalized non-bug,
|
|
|
989 non-enhancement data. Please send bug reports to bug-gnu-shogi instead
|
|
|
990 of posting them here.
|
|
|
991
|
|
|
992 Since help-gnu-shogi is a large list, send it only those items that
|
|
|
993 are seriously important to many people.
|
|
|
994
|
|
|
995 If source or patches that were previously posted or a simple fix is
|
|
|
996 requested in help-gnu-shogi, please mail it to the requester. Do NOT
|
|
|
997 repost it. If you also want something that is requested, send mail to
|
|
|
998 the requester asking him to forward it to you. This kind of traffic is
|
|
|
999 best handled by e-mail, not a broadcast medium that reaches thousands of
|
|
|
1000 sites.
|
|
|
1001
|
|
|
1002 See section '* General Information about help-* lists'.
|
|
|
1003
|
|
|
1004 * info-gnu-shogi-request@prep.ai.mit.edu to subscribe to info-gnu-shogi
|
|
|
1005 ** gnUSENET newsgroup: NONE PLANNED
|
|
|
1006 ** Send contributions to: info-gnu-shogi@prep.ai.mit.edu
|
|
|
1007
|
|
|
1008 This list is used for announcements about GNU Shogi and related
|
|
|
1009 programs, and small but important patches.
|
|
|
1010
|
|
|
1011 The list is filtered to remove items meant for info-gnu-shogi-request,
|
|
|
1012 that can be answered by the moderator without bothering the list, or
|
|
|
1013 should have been sent to another list.
|
|
|
1014
|
|
|
1015 See section '* General Information about info-* lists'.
|
|
|
1016
|
|
|
1017 * gnu-manual-request@a.cs.uiuc.edu IS NOW DEFUNCT
|
|
|
1018 ** DEAD: Gnusenet newsgroup: gnu.emacs.lisp.manual
|
|
|
1019 ** DEAD address: gnu-manual@a.cs.uiuc.edu
|
|
|
1020 *** DEAD UUCP address: ..!uunet!uiucdcs!gnu-manual-request
|
|
|
1021
|
|
|
1022 This list and newsgroup is dead. It was a working group whose
|
|
|
1023 volunteers wrote, proofread and commented on the developing GNU Emacs
|
|
|
1024 Lisp programmers manual.
|
|
|
1025
|
|
|
1026 Send bugs in the GNU Emacs Lisp reference manual to:
|
|
|
1027 lisp-manual-bugs@prep.ai.mit.edu
|
|
|
1028
|
|
|
1029 lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.
|
|
|
1030 It's just a bug-reporting address.
|
|
|
1031
|
|
|
1032 * no mailing list request
|
|
|
1033 ** gnUSENET newsgroup: gnu.gnusenet.config
|
|
|
1034 ** no mailing list
|
|
|
1035
|
|
|
1036 This newsgroup has nothing to do with GNU software, especially its
|
|
|
1037 configuration. It exists to distribute information about the
|
|
|
1038 administration and configuration of gnUSENET: the gnu.all alternative
|
|
|
1039 USENET hierarchy that carry the GNU mailing lists.
|
|
|
1040
|
|
|
1041 Administrators of gnUSENET hosts receiving the gnu.all newsgroups are
|
|
|
1042 welcome to ask questions here or via e-mail of gnu@prep.ai.mit.edu.
|
|
|
1043
|
|
|
1044 * no mailing list request
|
|
|
1045 ** gnUSENET newsgroup: gnu.gnusenet.test
|
|
|
1046 ** no mailing list
|
|
|
1047
|
|
|
1048 This newsgroup has nothing to do with GNU software, especially its
|
|
|
1049 testing. It exists to allow test messages to be made in gnUSENET: the
|
|
|
1050 gnu.all alternative USENET hierarchy that carry the GNU mailing lists.
|
|
|
1051
|
|
|
1052 Local variables:
|
|
|
1053 mode: outline
|
|
|
1054 fill-column: 72
|
|
|
1055 End:
|
