Mercurial > emacs
view nt/README @ 61126:c0aa521e0ca7
Revision: miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-220
Merge from gnus--rel--5.10
Patches applied:
* gnus--rel--5.10 (patch 45-52)
- Update from CVS
- Update from CVS: texi Makefile.in CVS keyw cruft
- Update from CVS: ChangeLog tweaks
2005-03-29 Reiner Steib <Reiner.Steib@gmx.de>
* etc/gnus-refcard.tex, etc/gnus-logo.eps: New files.
2005-03-25 Katsumi Yamaoka <yamaoka@jpl.org>
* lisp/gnus/message.el (message-resend): Bind rfc2047-encode-encoded-words.
* lisp/gnus/mm-util.el (mm-replace-in-string): New function.
(mm-xemacs-find-mime-charset-1): Ignore errors while loading
latin-unity, which cannot be used with XEmacs 21.1.
* lisp/gnus/rfc2047.el (rfc2047-encode-function-alist): Rename from
rfc2047-encoding-function-alist in order to avoid conflicting with
the old version.
(rfc2047-encode-message-header): Remove useless goto-char.
(rfc2047-encodable-p): Don't move point.
(rfc2047-syntax-table): Treat `(' and `)' as is.
(rfc2047-encode-region): Concatenate words containing non-ASCII
characters in structured fields; don't encode space-delimited
ASCII words even in unstructured fields; don't break words at
char-category boundaries; encode encoded words in structured
fields; treat text within parentheses as special; show the
original text when error has occurred; move point to the end of
the region after encoding, suggested by IRIE Tetsuya
<irie@t.email.ne.jp>; treat backslash-quoted characters as
non-special; check carefully whether to encode special characters;
fix some kind of misconfigured headers; signal a real error if
debug-on-quit or debug-on-error is non-nil; don't infloop,
suggested by Hiroshi Fujishima <pooh@nature.tsukuba.ac.jp>; assume
the close parenthesis may be included in the encoded word; encode
bogus delimiters.
(rfc2047-encode-string): Use mm-with-multibyte-buffer.
(rfc2047-encode-max-chars): New variable.
(rfc2047-encode-1): New function.
(rfc2047-encode): Use it; encode text so that it occupies the
maximum width within 76-column; work correctly on Q encoding for
iso-2022-* charsets; fold the line before encoding; don't append a
space if the encoded word includes close parenthesis.
(rfc2047-fold-region): Use existing whitespace for LWSP; make it
sure not to break a line just after the header name.
(rfc2047-b-encode-region): Remove.
(rfc2047-b-encode-string): New function.
(rfc2047-q-encode-region): Remove.
(rfc2047-q-encode-string): New function.
(rfc2047-encode-parameter): New function.
(rfc2047-encoded-word-regexp): Don't use shy group.
(rfc2047-decode-region): Follow rfc2047-encoded-word-regexp change.
(rfc2047-parse-and-decode): Ditto.
(rfc2047-decode): Treat the ascii coding-system as raw-text by
default.
2005-03-25 Lars Magne Ingebrigtsen <larsi@gnus.org>
* lisp/gnus/rfc2047.el (rfc2047-encode-encoded-words): New variable.
(rfc2047-field-value): Strip props.
(rfc2047-encode-message-header): Disabled header folding -- not
all headers can be folded, and this should be done by the message
composition mode. Probably. I think.
(rfc2047-encodable-p): Say that =? needs encoding.
(rfc2047-encode-region): Encode =? strings.
2005-03-25 Jesper Harder <harder@ifa.au.dk>
* lisp/gnus/rfc2047.el (rfc2047-encoded-word-regexp): Support RFC 2231
language tags; remove unnecessary '+'. Reported by Stefan Wiens
<s.wi@gmx.net>.
(rfc2047-decode-string): Don't cons a string unnecessarily.
(rfc2047-parse-and-decode, rfc2047-decode): Use a character for
the encoding to avoid consing a string.
(rfc2047-decode): Use mm-subst-char-in-string instead of
mm-replace-chars-in-string.
2005-03-25 TSUCHIYA Masatoshi <tsuchiya@namazu.org>
* lisp/gnus/rfc2047.el (rfc2047-encode): Use uppercase letters to specify
encodings of MIME-encoded words, in order to improve
interoperability with several broken MUAs.
2005-03-21 Reiner Steib <Reiner.Steib@gmx.de>
* lisp/gnus/gnus-srvr.el (gnus-browse-select-group): Add NUMBER argument and
pass it to `gnus-browse-read-group'.
(gnus-browse-read-group): Add NUMBER argument and pass it to
`gnus-group-read-ephemeral-group'.
* lisp/gnus/gnus-group.el (gnus-group-read-ephemeral-group): Add NUMBER
argument and pass it to `gnus-group-read-group'.
2005-03-19 Aidan Kehoe <kehoea@parhasard.net>
* lisp/gnus/mm-util.el (mm-xemacs-find-mime-charset): Only call
mm-xemacs-find-mime-charset-1 if we have the mule feature
available at runtime.
2005-03-25 Katsumi Yamaoka <yamaoka@jpl.org>
* man/emacs-mime.texi (Display Customization): Markup fixes.
(rfc2047): Update.
2005-03-23 Reiner Steib <Reiner.Steib@gmx.de>
* man/gnus-faq.texi: Replaced with auto-generated version.
author | Miles Bader <miles@gnu.org> |
---|---|
date | Wed, 30 Mar 2005 08:14:32 +0000 |
parents | ac71b28eccf8 |
children | 3723093a21fd |
line wrap: on
line source
Emacs for Windows NT/2000 and Windows 95/98/ME Copyright (c) 2001 Free Software Foundation, Inc. See the end of the INSTALL file in this directory for copying permissions. This directory contains support for compiling and running GNU Emacs on Windows NT, Windows 95, and their successors. This port supports all of the major functionality of the Unix version, including subprocesses, windowing features (fonts, colors, scroll bars, multiple frames, etc.), and networking support. Precompiled distributions are also available; ftp to ftp://ftp.gnu.org/gnu/windows/emacs/latest/ for the latest precompiled distributions. * Building and installing See the INSTALL file in this directory for detailed instructions on building and installing Emacs on your system. * Further information There is a web page that serves as a FAQ for the Windows port of Emacs (a.k.a. NTEmacs) at: http://www.gnu.org/software/emacs/windows/ntemacs.html There is also a mailing list for discussing issues related to this port of Emacs. For information about the list, see this Web page: http://mail.gnu.org/mailman/listinfo/help-emacs-windows To ask questions on the mailing list, send email to help-emacs-windows@gnu.org. (You don't need to subscribe for that.) To subscribe to the list or unsubscribe from it, fill the form you find at http://mail.gnu.org/mailman/listinfo/help-emacs-windows as explained there. Another valuable source of information and help which should not be overlooked is the various Usenet news groups dedicated to Emacs. These are particularly good for help with general issues which aren't specific to the Windows port of Emacs. The main news groups to use for seeking help are: gnu.emacs.help comp.emacs There are also fairly regular postings and announcements of new or updated Emacs packages on this group: gnu.emacs.sources * Reporting bugs If you encounter a bug in this port of Emacs, we would like to hear about it. First check the file etc/PROBLEMS and the FAQ on the web page above to see if the bug is already known and if there are any workarounds. If not, then check whether the bug has something to do with code in your .emacs file, e.g. by invoking Emacs with the "-q --no-site-file" options. If you decide that it is a bug in Emacs that might be specific to the Windows port, send a message to the help-emacs-windows@gnu.org mailing list describing the bug, the version of Emacs that you are using, and the operating system that you are running on (Windows NT, 95 or 98 including service pack level if known). If the bug is related to subprocesses, also specify which shell you are using (e.g., include the values of `shell-file-name' and `shell-explicit-file-name' in your message). If you think the bug is not specific to the Windows port of Emacs, then it is better to mail the bug report to bug-gnu-emacs@gnu.org so that it will be seen by the right people. If Emacs has been set up to send mail, you can use the command M-x report-emacs-bug to create and send the bug report, but in some cases there is a function to report bugs in a specific package; e.g. M-x gnus-bug for Gnus, M-x c-submit-bug-report for C/C++/Java mode, etc.