Mercurial > emacs
annotate BUGS @ 65719:5265a4059126
Revision: miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-564
Merge from gnus--rel--5.10
Patches applied:
* gnus--rel--5.10 (patch 125-127)
- Merge from emacs--cvs-trunk--0
- Update from CVS
2005-09-27 Reiner Steib <Reiner.Steib@gmx.de>
* lisp/gnus/mm-uu.el (mm-uu-emacs-sources-regexp): Make variable
customizable. Change default value.
(mm-uu-diff-groups-regexp): Change default value.
(mm-uu-type-alist): Added doc string.
(mm-uu-configure): Added doc string. Make it interactive.
(mm-uu-diff-groups-regexp): Fix missing quotes from previous
commit.
2005-09-27 Simon Josefsson <jas@extundo.com>
* lisp/gnus/message.el (message-idna-to-ascii-rhs-1): Reformat.
2005-09-27 Arne J,Ax(Brgensen <arne@arnested.dk>
* lisp/gnus/message.el (message-remove-duplicates): New function.
Implementation borrowed from `gnus-remove-duplicates'.
(message-idna-to-ascii-rhs): Also encode idna addresses in
Reply-To:, Mail-Reply-To: and Mail-Followup-To:.
(message-idna-to-ascii-rhs-1): When `message-use-idna' is 'ask
only ask about the same idna domain once per header and also tell
in what header to replace the idna domain.
* lisp/gnus/gnus-art.el (article-decode-idna-rhs): Also decode idna
addresses in Reply-To:, Mail-Reply-To: and Mail-Followup-To:.
(article-decode-idna-rhs): Fix regexp so that all idna-address in
a header is decoded and not just the last one.
2005-09-27 Katsumi Yamaoka <yamaoka@jpl.org>
* lisp/gnus/gnus-art.el (gnus-mime-display-single): Don't modify text if it
has been decoded.
* lisp/gnus/mm-decode.el (mm-insert-part): Don't modify text if it has been
decoded.
* lisp/gnus/mm-view.el (mm-inline-text): Don't strip text props unless
decoding enriched or richtext parts.
2005-09-26 Katsumi Yamaoka <yamaoka@jpl.org>
* man/gnus.texi (Server Buffer Format): Document the %a format spec.
author | Miles Bader <miles@gnu.org> |
---|---|
date | Wed, 28 Sep 2005 05:26:02 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
rev | line source |
---|---|
25856 | 1 If you think you may have found a bug in GNU Emacs, please |
2 read the Bugs section of the Emacs manual for advice on | |
3 (1) how to tell when to report a bug, and | |
4 (2) how to write a useful bug report and what information | |
5 it needs to have. | |
6 | |
7 There are three ways to read the Bugs section. | |
8 | |
9 (1) In a printed copy of the Emacs manual. | |
10 You can order one from the Free Software Foundation; | |
11 see the file etc/ORDERS. But if you don't have a copy on | |
12 hand and you think you have found a bug, you shouldn't wait | |
13 to get a printed manual; you should read the section right away | |
14 as described below. | |
15 | |
16 (2) With Info. Start Emacs, do C-h i to enter Info, | |
17 then m Emacs RET to get to the Emacs manual, then m Bugs RET | |
18 to get to the section on bugs. Or use standalone Info in | |
19 a like manner. (Standalone Info is part of the Texinfo distribution, | |
20 not part of the Emacs distribution.) | |
21 | |
22 (3) By hand. Do | |
23 cat info/emacs* | more "+/^File: emacs, Node: Bugs," | |
24 | |
55212
8ce686bd7f4f
Update key binding for viewing PROBLEMS.
Richard M. Stallman <rms@gnu.org>
parents:
34822
diff
changeset
|
25 Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to |
34822 | 26 make sure it isn't a known issue. |