projects
/
gnus
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
message.el: Silent the byte compiler
[gnus]
/
etc
/
gnus-tut.txt
diff --git
a/etc/gnus-tut.txt
b/etc/gnus-tut.txt
index
aa73f08
..
8267870
100644
(file)
--- a/
etc/gnus-tut.txt
+++ b/
etc/gnus-tut.txt
@@
-25,8
+25,7
@@
Ingebrigtsen. If you have a WWW browser, you can investigate to your
heart's delight at <URL:http://www.gnus.org/> and
<URL:http://quimby.gnus.org/lmi/>.
heart's delight at <URL:http://www.gnus.org/> and
<URL:http://quimby.gnus.org/lmi/>.
-;; Copyright (C) 1995, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-;; 2008, 2009, 2010 Free Software Foundation, Inc.
+;; Copyright (C) 1995, 2001-2015 Free Software Foundation, Inc.
;; Author: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
;; Keywords: news
;; Author: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
;; Keywords: news
@@
-57,7
+56,7
@@
to set `gnus-select-method'. A "method" is a way of specifying *how*
the news is to be found, and from *where*.
Say you want to read news from you local, friendly nntp server
the news is to be found, and from *where*.
Say you want to read news from you local, friendly nntp server
-"news.my.local.server".
+"news.my.local.server".
(setq gnus-select-method '(nntp "news.my.local.server"))
(setq gnus-select-method '(nntp "news.my.local.server"))
@@
-132,14
+131,14
@@
So if you want to go with nnmbox, you can simply say:
(The same for the other methods, kind of.)
(The same for the other methods, kind of.)
-You should also set `nnmail-split-methods' to something sensible:
+You should also set `nnmail-split-methods' to something sensible:
-(setq nnmail-split-methods
+(setq nnmail-split-methods
'(("mail.junk" "From:.*Lars")
("mail.misc "")))
This will put all mail from me in you junk mail group, and the rest in
'(("mail.junk" "From:.*Lars")
("mail.misc "")))
This will put all mail from me in you junk mail group, and the rest in
-"mail.misc".
+"mail.misc".
These groups will be subscribe the same way as the normal groups, so
you will probably find them among the zombie groups after you set
These groups will be subscribe the same way as the normal groups, so
you will probably find them among the zombie groups after you set
@@
-152,11
+151,11
@@
Date: Fri Feb 24 13:40:45 1995
Subject: Foreign newsgroups
Message-ID: <lars-doc5@eyesore.no>
Subject: Foreign newsgroups
Message-ID: <lars-doc5@eyesore.no>
-These are groups that do not come from `gnus-select-method'.
+These are groups that do not come from `gnus-select-method'.
Say you want to read "alt.furniture.couches" from "news.funet.fi". You
can then either type `B news.funet.fi <RET>' to browse that server and
Say you want to read "alt.furniture.couches" from "news.funet.fi". You
can then either type `B news.funet.fi <RET>' to browse that server and
-subscribe to that group, or you can type
+subscribe to that group, or you can type
`G m alt.furniture.couches<RET>nntp<RET>news.funet.fi<RET>', if you
like to type a lot.
`G m alt.furniture.couches<RET>nntp<RET>news.funet.fi<RET>', if you
like to type a lot.
@@
-178,7
+177,7
@@
Message-ID: <lars-doc6@eyesore.no>
Gnus really isn't GNUS, even though it looks like it. If you scrape
the surface, you'll find that most things have changed.
Gnus really isn't GNUS, even though it looks like it. If you scrape
the surface, you'll find that most things have changed.
-This means that old code that relies on GNUS internals will fail.
+This means that old code that relies on GNUS internals will fail.
In particular, `gnus-newsrc-hashtb', `gnus-newsrc-assoc',
`gnus-killed-list', the `nntp-header-' macros and the display formats
In particular, `gnus-newsrc-hashtb', `gnus-newsrc-assoc',
`gnus-killed-list', the `nntp-header-' macros and the display formats
@@
-190,13
+189,13
@@
remove all hilit code from all the Gnus hooks
(`gnus-group-prepare-hook', `gnus-summary-prepare-hook' and
`gnus-summary-article-hook'). (Well, at the very least the first
two.) Gnus provides various integrated functions for highlighting,
(`gnus-group-prepare-hook', `gnus-summary-prepare-hook' and
`gnus-summary-article-hook'). (Well, at the very least the first
two.) Gnus provides various integrated functions for highlighting,
-which are both faster and more accurate
d
.
+which are both faster and more accurate.
There is absolutely no chance, whatsoever, of getting Gnus to work
with Emacs 18. It won't even work on Emacsen older than Emacs
20.7/XEmacs 21.1. Upgrade your Emacs or die.
There is absolutely no chance, whatsoever, of getting Gnus to work
with Emacs 18. It won't even work on Emacsen older than Emacs
20.7/XEmacs 21.1. Upgrade your Emacs or die.
-
+
From lars Thu Feb 23 23:20:38 1995
From: larsi@gnus.org (ding)
Date: Fri Feb 24 13:40:45 1995
From lars Thu Feb 23 23:20:38 1995
From: larsi@gnus.org (ding)
Date: Fri Feb 24 13:40:45 1995
@@
-226,7
+225,7
@@
Create the group by saying
This will create the group "nnvirtual:my.virtual.newsgroup", which
will collect all articles from all the groups in the "rec.aquaria"
This will create the group "nnvirtual:my.virtual.newsgroup", which
will collect all articles from all the groups in the "rec.aquaria"
-hierarchy.
+hierarchy.
If you want to edit the regular expression, just type `M-e' on the
group line.
If you want to edit the regular expression, just type `M-e' on the
group line.
@@
-258,7
+257,7
@@
the lines of:
(setq gnus-select-group-hook
(lambda ()
(setq gnus-select-group-hook
(lambda ()
- (if (eq 'nnvirtual (car (gnus-find-method-for-group
+ (if (eq 'nnvirtual (car (gnus-find-method-for-group
gnus-newsgroup-name)))
(progn
(make-local-variable 'gnus-thread-sort-functions)
gnus-newsgroup-name)))
(progn
(make-local-variable 'gnus-thread-sort-functions)
@@
-275,18
+274,18
@@
If you want to report a bug, please type `M-x gnus-bug'. This will
give me a precise overview of your Gnus and Emacs version numbers,
along with a look at all Gnus variables you have changed.
give me a precise overview of your Gnus and Emacs version numbers,
along with a look at all Gnus variables you have changed.
-D
u
not expect a reply back, but your bug should be fixed in the next
+D
o
not expect a reply back, but your bug should be fixed in the next
version. If the bug persists, please re-submit your bug report.
When a bug occurs, I need a recipe for how to trigger the bug. You
have to tell me exactly what you do to uncover the bug, and you should
(setq debug-on-error t) and send me the backtrace along with the bug
version. If the bug persists, please re-submit your bug report.
When a bug occurs, I need a recipe for how to trigger the bug. You
have to tell me exactly what you do to uncover the bug, and you should
(setq debug-on-error t) and send me the backtrace along with the bug
-report.
+report.
If I am not able to reproduce the bug, I won't be able to fix it.
I would, of course, prefer that you locate the bug, fix it, and mail
If I am not able to reproduce the bug, I won't be able to fix it.
I would, of course, prefer that you locate the bug, fix it, and mail
-me the patches, but one can't have everything.
+me the patches, but one can't have everything.
If you have any questions on usage, the "ding@gnus.org" mailing list
is where to post the questions.
If you have any questions on usage, the "ding@gnus.org" mailing list
is where to post the questions.
@@
-310,8
+309,6
@@
and press `C-x C-e':
On older XEmacs version, use:
(Info-goto-node "(gnus)Frequently Asked Questions")
On older XEmacs version, use:
(Info-goto-node "(gnus)Frequently Asked Questions")
-
+
Or simply use RET or the middle mouse button, if the above is displayed
as a clickable button.
Or simply use RET or the middle mouse button, if the above is displayed
as a clickable button.
-
-