[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/gnus.texi
|
From: |
Miles Bader |
|
Subject: |
[Emacs-diffs] Changes to emacs/man/gnus.texi |
|
Date: |
Fri, 04 Apr 2003 01:23:34 -0500 |
Index: emacs/man/gnus.texi
diff -c emacs/man/gnus.texi:1.32 emacs/man/gnus.texi:1.33
*** emacs/man/gnus.texi:1.32 Wed Jan 15 20:16:09 2003
--- emacs/man/gnus.texi Tue Feb 4 09:53:27 2003
***************
*** 627,633 ****
Getting Mail
! * Mail in a Newsreader:: Important introductory notes.
* Getting Started Reading Mail:: A simple cookbook example.
* Splitting Mail:: How to create mail groups.
* Mail Sources:: How to tell Gnus where to get mail from.
--- 627,633 ----
Getting Mail
! * Mail in a Newsreader:: Important introductory notes.
* Getting Started Reading Mail:: A simple cookbook example.
* Splitting Mail:: How to create mail groups.
* Mail Sources:: How to tell Gnus where to get mail from.
***************
*** 1188,1194 ****
@item gnus-subscribe-topics
@vindex gnus-subscribe-topics
! Put the groups into the topic that has a matching @code{subscribe} topic
parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
topic parameter that looks like
--- 1188,1194 ----
@item gnus-subscribe-topics
@vindex gnus-subscribe-topics
! Put the groups into the topic that has a matching @code{subscribe} topic
parameter (@pxref{Topic Parameters}). For instance, a @code{subscribe}
topic parameter that looks like
***************
*** 1196,1202 ****
"nnslashdot"
@end example
! will mean that all groups that match that regex will be subscribed under
that topic.
If no topics match the groups, the groups will be subscribed in the
--- 1196,1202 ----
"nnslashdot"
@end example
! will mean that all groups that match that regex will be subscribed under
that topic.
If no topics match the groups, the groups will be subscribed in the
***************
*** 1486,1492 ****
@code{LIST ACTIVE group} command, this isn't very nice to the server.
If you think that starting up Gnus takes too long, try all the three
! different values for this variable and see what works best for you.
In any case, if you use @code{some} or @code{nil}, you should definitely
kill all groups that you aren't interested in to speed things up.
--- 1486,1492 ----
@code{LIST ACTIVE group} command, this isn't very nice to the server.
If you think that starting up Gnus takes too long, try all the three
! different values for this variable and see what works best for you.
In any case, if you use @code{some} or @code{nil}, you should definitely
kill all groups that you aren't interested in to speed things up.
***************
*** 2698,2704 ****
default charset will be used for decoding articles.
See also @code{gnus-group-ignored-charsets-alist}.
!
@item posting-style
You can store additional posting style information for this group only
here (@pxref{Posting Styles}). The format is that of an entry in the
--- 2698,2704 ----
default charset will be used for decoding articles.
See also @code{gnus-group-ignored-charsets-alist}.
!
@item posting-style
You can store additional posting style information for this group only
here (@pxref{Posting Styles}). The format is that of an entry in the
***************
*** 3278,3284 ****
@item T j
@kindex T j (Topic)
@findex gnus-topic-jump-to-topic
! Go to a topic (@code{gnus-topic-jump-to-topic}).
@item T c
@kindex T c (Topic)
--- 3278,3284 ----
@item T j
@kindex T j (Topic)
@findex gnus-topic-jump-to-topic
! Go to a topic (@code{gnus-topic-jump-to-topic}).
@item T c
@kindex T c (Topic)
***************
*** 3523,3532 ****
@table @code
@item subscribe
! When subscribing new groups by topic (@pxref{Subscription Methods}), the
! @code{subscribe} topic parameter says what groups go in what topic. Its
value should be a regexp to match the groups that should go in that
! topic.
@end table
--- 3523,3532 ----
@table @code
@item subscribe
! When subscribing new groups by topic (@pxref{Subscription Methods}), the
! @code{subscribe} topic parameter says what groups go in what topic. Its
value should be a regexp to match the groups that should go in that
! topic.
@end table
***************
*** 3642,3648 ****
@item gnus-group-name-charset-group-alist
@vindex gnus-group-name-charset-group-alist
! An alist of regexp of group name and the charset for group names.
It is used to show non-ASCII group names.
For example:
--- 3642,3648 ----
@item gnus-group-name-charset-group-alist
@vindex gnus-group-name-charset-group-alist
! An alist of regexp of group name and the charset for group names.
It is used to show non-ASCII group names.
For example:
***************
*** 4498,4505 ****
encoded in the @code{cn-gb-2312} charset. If you have
@lisp
! (setq gnus-summary-show-article-charset-alist
! '((1 . cn-gb-2312)
(2 . big5)))
@end lisp
--- 4498,4505 ----
encoded in the @code{cn-gb-2312} charset. If you have
@lisp
! (setq gnus-summary-show-article-charset-alist
! '((1 . cn-gb-2312)
(2 . big5)))
@end lisp
***************
*** 4731,4737 ****
@kindex S o p @r{(Summary)}
@findex gnus-summary-post-forward
Forward the current article to a newsgroup
! (@code{gnus-summary-post-forward}).
If no prefix is given, the message is forwarded according to the value
of (@code{message-forward-as-mime}) and
(@code{message-forward-show-mml}); if the prefix is 1, decode the
--- 4731,4737 ----
@kindex S o p @r{(Summary)}
@findex gnus-summary-post-forward
Forward the current article to a newsgroup
! (@code{gnus-summary-post-forward}).
If no prefix is given, the message is forwarded according to the value
of (@code{message-forward-as-mime}) and
(@code{message-forward-show-mml}); if the prefix is 1, decode the
***************
*** 6554,6560 ****
@lisp
(setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
! (setq gnus-default-article-saver
'gnus-summary-save-in-file) ; no encoding
@end lisp
--- 6554,6560 ----
@lisp
(setq gnus-use-long-file-name '(not-save)) ; to get a hierarchy
! (setq gnus-default-article-saver
'gnus-summary-save-in-file) ; no encoding
@end lisp
***************
*** 7432,7438 ****
@item W Q
@kindex W Q @r{(Summary)}
! @findex gnus-article-fill-long-lines
Fill long lines (@code{gnus-article-fill-long-lines}).
@item W C
--- 7432,7438 ----
@item W Q
@kindex W Q @r{(Summary)}
! @findex gnus-article-fill-long-lines
Fill long lines (@code{gnus-article-fill-long-lines}).
@item W C
***************
*** 7480,7486 ****
@item W h
@kindex W h @r{(Summary)}
@findex gnus-article-wash-html
! Treat HTML (@code{gnus-article-wash-html}).
Note that the this is usually done automatically by Gnus if the message
in question has a @code{Content-Type} header that says that this type
has been done.
--- 7480,7486 ----
@item W h
@kindex W h @r{(Summary)}
@findex gnus-article-wash-html
! Treat HTML (@code{gnus-article-wash-html}).
Note that the this is usually done automatically by Gnus if the message
in question has a @code{Content-Type} header that says that this type
has been done.
***************
*** 7824,7830 ****
@kindex A t @r{(Summary)}
@findex gnus-article-babel
Translate the article from one language to another
! (@code{gnus-article-babel}).
@end table
--- 7824,7830 ----
@kindex A t @r{(Summary)}
@findex gnus-article-babel
Translate the article from one language to another
! (@code{gnus-article-babel}).
@end table
***************
*** 8529,8535 ****
@vindex gnus-preserve-marks
Move the article from one mail group to another
(@code{gnus-summary-move-article}). Marks will be preserved if
! @var{gnus-preserve-marks} is address@hidden (which is the default).
@item B c
@kindex B c @r{(Summary)}
--- 8529,8535 ----
@vindex gnus-preserve-marks
Move the article from one mail group to another
(@code{gnus-summary-move-article}). Marks will be preserved if
! @var{gnus-preserve-marks} is address@hidden (which is the default).
@item B c
@kindex B c @r{(Summary)}
***************
*** 9277,9283 ****
@findex gnus-mime-view-part-as-type
@item t @r{(Article)}
View the @sc{mime} object as if it were a different @sc{mime} media type
! (@code{gnus-mime-view-part-as-type}).
@findex gnus-mime-pipe-part
@item | @r{(Article)}
--- 9277,9283 ----
@findex gnus-mime-view-part-as-type
@item t @r{(Article)}
View the @sc{mime} object as if it were a different @sc{mime} media type
! (@code{gnus-mime-view-part-as-type}).
@findex gnus-mime-pipe-part
@item | @r{(Article)}
***************
*** 9427,9433 ****
@code{gnus-part-display-hook}. The functions are called narrowed to the
part, and you can do anything you like, pretty much. There is no
information that you have to keep in the buffer---you can change
! everything.
@node Article Keymap
--- 9427,9433 ----
@code{gnus-part-display-hook}. The functions are called narrowed to the
part, and you can do anything you like, pretty much. There is no
information that you have to keep in the buffer---you can change
! everything.
@node Article Keymap
***************
*** 10514,10520 ****
The file contains one or more line, each of which define one server.
@item
! Each line may contain an arbitrary number of token/value pairs.
The valid tokens include @samp{machine}, @samp{login}, @samp{password},
@samp{default}. In addition Gnus introduces two new tokens, not present
--- 10514,10520 ----
The file contains one or more line, each of which define one server.
@item
! Each line may contain an arbitrary number of token/value pairs.
The valid tokens include @samp{machine}, @samp{login}, @samp{password},
@samp{default}. In addition Gnus introduces two new tokens, not present
***************
*** 10573,10579 ****
@lisp
'(("nntpd 1\\.5\\.11t"
! (remove-hook 'nntp-server-opened-hook
'nntp-send-mode-reader)))
@end lisp
--- 10573,10579 ----
@lisp
'(("nntpd 1\\.5\\.11t"
! (remove-hook 'nntp-server-opened-hook
'nntp-send-mode-reader)))
@end lisp
***************
*** 10714,10724 ****
@lisp
;; Type `C-c C-c' after you've finished editing.
;;
! ;; "snews" is port 563 and is predefined
;; in our /etc/services
;;
(nntp "snews.bar.com"
! (nntp-open-connection-function
nntp-open-ssl-stream)
(nntp-port-number "snews")
(nntp-address "snews.bar.com"))
--- 10714,10724 ----
@lisp
;; Type `C-c C-c' after you've finished editing.
;;
! ;; "snews" is port 563 and is predefined
;; in our /etc/services
;;
(nntp "snews.bar.com"
! (nntp-open-connection-function
nntp-open-ssl-stream)
(nntp-port-number "snews")
(nntp-address "snews.bar.com"))
***************
*** 10878,10884 ****
course.
@menu
! * Mail in a Newsreader:: Important introductory notes.
* Getting Started Reading Mail:: A simple cookbook example.
* Splitting Mail:: How to create mail groups.
* Mail Sources:: How to tell Gnus where to get mail from.
--- 10878,10884 ----
course.
@menu
! * Mail in a Newsreader:: Important introductory notes.
* Getting Started Reading Mail:: A simple cookbook example.
* Splitting Mail:: How to create mail groups.
* Mail Sources:: How to tell Gnus where to get mail from.
***************
*** 10897,10907 ****
@node Mail in a Newsreader
@subsection Mail in a Newsreader
! If you are used to traditional mail readers, but have decided to switch
to reading mail with Gnus, you may find yourself experiencing something
of a culture shock.
! Gnus does not behave like traditional mail readers. If you want to make
it behave that way, you can, but it's an uphill battle.
Gnus, by default, handles all its groups using the same approach. This
--- 10897,10907 ----
@node Mail in a Newsreader
@subsection Mail in a Newsreader
! If you are used to traditional mail readers, but have decided to switch
to reading mail with Gnus, you may find yourself experiencing something
of a culture shock.
! Gnus does not behave like traditional mail readers. If you want to make
it behave that way, you can, but it's an uphill battle.
Gnus, by default, handles all its groups using the same approach. This
***************
*** 10915,10921 ****
deleted? How awful!
But, no, it means that old messages are @dfn{expired} according to some
! scheme or other. For news messages, the expire process is controlled by
the news administrator; for mail, the expire process is controlled by
you. The expire process for mail is covered in depth in @pxref{Expiring
Mail}.
--- 10915,10921 ----
deleted? How awful!
But, no, it means that old messages are @dfn{expired} according to some
! scheme or other. For news messages, the expire process is controlled by
the news administrator; for mail, the expire process is controlled by
you. The expire process for mail is covered in depth in @pxref{Expiring
Mail}.
***************
*** 11071,11077 ****
can use the @kbd{M-x nnmail-split-history} command. If you wish to see
where re-spooling messages would put the messages, you can use
@code{gnus-summary-respool-trace} and related commands (@pxref{Mail
! Group Commands}).
Gnus gives you all the opportunity you could possibly want for shooting
yourself in the foot. Let's say you create a group that will contain
--- 11071,11077 ----
can use the @kbd{M-x nnmail-split-history} command. If you wish to see
where re-spooling messages would put the messages, you can use
@code{gnus-summary-respool-trace} and related commands (@pxref{Mail
! Group Commands}).
Gnus gives you all the opportunity you could possibly want for shooting
yourself in the foot. Let's say you create a group that will contain
***************
*** 11146,11153 ****
(file)
@end lisp
! If the mail spool file is not located on the local machine, it's best to
! use POP or @sc{imap} or the like to fetch the mail. You can not use ange-ftp
file names here---it has no way to lock the mail spool while moving the
mail.
--- 11146,11153 ----
(file)
@end lisp
! If the mail spool file is not located on the local machine, it's best to
! use POP or @sc{imap} or the like to fetch the mail. You can not use ange-ftp
file names here---it has no way to lock the mail spool while moving the
mail.
***************
*** 11337,11348 ****
Two example maildir mail sources:
@lisp
! (maildir :path "/home/user-name/Maildir/"
:subdirs ("cur" "new"))
@end lisp
@lisp
! (maildir :path "/user@@remotehost.org:~/Maildir/"
:subdirs ("new"))
@end lisp
--- 11337,11348 ----
Two example maildir mail sources:
@lisp
! (maildir :path "/home/user-name/Maildir/"
:subdirs ("cur" "new"))
@end lisp
@lisp
! (maildir :path "/user@@remotehost.org:~/Maildir/"
:subdirs ("new"))
@end lisp
***************
*** 11435,11442 ****
An example @sc{imap} mail source:
@lisp
! (imap :server "mail.mycorp.com"
! :stream kerberos4
:fetchflag "\\Seen")
@end lisp
--- 11435,11442 ----
An example @sc{imap} mail source:
@lisp
! (imap :server "mail.mycorp.com"
! :stream kerberos4
:fetchflag "\\Seen")
@end lisp
***************
*** 11476,11483 ****
An example webmail source:
@lisp
! (webmail :subtype 'hotmail
! :user "user-name"
:password "secret")
@end lisp
@end table
--- 11476,11483 ----
An example webmail source:
@lisp
! (webmail :subtype 'hotmail
! :user "user-name"
:password "secret")
@end lisp
@end table
***************
*** 11495,11501 ****
@lisp
(setq mail-sources
! '((directory :path "/home/pavel/.Spool/"
:suffix ""
:plugged t)))
@end lisp
--- 11495,11501 ----
@lisp
(setq mail-sources
! '((directory :path "/home/pavel/.Spool/"
:suffix ""
:plugged t)))
@end lisp
***************
*** 11704,11710 ****
(any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
(any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
;; Both lists below have the same suffix, so prevent
! ;; cross-posting to mkpkg.list of messages posted only to
;; the bugs- list, but allow cross-posting when the
;; message was really cross-posted.
(any "bugs-mypackage@@somewhere" "mypkg.bugs")
--- 11704,11710 ----
(any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
(any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
;; Both lists below have the same suffix, so prevent
! ;; cross-posting to mkpkg.list of messages posted only to
;; the bugs- list, but allow cross-posting when the
;; message was really cross-posted.
(any "bugs-mypackage@@somewhere" "mypkg.bugs")
***************
*** 12719,12726 ****
little bit of optimization to this so that each of one's mail groups has
a Unix mail box file. It's faster than @code{nnmbox} because each group
can be parsed separately, and still provides the simple Unix mail box
! format requiring minimal effort in moving the mail around. In addition,
! it maintains an ``active'' file making it much faster for Gnus to figure
out how many messages there are in each separate group.
If you have groups that are expected to have a massive amount of
--- 12719,12726 ----
little bit of optimization to this so that each of one's mail groups has
a Unix mail box file. It's faster than @code{nnmbox} because each group
can be parsed separately, and still provides the simple Unix mail box
! format requiring minimal effort in moving the mail around. In addition,
! it maintains an ``active'' file making it much faster for Gnus to figure
out how many messages there are in each separate group.
If you have groups that are expected to have a massive amount of
***************
*** 12746,12758 ****
go through a cumbersome subscription procedure, and most people don't
even know what a news group is.
! The problem with this scenario is that web browsers are not very good at
! being newsreaders. They do not keep track of what articles you've read;
! they do not allow you to score on subjects you're interested in; they do
not allow off-line browsing; they require you to click around and drive
you mad in the end.
! So---if web browsers suck at reading discussion forums, why not use Gnus
to do it instead?
Gnus has been getting a bit of a collection of back ends for providing
--- 12746,12758 ----
go through a cumbersome subscription procedure, and most people don't
even know what a news group is.
! The problem with this scenario is that web browsers are not very good at
! being newsreaders. They do not keep track of what articles you've read;
! they do not allow you to score on subjects you're interested in; they do
not allow off-line browsing; they require you to click around and drive
you mad in the end.
! So---if web browsers suck at reading discussion forums, why not use Gnus
to do it instead?
Gnus has been getting a bit of a collection of back ends for providing
***************
*** 12769,12775 ****
All the web sources require Emacs/w3 and the url library to work.
The main caveat with all these web sources is that they probably won't
! work for a very long time. Gleaning information from the @sc{html} data
is guesswork at best, and when the layout is altered, the Gnus back end
will fail. If you have reasonably new versions of these back ends,
though, you should be ok.
--- 12769,12775 ----
All the web sources require Emacs/w3 and the url library to work.
The main caveat with all these web sources is that they probably won't
! work for a very long time. Gleaning information from the @sc{html} data
is guesswork at best, and when the layout is altered, the Gnus back end
will fail. If you have reasonably new versions of these back ends,
though, you should be ok.
***************
*** 12971,12977 ****
information Gnus needs to keep groups updated.
The easiest way to get started with @code{nnultimate} is to say
! something like the following in the group buffer: @kbd{B nnultimate
@key{RET}
http://www.tcj.com/messboard/ubbcgi/ @key{RET}}. (Substitute the @sc{url}
(not including @samp{Ultimate.cgi} or the like at the end) for a forum
you're interested in; there's quite a list of them on the Ultimate web
--- 12971,12977 ----
information Gnus needs to keep groups updated.
The easiest way to get started with @code{nnultimate} is to say
! something like the following in the group buffer: @kbd{B nnultimate @key{RET}
http://www.tcj.com/messboard/ubbcgi/ @key{RET}}. (Substitute the @sc{url}
(not including @samp{Ultimate.cgi} or the like at the end) for a forum
you're interested in; there's quite a list of them on the Ultimate web
***************
*** 13032,13043 ****
@cindex url
@cindex Netscape
! Gnus uses the url library to fetch web pages and Emacs/w3 to display web
pages. Emacs/w3 is documented in its own manual, but there are some
things that may be more relevant for Gnus users.
For instance, a common question is how to make Emacs/w3 follow links
! using the @code{browse-url} functions (which will call some external web
browser like Netscape). Here's one way:
@lisp
--- 13032,13043 ----
@cindex url
@cindex Netscape
! Gnus uses the url library to fetch web pages and Emacs/w3 to display web
pages. Emacs/w3 is documented in its own manual, but there are some
things that may be more relevant for Gnus users.
For instance, a common question is how to make Emacs/w3 follow links
! using the @code{browse-url} functions (which will call some external web
browser like Netscape). Here's one way:
@lisp
***************
*** 13722,13728 ****
@lisp
(setq gnus-post-method
! '(nngateway
"mail2news@@replay.com"
(nngateway-header-transformation
nngateway-mail2news-header-transformation)))
--- 13722,13728 ----
@lisp
(setq gnus-post-method
! '(nngateway
"mail2news@@replay.com"
(nngateway-header-transformation
nngateway-mail2news-header-transformation)))
***************
*** 13771,13777 ****
might look something like this:
@lisp
! (setq gnus-secondary-select-methods
'((nnimap "simpleserver") ; no special configuration
; perhaps a ssh port forwarded server:
(nnimap "dolk"
--- 13771,13777 ----
might look something like this:
@lisp
! (setq gnus-secondary-select-methods
'((nnimap "simpleserver") ; no special configuration
; perhaps a ssh port forwarded server:
(nnimap "dolk"
***************
*** 13833,13839 ****
@lisp
(nnimap "mail.server.com"
! (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
("~friend/Mail/" . "list/*"))))
@end lisp
--- 13833,13839 ----
@lisp
(nnimap "mail.server.com"
! (nnimap-list-pattern ("INBOX" "Mail/*" "alt.sex.*"
("~friend/Mail/" . "list/*"))))
@end lisp
***************
*** 14041,14047 ****
@lisp
(setq nnimap-split-rule
! '(("INBOX.nnimap"
"^Sender: owner-nnimap@@vic20.globalcom.se")
("INBOX.junk" "^Subject:.*MAKE MONEY")
("INBOX.private" "")))
--- 14041,14047 ----
@lisp
(setq nnimap-split-rule
! '(("INBOX.nnimap"
"^Sender: owner-nnimap@@vic20.globalcom.se")
("INBOX.junk" "^Subject:.*MAKE MONEY")
("INBOX.private" "")))
***************
*** 15618,15624 ****
For example, to do hierarchical scoring but use a non-server-specific
overall score file, you could use the value
@example
! (list (lambda (group) ("all.SCORE"))
'gnus-score-find-hierarchical)
@end example
--- 15618,15624 ----
For example, to do hierarchical scoring but use a non-server-specific
overall score file, you could use the value
@example
! (list (lambda (group) ("all.SCORE"))
'gnus-score-find-hierarchical)
@end example
***************
*** 16297,16303 ****
If you want to lower the score of articles that have been crossposted to
more than, say, 3 groups:
@lisp
! ("xref"
("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
-1000 nil r))
@end lisp
--- 16297,16303 ----
If you want to lower the score of articles that have been crossposted to
more than, say, 3 groups:
@lisp
! ("xref"
("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+"
-1000 nil r))
@end lisp
***************
*** 17533,17539 ****
accomplish that, something like the following can be done:
@lisp
! (message
(frame 1.0
(if (not (buffer-live-p gnus-summary-buffer))
(car (cdr (assoc 'group gnus-buffer-configuration)))
--- 17533,17539 ----
accomplish that, something like the following can be done:
@lisp
! (message
(frame 1.0
(if (not (buffer-live-p gnus-summary-buffer))
(car (cdr (assoc 'group gnus-buffer-configuration)))
***************
*** 17575,17581 ****
@subsection Example Window Configurations
@itemize @bullet
! @item
Narrow left hand side occupied by group buffer. Right hand side split
between summary buffer (top one-sixth) and article buffer (bottom).
--- 17575,17581 ----
@subsection Example Window Configurations
@itemize @bullet
! @item
Narrow left hand side occupied by group buffer. Right hand side split
between summary buffer (top one-sixth) and article buffer (bottom).
***************
*** 18090,18096 ****
@findex gnus-undo
The undoability is provided by the @code{gnus-undo-mode} minor mode. It
is used if @code{gnus-use-undo} is address@hidden, which is the
! default. The @kbd{C-M-_} key performs the @code{gnus-undo}
command, which should feel kinda like the normal Emacs @code{undo}
command.
--- 18090,18096 ----
@findex gnus-undo
The undoability is provided by the @code{gnus-undo-mode} minor mode. It
is used if @code{gnus-use-undo} is address@hidden, which is the
! default. The @kbd{C-M-_} key performs the @code{gnus-undo}
command, which should feel kinda like the normal Emacs @code{undo}
command.
***************
*** 18915,18921 ****
Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
! 1999.
If you happen upon a version of Gnus that has a prefixed name --
``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'' --
--- 18915,18921 ----
Gnus 5.6 begat Pterodactyl Gnus on August 29th 1998 and was released as
``Gnus 5.8'' (after 99 releases and a CVS repository) on December 3rd
! 1999.
If you happen upon a version of Gnus that has a prefixed name --
``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'' --
***************
*** 20150,20156 ****
(setq nnmail-procmail-suffix "\\.in")
@end lisp
! this now has changed to
@lisp
(setq mail-sources
--- 20150,20156 ----
(setq nnmail-procmail-suffix "\\.in")
@end lisp
! this now has changed to
@lisp
(setq mail-sources
***************
*** 20179,20185 ****
@item The Gnus posting styles have been redone again and now works in a
subtly different manner.
! @item New web-based back ends have been added: @code{nnslashdot},
@code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
again, to keep up with ever-changing layouts.
--- 20179,20185 ----
@item The Gnus posting styles have been redone again and now works in a
subtly different manner.
! @item New web-based back ends have been added: @code{nnslashdot},
@code{nnwarchive} and @code{nnultimate}. nnweb has been revamped,
again, to keep up with ever-changing layouts.
***************
*** 20258,20273 ****
that's already there. This is not how this manual is written. When
implementing something, I write the manual entry for that something
straight away. I then see that it's difficult to explain the
! functionality, so I write how it's supposed to be, and then I change the
implementation. Writing the documentation and writing the code goes
hand in hand.
This, of course, means that this manual has no, or little, flow. It
documents absolutely everything in Gnus, but often not where you're
! looking for it. It is a reference manual, and not a guide to how to get
started with Gnus.
! That would be a totally different book, that should be written using the
reference manual as source material. It would look quite differently.
--- 20258,20273 ----
that's already there. This is not how this manual is written. When
implementing something, I write the manual entry for that something
straight away. I then see that it's difficult to explain the
! functionality, so I write how it's supposed to be, and then I change the
implementation. Writing the documentation and writing the code goes
hand in hand.
This, of course, means that this manual has no, or little, flow. It
documents absolutely everything in Gnus, but often not where you're
! looking for it. It is a reference manual, and not a guide to how to get
started with Gnus.
! That would be a totally different book, that should be written using the
reference manual as source material. It would look quite differently.
***************
*** 21488,21495 ****
"*Non-nil means that nndir will never retrieve NOV headers."
nnml-nov-is-evil)
! (defvoo nndir-current-group ""
! nil
nnml-current-group nnmh-current-group)
(defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
(defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
--- 21488,21495 ----
"*Non-nil means that nndir will never retrieve NOV headers."
nnml-nov-is-evil)
! (defvoo nndir-current-group ""
! nil
nnml-current-group nnmh-current-group)
(defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
(defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
***************
*** 21508,21514 ****
(unless (assq 'nndir-directory defs)
(push `(nndir-directory ,server) defs))
(push `(nndir-current-group
! ,(file-name-nondirectory
(directory-file-name nndir-directory)))
defs)
(push `(nndir-top-directory
--- 21508,21514 ----
(unless (assq 'nndir-directory defs)
(push `(nndir-directory ,server) defs))
(push `(nndir-current-group
! ,(file-name-nondirectory
(directory-file-name nndir-directory)))
defs)
(push `(nndir-top-directory
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/man/gnus.texi,
Miles Bader <=